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:49:17 -0700 [thread overview]
Message-ID: <28778520-C182-4466-8A5D-D6E67429B6C0@telus.net> (raw)
In-Reply-To: <C746BA14-B78C-4B1D-96DE-336678BF3E5B@telus.net>
Crap - Sorry about the tarball - I have to learn to read the
generated To line on reply vs reply-to-all, which in both cases
defaults to the list, not the sender.
Paul
On 8-Oct-05, at 6:44 AM, Paul Lalonde wrote:
> Uriel - regarding the patch, can you help me?
> I've attached my tarball, it should just build.
> Or, I could use a walk-through of using 9p from p9p to drop the
> file into contrib somewhere handy.
> Thanks,
> Paul
>
> <paul_acme.tgz>
>
> On 8-Oct-05, at 6:33 AM, Uriel wrote:
>
>
>> On Sat, Oct 08, 2005 at 06:19:38AM -0700, Paul Lalonde wrote:
>>
>>
>>> 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 :-(
>>>
>>>
>> Oh, well, that still should let you upload stuff to a sources/contrib
>> dir using 9p(1) or the python 9p client. Or you can drawterm to a
>> 9grid
>> node.
>>
>>
>>
>>> 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.
>>>
>>>
>> I agree, but still I'm unsure \n should be accepted in the tag just
>> making the text flow into the following line when it doesn't fit
>> in the
>> current one should be enough... but I can't think of any strong
>> reason
>> to avoid \n except simplicity as things like dump assume a single
>> line.
>>
>> It would be nice if there was a way to see that there are more lines
>> than what is visible... not sure how that can be done without an
>> extra
>> scroll bar, but that I think would be a bad idea.
>>
>> But I should try the patch before commenting so much :)
>>
>> uriel
>>
>>
>
>
next prev parent reply other threads:[~2005-10-08 13:49 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
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 [this message]
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=28778520-C182-4466-8A5D-D6E67429B6C0@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).