On Fri, 3 Sep 2010 21:56:48 +0300 Liviu Andronic <landronimirc@xxxxxxxxx> wrote: > The difficulty I encountered was that emel didn't accept a %{} as a > sole argument. For example, using action 'file.du' and argument ' > %{(pattern)@Enter pattern:}' fails with > total size: 0 bytes > in 0 files and 0 directories named or in directories named > '%{(pattern)@Enter pattern:}' > -- end-of-output -- > > Should this be fixed? Not a problem to interpret macros (and/or variables) in the plugin. However its design is presently based around either: all selected items, or a single name/pattern, in the current directory. Sensibly handling macros like %f or %d or multiple items named via %{} all need further work. The alternative is to use <custom command>, Even then, present code would not work, due to the way that macro expansion in the command interpreter works for 'file.*' actions. but > it's missing in the list of available actions and, other than not > remembering the exact name, it's awkwardly longish to type when in > need. Would you consider restoring this item in the list, for > convenience purposes? (Confer [1]) 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.