From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Acme tag scrolling/expansion
Date: Sat, 8 Oct 2005 06:19:38 -0700 [thread overview]
Message-ID: <091EC7FF-32F8-424F-85BB-AF1CBDD3B43B@telus.net> (raw)
In-Reply-To: <20051008090621.GI18315@server4.lensbuddy.com>
On 8-Oct-05, at 2:06 AM, Uriel wrote
> Very cool; please, could you put it in sources/contrib?
> See: http://plan9.bell-labs.com/wiki/plan9/How_to_contribute/
Ah - I forgot to mention; ever since my shuttle turned into an
unresponsive pile of silicon, I've been working in plan9port under OS
X; patch doesn't exist there :-(
>> Should I also allow carriage returns in the tag text now?
>>
> This might be confusing because IMHO the main purpose for a multi line
> tag is to accommodate longer paths and I don't see much use for
> explicit
> new lines, also opens it to abuse as scratch space for big chunks of
> stuff where a guide file should be used instead.
>
I used to think that too; but I found myself using the longer tag to
hide less-frequent commands, especially with my debugger. I know I
can use "Send" to bridge from a guide file, but then I can't also
chord in a parameter. So, debugging with GDB in particular, I need
break, display, print, and so on, in my tag if I want to chord
parameters. Now I keep them tucked on the second line, and find
myself opening my tag, chording the command, and closing it up, all
in one "gesture". Incidentally - you can already cut and paste
newlines into the tag.
The hard part of multi-line tags is finding a backwards compatible
format for the dump files.
Paul
next prev parent reply other threads:[~2005-10-08 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 3:34 Paul Lalonde
2005-10-08 4:43 ` Paul Lalonde
2005-10-08 9:06 ` Uriel
2005-10-08 12:46 ` erik quanstrom
2005-10-08 13:30 ` Paul Lalonde
2005-10-08 13:19 ` Paul Lalonde [this message]
2005-10-08 13:33 ` Uriel
2005-10-08 13:37 ` Paul Lalonde
2005-10-08 13:44 ` Paul Lalonde
2005-10-08 13:49 ` Paul Lalonde
2005-10-08 15:34 ` Russ Cox
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=091EC7FF-32F8-424F-85BB-AF1CBDD3B43B@telus.net \
--to=plalonde@telus.net \
--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).