Re: disk usage of hidden files
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Thu, 26 Aug 2010 16:19:16 +1000
On Wed, 25 Aug 2010 21:26:38 +0300
Liviu Andronic <landronimirc@xxxxxxxxx> wrote:
> > I've committed a revised form of the plugin, which now interprets any
> > action-argument as a request to check the usage of active-pane items
> >
> I also noted this unfortunate limitation. For the example of hidden
> files, file.du would fail on hidden dirs contained in a non-hidden one
> in the active pane. Say,
> file.du !.*
>
> would fail to spot
> ./test/.hidden/file.txt
>
> Do you think there would be a workaround and make this work
> recursively?
Actually, the first version I did used to work like that. However I concluded
that it was better to change, for several reasons.
Actions named like 'file.whatever' apply to items in the active pane, and it
would be inconsistent to depart from this, especially without advice to the
user. And it's less trouble to avoid multiple-counting the size of matching
items which are, or are in, nested directories, say ~/.A/B/.A/C
Although this would (logically) apply only to the
> specific case of hidden files.
I know your specific need is to discover the scope of hidden items, though IMHO
it's no more logical to apply it than for any other item-name.
>
>
> > whose name matches the name or pattern (see IEEE Std 1003.1-2001, Section
> > 2.13.3, Patterns Used for Filename Expansion) in the argument, instead of
> > the former default, which is to check the selected items.
> >
> > Note that if this action is initiated via the command line, you will need
> > to preface a '!', to prevent unwanted addition of any selected items, and
> > to prevent (possibly incomplete) expansion of something like ".*".
> >
> > Please evaluate.
> >
> It is necessary to prepend '!' even when configuring a toolbar item,
> although I cannot manage to configure a toolbar item that behaves
> properly. Is there a different way to initiate the plug-in? Perhaps a
> <shft>+file.du interface, similar to that of Copy names?
I may have been too cryptic. For a toobar action,
file.du .*
is sufficient. For historical reasons, toolbar-initiated actions are processed
by the command-interpreter only if they're not actions.
However for an entered command, you need
!file.du name-or-pattern e.g !file.du .*
NOT
file.du !.*
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:
