From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme multi-line tags (or maybe, efficient message stores)
Date: Sun, 9 Oct 2011 21:07:35 -0700 [thread overview]
Message-ID: <CA+POUVhK4HHU8zbvFWaH5SVZJuVaP7+dkSK9UzEdjpqPbRkcxg@mail.gmail.com> (raw)
In-Reply-To: <83109255370bf46152ae8d1bb04a463f@chula.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
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.
Paul
On Sun, Oct 9, 2011 at 8:21 PM, erik quanstrom <quanstro@quanstro.net>wrote:
> > didn't have the time to make that change. That said, I find acme (and
> > Edit in particular) damned near unusable without multi-line tags now.
>
> do you have a particular usage senerio where this is most apparent?
>
> - erik
>
>
--
I'm migrating my email. plalonde@telus.net will soon be disconnected.
Please use paul.a.lalonde@gmail.com from now on.
[-- Attachment #2: Type: text/html, Size: 1455 bytes --]
next prev parent reply other threads:[~2011-10-10 4:07 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 [this message]
2011-10-10 7:22 ` dexen deVries
[not found] ` <CA+POUVhK4HHU8zbvFWaH5SVZJuVaP7+dkSK9UzEdjpqPbRkcxg@mail.gmail.c>
2011-10-10 21:36 ` erik quanstrom
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=CA+POUVhK4HHU8zbvFWaH5SVZJuVaP7+dkSK9UzEdjpqPbRkcxg@mail.gmail.com \
--to=paul.a.lalonde@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).