Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Stephan Beal
On Tue, Jun 17, 2014 at 6:49 AM, B Harder brad.har...@gmail.com wrote: Remember that the buffer is only one level deep, though. A subsequent ^W, ^K , etc will clobber the previous contents. Almost: try 2x (NON-consecutively) ctrl-k (or ctrl-w, or whatever), then 1x ctrl-y, then Esc-y. Esc-y

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Sergei Gavrikov
On Tue, 17 Jun 2014, Nico Williams wrote: On Mon, Jun 16, 2014 at 11:49 PM, B Harder wrote: Remember that the buffer is only one level deep, though. A subsequent ^W, ^K , etc will clobber the previous contents. Along lines of Stephan Beals method, I use : preceding the fossil command.

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Eric Rubin-Smith
This thread is hilarious. I thought I was pretty old-school -- I use vi, xterm, fvwm2, and other tools written by my forebears around the time when I was born. I get made fun of by people twice my age for my dev toolkit. But even *I* will have two terminals up concurrently -- so that I can

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Scott Robison
On Jun 17, 2014 8:42 AM, Eric Rubin-Smith eas@gmail.com wrote: This thread is hilarious. I thought I was pretty old-school -- I use vi, xterm, fvwm2, and other tools written by my forebears around the time when I was born. I get made fun of by people twice my age for my dev toolkit.

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread B Harder
On 6/17/14, Stephan Beal sgb...@googlemail.com wrote: On Tue, Jun 17, 2014 at 6:49 AM, B Harder brad.har...@gmail.com wrote: Remember that the buffer is only one level deep, though. A subsequent ^W, ^K , etc will clobber the previous contents. Almost: try 2x (NON-consecutively) ctrl-k (or

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Stephan Beal
On Tue, Jun 17, 2014 at 7:24 PM, B Harder brad.har...@gmail.com wrote: Nice! As a BSD user though, I feel compelled to point out this looks like a readline[1] feature, and not an editline[2] feature. So it works with bash (and likely other readline linked progs), it doesn't work w/ (e.g.)

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread B Harder
On Jun 17, 2014 10:47 AM, Stephan Beal sgb...@googlemail.com wrote: On Tue, Jun 17, 2014 at 7:24 PM, B Harder brad.har...@gmail.com wrote: Nice! As a BSD user though, I feel compelled to point out this looks like a readline[1] feature, and not an editline[2] feature. So it works with bash

[fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/16/2014 3:24 PM, Stephan Beal wrote: 1) Move your cursor to the beginning of the line. In Bash-like shells that's normally Ctrl-A, but many terminals support the Home key as well. 2) Type the '#' character (shift-3 on a US keyboard). That's

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Doug Franklin
On 2014-06-17 22:00, Andy Goth wrote: This almost works in csh (which I am regrettably forced to use). Yes, the command is not executed but is still stuffed in the history buffer, Maybe I'm OCD or something, but if I have to do it more than twice, it gets embodied as a script. :) --

[fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-17 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/17/2014 9:40 PM, Doug Franklin wrote: On 2014-06-17 22:00, Andy Goth wrote: This almost works in csh (which I am regrettably forced to use). Yes, the command is not executed but is still stuffed in the history buffer, Maybe I'm OCD or

[fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-16 Thread Stephan Beal
Hi, all, This is for Unix-shell users only (including workalikes on Windows)... Here's a time-saving tip which i use very often myself, but most CLI users i know don't seem to know about: It often happens that i'm typing a commit message when i decide i need to stop and go check if what i'm

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-16 Thread Scott Robison
On Mon, Jun 16, 2014 at 2:24 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, This is for Unix-shell users only (including workalikes on Windows)... Here's a time-saving tip which i use very often myself, but most CLI users i know don't seem to know about: It often happens that i'm

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-16 Thread Matt Welland
Under bash another way to achieve the goal of temporarily putting your partially written commit command aside is to do: ^a ^k This puts your command in the cut buffer. To retrieve it (after having run fossil gdiff to figure out what you did!) just do: ^y On Mon, Jun 16, 2014 at 1:24 PM,

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-16 Thread B Harder
Remember that the buffer is only one level deep, though. A subsequent ^W, ^K , etc will clobber the previous contents. Along lines of Stephan Beals method, I use : preceding the fossil command. So: $ : fossil ci -m 'some msg' ($ is shell prompt). : is a command that consumes it's arguments and

Re: [fossil-users] fossil CLI tricks: interrupting a commit message

2014-06-16 Thread Nico Williams
On Mon, Jun 16, 2014 at 11:49 PM, B Harder brad.har...@gmail.com wrote: Remember that the buffer is only one level deep, though. A subsequent ^W, ^K , etc will clobber the previous contents. Along lines of Stephan Beals method, I use : preceding the fossil command. So: $ : fossil ci -m