9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: erik quanstrom <quanstro@speakeasy.net>,
	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:30:44 -0700	[thread overview]
Message-ID: <09C75CA2-AD55-46E2-8FF7-3821EAAD6316@telus.net> (raw)
In-Reply-To: <20051008124641.6E5561A825B@dexter-peak.quanstro.net>


On 8-Oct-05, at 5:46 AM, erik quanstrom wrote:
> can this work with a 3-button mouse, too?

I'd like it to, but I was unable to find an interaction that didn't  
break the current behaviour: the obvious thing is to manipulate the  
window button.  The second most obvious thing is to add TagExpand and  
TagReduce keywords, but that's a nasty cop-out - they are slow and  
awkward to use, which isn't bad for expanding, but is awful (I tried  
it) for making the tag smaller and reclaiming space.  Pretty much  
every gesture of 3 buttons is already used up.

Any suggestions?
>
> it's hard to type "| awkscript <script>" in acme for this
> reason. it gets difficult to read even for a 3-line BEGIN/
> for-each-line/END script.
For this I'm on uriel's side: I drop my scripts into the guide file  
and chord it to Send or to '|' in the appropriate window.

>
> alternatively, what if any line after the first scrolls and is  
> executed
> on \n, like sam.

Now that I won't implement - I think Rob would shoot me!

Paul



  reply	other threads:[~2005-10-08 13:30 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 [this message]
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=09C75CA2-AD55-46E2-8FF7-3821EAAD6316@telus.net \
    --to=plalonde@telus.net \
    --cc=9fans@cse.psu.edu \
    --cc=quanstro@speakeasy.net \
    /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).