9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Fri,  7 Oct 2005 21:43:11 -0700	[thread overview]
Message-ID: <7D9B8282-F623-44A0-8782-ECFE2CAE9025@telus.net> (raw)
In-Reply-To: <4E221736-0D0C-496F-A6FB-C33F305D58D7@telus.net>

And one more associated question: with longer tags, does it make  
sense to augment the dump format to save/restore tags with carriage  
returns?

Paul

On 7-Oct-05, at 8:34 PM, Paul Lalonde wrote:

> I have a working hack to acme that now lets me use the scroll wheel  
> to expand the tag to multiple lines and collapse it again.  It  
> seems to have no nasty interactions with the feature set I use.   
> Moving a window into a slot shorter than the tag shortens the tag  
> to fit.  One line of the body tries to always show, except when  
> windows are collapsed.  Dragging the tag text continues to work.
>
> Does anyone else want it?  How do I submit the patch?  It's  
> substantially smaller than I expected.
>
> Should I also allow carriage returns in the tag text now?
>
> One thing that it has caused me to observe in more detail is the  
> layout bug where occasionally a window moved into a tight space  
> wastes nearly a line of space and doesn't show the separator bar  
> between it and the (unshown) body.  I'll pick at it this evening.
>
> Paul
>
>



  reply	other threads:[~2005-10-08  4:43 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 [this message]
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
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=7D9B8282-F623-44A0-8782-ECFE2CAE9025@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).