Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Stephan Beal
The problem is access - i don't have root access on most systems, and many others don't have compilers, or have quota limitations, weird/old OS versions, etc. So -m, which works the same in all environments, has become what my fingers "just do" without having to be told. - stephan Sent from a

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread David Mason
On 6 October 2014 15:05, Stephan Beal wrote: > good reason not to use -m and rely on $EDITOR instead. i think my problem is > that i regularly use 2 (sometimes 3) SCMs, namely fossil, svn, and > (sometimes) git, often over a remote connection on systems with no emacs > installed (and emacs takes t

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread paul
On 06/10/14 19:41, Scott Robison wrote: Bah! Commit not conmit. Stupid phone keyboard. On Oct 6, 2014 12:39 PM, "Scott Robison" > wrote: On Oct 6, 2014 12:26 PM, "Stephan Beal" mailto:sgb...@googlemail.com>> wrote: > > Hi, all, > > (This jus

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Scott Robison
On Mon, Oct 6, 2014 at 1:34 PM, Andy Bradford wrote: > Thus said Stephan Beal on Mon, 06 Oct 2014 20:25:55 +0200: > > > The autosync option provides (incidentally, not specifically by > > design) a feature one doesn't have if it is turned off: the ability to > > abort a commit within a sma

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Andy Bradford
Thus said Stephan Beal on Mon, 06 Oct 2014 20:25:55 +0200: > The autosync option provides (incidentally, not specifically by > design) a feature one doesn't have if it is turned off: the ability to > abort a commit within a small (and unknown/varying) time frame. Perhaps there should be a

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Ron W
On Mon, Oct 6, 2014 at 3:05 PM, Stephan Beal wrote: > But seriously, though, your argument is a good reason not to use -m and > rely on $EDITOR instead. i think my problem is that i regularly use 2 > (sometimes 3) SCMs, namely fossil, svn, and (sometimes) git, often over a > remote connection on

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Stephan Beal
On Mon, Oct 6, 2014 at 9:00 PM, Scott Robison wrote: > I just wanted to give you a little grief based on past -m comments. :) > LOL! i expected you might be, but wasn't sure if you had arrived on the list the last time that topic came up. But seriously, though, your argument is a good reason not

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Stephan Beal
On Mon, Oct 6, 2014 at 9:05 PM, Ron W wrote: > Hmm. I seem to recall you extolling the virtues of command line editing. :) > Touché! (That's a word we don't get to use nearly enough in everyday speech!) I confess I didn't think if this an a reason to use an actual editor. > Agreed! -- -

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Ron W
On Mon, Oct 6, 2014 at 2:41 PM, Stephan Beal wrote: > On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison > wrote: > >> I have that functionality without auto sync. I don't use the -m comment >> option so I get a text editor showing me what has changed before I type the >> message. If I decide I need

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Scott Robison
I just wanted to give you a little grief based on past -m comments. :) On Oct 6, 2014 12:42 PM, "Stephan Beal" wrote: > On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison > wrote: > >> I have that functionality without auto sync. I don't use the -m comment >> option so I get a text editor showing me

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Stephan Beal
On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison wrote: > I have that functionality without auto sync. I don't use the -m comment > option so I get a text editor showing me what has changed before I type the > message. If I decide I need to not commit, I don't enter a message and > fossil warns me a

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Scott Robison
Bah! Commit not conmit. Stupid phone keyboard. On Oct 6, 2014 12:39 PM, "Scott Robison" wrote: > On Oct 6, 2014 12:26 PM, "Stephan Beal" wrote: > > > > Hi, all, > > > > (This just happened...) > > > > The autosync option provides (incidentally, not specifically by design) > a feature one doesn't

Re: [fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Scott Robison
On Oct 6, 2014 12:26 PM, "Stephan Beal" wrote: > > Hi, all, > > (This just happened...) > > The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. > > For

[fossil-users] Tip: abusing autosync to abort a commit

2014-10-06 Thread Stephan Beal
Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. For example: the intention here was to commit a single file, but