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:37:38 -0700 [thread overview]
Message-ID: <5BA34AD7-2629-48C8-98AE-5A45A7CAC8A8@telus.net> (raw)
In-Reply-To: <20051008133306.GB5588@server4.lensbuddy.com>
On 8-Oct-05, at 6:33 AM, Uriel wrote:
>>
> 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.
I thought Dump did that too, but then I found the code that searches
for the end of the tag or the first newline to cut it off at; my dump
files are 100 backwards compatible, because they haven't changed!
> 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.
Yes; I thought of overloading the window button, but again, that
changes existing functionality/expectations. It's pretty easy to
scroll open the tag and check though.
Paul
next prev parent reply other threads:[~2005-10-08 13:37 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 [this message]
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=5BA34AD7-2629-48C8-98AE-5A45A7CAC8A8@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).