From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] searching in rio terminal windows
Date: Thu, 22 Apr 2004 09:14:19 +0200 [thread overview]
Message-ID: <bea8a18c32126b8d06265a9e1ed1a6f0@plan9.escet.urjc.es> (raw)
In-Reply-To: <12c63e4238729e9b41a0d889d51485c9@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
Yep. Snarf, Cut, Paste is mostly wasted space in the
menu. We always have a hard time if you don't a have
a 3 button mouse, and if you have one, those entries
give you nothing.
I'd keep just
plumb
send
look
scroll
[-- Attachment #2: Type: message/rfc822, Size: 2231 bytes --]
From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] searching in rio terminal windows
Date: Wed, 21 Apr 2004 04:45:26 -0400
Message-ID: <12c63e4238729e9b41a0d889d51485c9@9srv.net>
i'd love having Look in rio. i've made two or three half-hearted
passes at doing it myself over the last few years, but never
finished any of them.
my solution to it making the button 2 menu too croweded was to
remove the cut/snarf/paste options in favor of chording. in one
of my passes at Look, i had the menu changed (-cut/snarf/past,
+non-functional look) and i didn't look for the missing options
once.
but i realize that's a solution many here would hate. maybe
options for including sets of features?
the addition of plumb was, i think, quite noticable.
ア
next prev parent reply other threads:[~2004-04-22 7:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 2:27 andrey mirtchovski
2004-04-21 2:58 ` Rob Pike
2004-04-21 3:57 ` andrey mirtchovski
2004-04-21 3:15 ` Roman Shaposhnick
2004-04-21 4:34 ` andrey mirtchovski
2004-04-21 4:36 ` Ronald G. Minnich
2004-04-21 9:37 ` Charles Forsyth
2004-04-21 12:54 ` boyd, rounin
2004-04-21 12:44 ` boyd, rounin
2004-04-21 3:37 ` Nick Jamieson
2004-04-21 5:59 ` lucio
2004-04-21 8:45 ` a
2004-04-22 7:14 ` Fco.J.Ballesteros [this message]
2004-04-22 8:56 ` lucio
2004-04-23 8:55 ` Douglas A. Gwyn
2004-04-23 9:02 ` boyd, rounin
2004-04-21 8:48 ` matt
2004-04-21 13:04 ` boyd, rounin
2004-04-21 16:59 ` a
2004-04-21 12:05 ` boyd, rounin
2004-04-21 15:57 ` rog
2004-04-21 16:05 ` matt
2004-04-21 16:17 ` Russ Cox
2004-04-21 16:31 ` matt
2004-04-21 16:36 ` C H Forsyth
2004-04-21 16:35 ` matt
2004-04-21 16:37 ` boyd, rounin
2004-04-21 16:44 ` C H Forsyth
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=bea8a18c32126b8d06265a9e1ed1a6f0@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).