From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] An acme question
Date: Fri, 29 Apr 2011 14:47:53 -0700 [thread overview]
Message-ID: <BANLkTi=1FbBF+=SFDTbhhFewG+Dp3vSFrA@mail.gmail.com> (raw)
In-Reply-To: <864o5gzqhx.fsf@cmarib.ramside>
On Fri, Apr 29, 2011 at 2:39 PM, <smiley@zenzebra.mv.com> wrote:
> Bakul Shah <bakul@bitblocks.com> writes:
>
>> Example: given
>>
>> { fee [({ foo bar}) [and so on]] }
>> 1 2 3456 7
>>
>> Double clicking at 1 selects foo,
>> at 2 or 3 selects the phrase { foo bar},
>> at 4 selects the phrase ({ foo bar}),
>> at 5 selects the phrase [({ foo bar}) [and so on]],
>> at 6 selects the phrase [and so on],
>> at 7 selects the entire { fee [({ foo bar}) [and so on]] } etc.
>> Note: a block need not fit on one line.
>
> If I were filling out an Acme wishlist, I would like to see triple and
> quadruple clicks select larger chunks of text. Being able to do
> something like click-click-click-click to "Select All" (in those apps
> that support it) is frequently very useful.
>
> I would also move the newline in a "selected line" to the begining of,
> rather than the end of, the selection. It would be much easier to cut
> and paste lines if it didn't have to be done from all the way over in
> the wee left margin.
These are all interesting comments. I suggest you just beat on the
code. Honestly, it's pretty nice in there, you can play to your
heart's content. Give it a go.
ron
next prev parent reply other threads:[~2011-04-29 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 16:56 Bakul Shah
2011-04-29 17:16 ` ron minnich
2011-04-29 17:30 ` Bakul Shah
2011-04-29 17:28 ` John Floren
2011-04-29 18:28 ` Bakul Shah
2011-04-29 21:39 ` smiley
2011-04-29 21:47 ` ron minnich [this message]
2011-04-30 7:06 ` Bakul Shah
2011-04-30 12:33 ` 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='BANLkTi=1FbBF+=SFDTbhhFewG+Dp3vSFrA@mail.gmail.com' \
--to=rminnich@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).