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 ctrl-w, or whatever), then 1x > ctrl-y, then Esc-y. Esc-y acts upon the previous Ctrl-Y, and subsequent > Esc-y's pull back one proceeding entry further from the yank buffer.
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.) NetBSDs /bin/sh. Good tip though. [1] http://en.wikipedia.org/wiki/GNU_Readline [2] http://thrysoee.dk/editline/ > Nonetheless, it is easy to lose text this way, so i recommend the comment > method over the yank buffer. > > ("$" is shell prompt). >> >> ":" is a command that consumes it's arguments and returns true. >> > > Another nice one. At times i've seen in-script docs done that way: > > : <<EOF > docs go here... > EOF > > Not sure why one would do it that way, though. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of > those who insist on a perfect world, freedom will have to do." -- Bigby > Wolf > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
