From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] find command reloaded
Date: Sun, 24 Jan 2010 11:46:26 -0800 [thread overview]
Message-ID: <3e1162e61001241146v37d238e3ob0780aba56a3a54c@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.64.1001240804520.5454@malasada.lava.net>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Sun, Jan 24, 2010 at 10:05 AM, Tim Newsham <newsham@lava.net> wrote:
> I have never felt the need for tools like these, I use the mouse to edit
>> the text on the screen (changing history), I then double click to the
>> right
>> of the line and click send which resubmits the text.
>>
>> The idea that any text on the screen may be used to form a new command is
>> very powerful, but takes some getting used to.
>>
>
> the " command works with the grain here. It brings text
> on the screen that may be further away closer.
>
Actually, I've never used those scripts... mainly because I'm not really
sure I "get it". I've just always typed what I wanted in, and a lot of
times, my work patterns involve invoking the same pretty recent steps over
and over. Snarf buffer often works just fine for me.
I guess I should learn to try out the " command sometime. I mean like
pretty much everything else Russ has done :-)
Dave
>
> -Steve
>>
>
> Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
>
>
[-- Attachment #2: Type: text/html, Size: 1917 bytes --]
next prev parent reply other threads:[~2010-01-24 19:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 17:29 Rudolf Sykora
2010-01-22 17:36 ` ron minnich
2010-01-22 17:44 ` Rudolf Sykora
2010-01-22 18:15 ` ron minnich
2010-01-22 18:20 ` erik quanstrom
2010-01-22 18:59 ` Rudolf Sykora
2010-01-22 18:40 ` Rudolf Sykora
2010-01-22 18:52 ` ron minnich
2010-01-22 17:41 ` maht
2010-01-22 18:00 ` Rudolf Sykora
2010-01-22 17:44 ` Robert Raschke
2010-01-22 17:59 ` Rudolf Sykora
2010-01-22 18:08 ` Corey Thomasson
2010-01-22 18:12 ` andrey mirtchovski
2010-01-22 18:19 ` Joseph Xu
2010-01-22 18:26 ` ron minnich
2010-01-22 18:29 ` Rudolf Sykora
2010-01-22 18:42 ` ron minnich
2010-01-22 19:00 ` geoff
2010-01-22 19:37 ` John Stalker
2010-01-22 19:45 ` erik quanstrom
2010-01-22 20:16 ` Jason Catena
2010-01-22 20:26 ` ron minnich
2010-01-22 20:23 ` John Stalker
2010-01-22 20:31 ` erik quanstrom
2010-01-22 20:57 ` John Stalker
2010-01-22 20:38 ` ron minnich
2010-01-22 21:07 ` Steve Simon
2010-01-22 21:18 ` Tim Newsham
2010-01-22 21:11 ` John Stalker
2010-01-22 21:54 ` erik quanstrom
2010-01-22 22:08 ` John Stalker
2010-01-23 6:04 ` lucio
2010-01-23 10:16 ` John Stalker
2010-01-23 15:02 ` Rudolf Sykora
2010-01-23 15:24 ` Steve Simon
2010-01-23 15:44 ` Rudolf Sykora
2010-01-24 18:05 ` Tim Newsham
2010-01-24 19:46 ` David Leimbach [this message]
2010-01-23 15:42 ` erik quanstrom
2010-01-23 15:52 ` Rudolf Sykora
2010-02-03 17:58 ` Rudolf Sykora
2010-02-03 18:23 ` Rudolf Sykora
2010-02-03 18:28 ` erik quanstrom
2010-02-03 18:40 ` Rudolf Sykora
2010-01-22 18:13 ` Jason Catena
2010-01-22 19:17 ` John Stalker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e1162e61001241146v37d238e3ob0780aba56a3a54c@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).