Re: PATCH: _diff (new), _prcs (upgrade)

[Sven Wischnowsky <wischnow@informatik.hu-berlin.de>]

Alexandre Duret-Lutz wrote:

> >>> "Sven" == Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> 
> [...]
> 
>  Sven> The rest of the patch just makes some of the descriptions more
>  Sven> verbose. I hope this is ok for Alexandre (?).
> 
> I don't see why it shouldn't be ok.
> 
>  Sven> Oh, and it makes _diff_options use `$(command diff ...)' -- I at least 
>  Sven> have a small wrapper function for it which makes it fail otherwise.
> 
> I first wrote this, and then removed 'command' when I thought that on a
> system without GNU diff a user may have installed GNU diff and made diff be
> an alias to GNU diff.  But maybe it's quite uncommon especially with diff
> (which is used by several commands and is thus better put in the PATH).
> 
> Also, I should say: I understand why _pids is running $(command ps ...)
> but the difference in _diff_options is that we should be testing the
> command that the user is actually running.

Actually, I wasn't too sure about _pids either... the problem is that
some users may have functions for ps, diff, and so on that may give
completely different results when invoked in the way we invoke them.

Hm. maybe we should try to solve this in a generic manner by writing a 
function that is called in such cases, like:

  _call <name> [ <how> ]

(i.e. we use `$(_diff ps)', `$(_call ps list)' and so on).

_call would then first see if there is a style `command-line' for the
tag `<name>' or, if <how> is given, <name>-<how>. If there is such a
style it is used as an array containing the whole command line to use
(the styles for ps we have now would be removed). If there is no such
style, and $+functions[<name>] is 1, we use `command <name>',
otherwise we use just `<name>'.

Does this sound reasonable?


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de