9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] searching in rio terminal windows
Date: Wed, 21 Apr 2004 16:57:55 +0100	[thread overview]
Message-ID: <824dcbc42c5a77605369bc958f12f80a@vitanuova.com> (raw)
In-Reply-To: <097001c42798$efe91a40$0fca7d50@SOMA>

> i suggested this to rob in 1992-1993 when 9term came out but
> he said it would make the button 2 menu too long.  i added it
> to 9term anyway and it was very useful; looking for 'close'
> strings in log files was one use.

what i tend to do in these circumstances is select all the text
in the rio window, click New in acme and paste it in there.

(that brings me to the thing i find most annoying in rio - i'll
drag down to the end of the window, chord cut and paste to
snarf it all... and it executes the entire snarf buffer!
(potentially really nasty, but mitigated by dumpfs...)
i started to have a look at fixing this once, but got bogged
down and haven't mustered the energy again.)

acme Edit in temporary windows for playing with log files
is a wonderful thing.

(actually, it's great in other ways too. for example, i tend to keep a large mailbox,
and in a /mail/fs/mbox/ window, i can do:
Edit ,x/^[0-9].*\n(	.*\n)*/g/\[9fans]/d
to restrict my view to non-9fans messages only.)

acme temporary, unlabeled, windows are great. it's a pity
they're not archived when acme is Dumped.

to add to the mouse button thing: if i had an extra mouse button,
i think i'd use it as a "search backwards" button in acme.



  reply	other threads:[~2004-04-21 15:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  2:27 andrey mirtchovski
2004-04-21  2:58 ` Rob Pike
2004-04-21  3:57   ` andrey mirtchovski
2004-04-21  3:15     ` Roman Shaposhnick
2004-04-21  4:34       ` andrey mirtchovski
2004-04-21  4:36       ` Ronald G. Minnich
2004-04-21  9:37       ` Charles Forsyth
2004-04-21 12:54       ` boyd, rounin
2004-04-21 12:44     ` boyd, rounin
2004-04-21  3:37 ` Nick Jamieson
2004-04-21  5:59 ` lucio
2004-04-21  8:45 ` a
2004-04-22  7:14   ` Fco.J.Ballesteros
2004-04-22  8:56     ` lucio
2004-04-23  8:55     ` Douglas A. Gwyn
2004-04-23  9:02       ` boyd, rounin
2004-04-21  8:48 ` matt
2004-04-21 13:04   ` boyd, rounin
2004-04-21 16:59     ` a
2004-04-21 12:05 ` boyd, rounin
2004-04-21 15:57   ` rog [this message]
2004-04-21 16:05     ` matt
2004-04-21 16:17       ` Russ Cox
2004-04-21 16:31         ` matt
2004-04-21 16:36           ` C H Forsyth
2004-04-21 16:35             ` matt
2004-04-21 16:37               ` boyd, rounin
2004-04-21 16:44             ` C H Forsyth

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=824dcbc42c5a77605369bc958f12f80a@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /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).