From: yy <yiyu.jgl@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a small Acme annoyance
Date: Wed, 12 Dec 2012 15:01:56 +0100 [thread overview]
Message-ID: <CADErNDt6n-jpPcZ=9KQh1qyZSz0iiqUriU2kSQhchM66viTGbg@mail.gmail.com> (raw)
In-Reply-To: <7d259252f052b63e8397caef9c96c896@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
On 12 December 2012 00:00, <lucio@proxima.alt.za> wrote:
> Sounds unavoidable.
If it really annoys you, avoiding it is actually quite easy.
Some time ago I wrote a small patch [1] to interpret the pipe symbol as
Edit when it is all the selected text (ie. when it is not followed by a
command). This is quite convenient to use the 1-2 chord with Edit commands.
You could either apply this patch or a modified version.
[1] http://9fans.net/archive/2009/08/571
--
- yiyus || JGL .
[-- Attachment #2: Type: text/html, Size: 1098 bytes --]
next prev parent reply other threads:[~2012-12-12 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 12:53 dexen deVries
2012-12-11 23:00 ` lucio
2012-12-12 14:01 ` yy [this message]
2012-12-12 18:13 ` dexen deVries
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='CADErNDt6n-jpPcZ=9KQh1qyZSz0iiqUriU2kSQhchM66viTGbg@mail.gmail.com' \
--to=yiyu.jgl@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).