Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-15 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Wed, 14 Dec 2005 19:09:39 +0100, Jon Bright [EMAIL PROTECTED] said: jon ~$ monotone rev jon monotone: The revert command must be typed in full jon jon How does that sound? Best of both worlds, or unwanted nannying? The latter. Cheers, Richard - Please

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-14 Thread Nathaniel Smith
On Tue, Dec 13, 2005 at 10:59:34PM -0600, Chad Walstrom wrote: For example, while commi will expand to commit today, it will fail to do so tomorrow when we add the much requested commissar appointment feature to monotone. Then you get an error and learn that there's a new command

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-14 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Wed, 14 Dec 2005 15:31:39 +1300, Matthew Gregan [EMAIL PROTECTED] said: kinetik While discussing the current behaviour of 'monotone revert' kinetik (see Alex's email about the possibility of losing work too kinetik easily) on #monotone, the idea of removing the

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-14 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Tue, 13 Dec 2005 23:39:34 -0800, Nathaniel Smith [EMAIL PROTECTED] said: njs On Tue, Dec 13, 2005 at 10:59:34PM -0600, Chad Walstrom wrote: njs For example, while commi will expand to commit today, it will njs fail to do so tomorrow when we add the much

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-14 Thread Chad Walstrom
Nathaniel Smith [EMAIL PROTECTED] wrote: Fingers are also effectively a scripting environment; I think the other _monotone_ developers would lynch us if we tried to make them relearn up or ci. Never mind the actual user base :-). True. Very, very true, and thus why command names need to be

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-14 Thread Daniel Carosone
On Wed, Dec 14, 2005 at 07:09:39PM +0100, Jon Bright wrote: Hi, Richard Levitte - VMS Whacker wrote: I disagree with removing keyword expansion. I agree that some aliases can be added to ensure that certain shortcuts always work. I also disagree with removing keyword expansion on the

[Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-13 Thread Matthew Gregan
Hi list, While discussing the current behaviour of 'monotone revert' (see Alex's email about the possibility of losing work too easily) on #monotone, the idea of removing the automatic command expansion from monotone was discussed. monotone currently accepts commands in three ways: 1.

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-13 Thread Chad Walstrom
Matthew Gregan [EMAIL PROTECTED] wrote: While discussing the current behaviour of 'monotone revert' (see Alex's email about the possibility of losing work too easily) on #monotone, the idea of removing the automatic command expansion from monotone was discussed. What?! Why? 3. By guessing

Re: [Monotone-devel] Command aliases and removing command expansion from monotone

2005-12-13 Thread Chad Walstrom
Chad Walstrom [EMAIL PROTECTED] wrote: Aliases, on the other hand, are explicitly defined. This means that they're less likely to change tomorrow, and that any change that affected them is much more likely to be reflected in the documentation and the monotone release notes. Command