From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v734)
In-Reply-To: <20051008090621.GI18315@server4.lensbuddy.com>
References: <4E221736-0D0C-496F-A6FB-C33F305D58D7@telus.net>
	<20051008090621.GI18315@server4.lensbuddy.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <091EC7FF-32F8-424F-85BB-AF1CBDD3B43B@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:19:38 -0700
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 97461e6c-ead0-11e9-9d60-3106f5b1d025


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