9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] acme multi-line tags (or maybe, efficient message stores)
Date: Mon, 10 Oct 2011 17:36:03 -0400	[thread overview]
Message-ID: <396284eb18c16a071ce649b5e2370e4a@brasstown.quanstro.net> (raw)
In-Reply-To: <CA+POUVhK4HHU8zbvFWaH5SVZJuVaP7+dkSK9UzEdjpqPbRkcxg@mail.gmail.c>

On Mon Oct 10 00:08:51 EDT 2011, paul.a.lalonde@gmail.com wrote:

> I often keep an Edit I'm refining in a separate tag line for easy selection.
> But the real use was in keeping commands that need chorded parameters, so my
> debugger sessions, for example, keep a line of "list print break" etc, so I
> can chord in the parameter easily.  That way I don't have to construct the
> breakpoint instruction in a scratch window, and I can keep enough of them
> around to be useful - one tag line isn't big enough.

i'd rather have a window like win that would operate on the same principle
as the sam edit window.

unless i've misread the man page, i don't think this is possible with the current
command interface*.  you'd have to insert the text into the tag and then execute
it.  it'd be the opposite of screen scraping.  :-)

- erik

*i want to send "Edit X ,s:frobnatz:blatz:g." or "Edit b somefile",  how do i do that?



  parent reply	other threads:[~2011-10-10 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 19:48 Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-10-10  3:25 ` Paul Lalonde
2011-10-10  3:21   ` erik quanstrom
2011-10-10  4:07     ` Paul Lalonde
2011-10-10  7:22     ` dexen deVries
     [not found]     ` <CA+POUVhK4HHU8zbvFWaH5SVZJuVaP7+dkSK9UzEdjpqPbRkcxg@mail.gmail.c>
2011-10-10 21:36       ` erik quanstrom [this message]
2011-10-11  5:59         ` Peter A. Cejchan
2011-10-11  7:41           ` hiro
2011-10-11  8:09             ` yy
2011-10-11  8:15               ` Peter A. Cejchan
2011-10-11  8:56                 ` yy
2011-10-11  9:02                   ` Peter A. Cejchan
2011-10-11 22:48                   ` yy
2011-10-11 12:41               ` hiro

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=396284eb18c16a071ce649b5e2370e4a@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).