Re: A couple of things...
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Wed, 9 Jul 2008 23:17:13 +1000
On Tue, 8 Jul 2008 17:48:08 +0100 (IST)
"Sadako" <sadako@xxxxxxxxxxxxxxxxx> wrote:
> Just a few of things I'd like to ask about;
>
> #1: middle-click in the address/location bar brings up an open dialog,
> rather than just pasting from the X selection buffer, is this by design?
Yes.
We do want an easy way to trigger the dialog by mouse-action (in keeping with
our goal of making things happen by mouse or keyboard). Left- and right-clicks
are taken, and it seemed like pasting into an address-entry would be not so
common, and anyway, pasting is available via a right-click context-menu.
But the current arrangement could be changed without any great harm, so as to
not detract from "standard" functionality.
Maybe it would be easiest to remember as <Ctrl><middle-click> ? Anyone got any
strong views about this stuff ?
>
> #2: If you set emelfm2 to open a particular directory in each pane upon
> startup, it still visibly opens the last directories viewed, and _then_
> switches to the direcories specified...
Wasted effort doesn't actually happen, but it may look a bit like it. The
directory-combo will initially show the history from last session, but any
"startup" dir is selected before any filelist contents are produced.
> #3: I'm pretty sure with 0.0.9 you could select and open multiple files
> normally _without_ opening the context menu, but now emelfm2 only opens
> the first file selected.
> I can understand why you'd want to do this, but is there any way to
> re-enable the old functionality?
No. It's a "safety blanket". It's too easy to select different sorts of things
and then activate them. With the context menu, at least you have to think again
about what you're doing.
> I had a look at the source, but I'm not really much of a programmer so
> that was kind of pointless...
>
> #4: When you open a file simply by clicking it or selecting it and
> pressing enter, the filename is provided to whatever you have associated
> that filetype with the full path, however if you open the file by bringing
> up the context menu and selecting any of the programs associated with it,
> only the file name is provided, no path, which is understandable as you
> can select and open multiple files by this method, but the difference in
> behaviour seems a little bit odd (and is messing with my mpc script :( )
It defaults to adding just the names, if only a command|application name is
provided via the dialog.
It's quite ok to include macros, and in particular, to append %p. That will
provide the full path of each selected item as separate arguments.
Maybe it would be more consistent to default to %p behaviour, with %f to
over-ride that. Especially as the operation is queued, and it may be that the
CWD is not what it was when the selection was done ...
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.
- Follow-Ups:
- Re: A couple of things...
- From: Liviu Andronic
- Re: A couple of things...
- From: Sadako
- References:
- A couple of things...
- From: Sadako
Other related posts:
- » A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- » Re: A couple of things...
- Re: A couple of things...
- From: Liviu Andronic
- Re: A couple of things...
- From: Sadako
- A couple of things...
- From: Sadako