Re: emelfM2 pre-release available
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Wed, 27 Dec 2006 09:29:28 -0500
On Mon, 25 Dec 2006 19:31:22 -0500
"Liviu Andronic" <landronimirc@xxxxxxxxx> wrote:
> > That's a deliberate change. Not for any compelling reason, but to make
> > commands consistent with actions (which must be cancelled when a session
> > ends) and a probably-mistaken concern about managing zombie processes. It
> > could readily be reversed.
>
> In my view, this is a dangerous feature. User doesn't expect such
> behaviour from a file manager.
Seems right. But presumably they do expect it from a terminal-emulator. And e2
is a bit of both, and happens to run commands somewhat like a terminal.
Taking down child processes when
> emelFM2 shuts down, can be very damaging.
The exit warning does have a purpose beyond nagging ...
I've tested it with
> Mousepad: an unsaved document gets down (no promting for
> saving/discarding). Other applications may be doing something
> important for user, and the latter would not at all expect that
> closing emel would close their program (ripping a dvd, for example,
> with acidrip).
>
> emel's advantage is that _any_ command can be attributed to
> buttons/keybindings: on a personal level, I use emel to start
> applications that otherwise would be quite a mess to start in
> Terminal. So, I start the application and then I close emel, as I
> don't need him any more at that given moment
Except in the case of computer resource limitation, that closure is essentially
a user-choice (or habit), isn't it?
I'm all for allowing old habits to persist, unless there's a good reason
otherwise. And in this case, there is a reason, but I'm still not sure how good
it is.
(for example, emelFM2 in
> combination with mplayer and an input box cacheing entries is one easy
> way to get DVDs or VCDs playing).
>
> Well, I would be against this feature even as an option. Potentially,
> it is too dangerous.
Regards
Tom
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts:
