RFC: Shell Aliases and Arguments

[Martin Geisler]

Isaac Jurado <diptongo at gmail.com> writes:

> Replying Steve Losh:
>
>> You could of course make an 'hgqempty' script and put it on your path.
>> That works, but it's less than ideal:
>>
>> * It pollutes the tab completion namespace.

This is what annoys me the most.

>> * When you want to run an alias/script you now need to think "Did I
>>   define that as an alias (hg qempty) or a script (hgqempty)?"
>> * It's yet another file to keep synced to all the machines you work on
>>   (not a huge deal, since it could live with the rest of your
>>   dotfiles).
>>
>> Defining qempty as an alias avoids these problems.
>
> I was already aware of those.  You can also add to the list the fact
> that aliases are detected by the various shell programmable completion
> becuse hg lists them as commands.  However I didn't find them important
> enough to add dedicated functionality.  Having it already implemented
> changes the scenario considerably.
>
> Well, sorry for posting this in -dev.

No need to apologize, I think you raise some valid points and that this
is the right place for such this discussion.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100823/aaa2eb22/attachment.pgp>