From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v734)
In-Reply-To: <20051008133306.GB5588@server4.lensbuddy.com>
References: <4E221736-0D0C-496F-A6FB-C33F305D58D7@telus.net>
	<20051008090621.GI18315@server4.lensbuddy.com>
	<091EC7FF-32F8-424F-85BB-AF1CBDD3B43B@telus.net>
	<20051008133306.GB5588@server4.lensbuddy.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5BA34AD7-2629-48C8-98AE-5A45A7CAC8A8@telus.net>
Content-Transfer-Encoding: 7bit
From: Paul Lalonde <plalonde@telus.net>
Subject: Re: [9fans] Acme tag scrolling/expansion
Date: Sat,  8 Oct 2005 06:37:38 -0700
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 975564a8-ead0-11e9-9d60-3106f5b1d025


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