From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] reverse search direction in p9p acme
Date: Mon, 19 Sep 2011 10:13:16 +0100 [thread overview]
Message-ID: <CAJhgacg11sjJ69T7iLRhk8W5+Qi_FXa8jhe=PKXv+U6asq4n-A@mail.gmail.com> (raw)
In-Reply-To: <201109191055.56851.dexen.devries@gmail.com>
On 19 September 2011 09:55, dexen deVries <dexen.devries@gmail.com> wrote:
> On Monday 19 of September 2011 10:37:54 roger peppe wrote:
>> i'm not sure about adding more invisible state to acme
>> windows.
>
> if `hidden' is the keyword, then let's have some new files in acme's control
> file hierarchy for various bits of state.
making the state available to programs doesn't really cut it for me.
for it to be useful in moment-to-moment interactions with acme,
it must be visible on screen, in the same way that the dirty
bit has the top left indicator (well, mostly).
> privately i think the Rev command is redundant, but meh.
well, i've gone all these years without it, so it is redundant in that
sense, but it still feels a bit awkward when browsing a large file
and right clicking one-too-many times, that i have to copy the
text to the tag, insert :-/, reselect and/or quote metacharacters,
and click. it's a sequence i often get slightly wrong too
by getting the selection slightly out.
a single-click reverse search would quickly internalise and be
very useful i think. the difficulty is coming up with the right way of
doing it.
next prev parent reply other threads:[~2011-09-19 9:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 13:21 Mathieu Lonjaret
2011-09-18 13:28 ` dexen deVries
2011-09-18 13:32 ` Mathieu Lonjaret
2011-09-18 13:56 ` dexen deVries
2011-09-18 14:19 ` Mathieu Lonjaret
2011-09-18 14:30 ` dexen deVries
2011-09-18 14:52 ` Mathieu Lonjaret
2011-09-19 8:01 ` Peter A. Cejchan
2011-09-19 8:19 ` Mathieu Lonjaret
2011-09-19 8:37 ` roger peppe
2011-09-19 8:55 ` dexen deVries
2011-09-19 9:13 ` roger peppe [this message]
2011-09-19 9:14 ` Mathieu Lonjaret
2011-09-19 9:34 ` yy
2011-09-19 14:50 ` Rob Pike
2011-09-19 16:14 ` roger peppe
2011-09-19 18:17 ` Rob Pike
2011-09-20 8:00 ` roger peppe
2011-09-20 14:22 ` Rob Pike
2011-09-23 13:52 ` Yaroslav
2011-09-26 8:59 ` Christian Neukirchen
2011-09-26 9:59 ` Steve Simon
[not found] ` <CAKzdPgxHUkmZ9wVHVNo>
[not found] ` <CAKzdPgx2WxsMsh-opRuHAFbrqDjf9LW15b_d0xT2Ym_zngrjoQ@mail.gmail.c>
2011-09-19 18:19 ` erik quanstrom
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='CAJhgacg11sjJ69T7iLRhk8W5+Qi_FXa8jhe=PKXv+U6asq4n-A@mail.gmail.com' \
--to=rogpeppe@gmail.com \
--cc=9fans@9fans.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).