From: Brian Zwahr <echosa@icloud.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Acme 2-1 chord arguments
Date: Wed, 15 Jul 2015 09:06:20 -0500 [thread overview]
Message-ID: <2967C352-8607-44E6-87FA-DB94B18688DC@icloud.com> (raw)
According to the man page, using the 2-1 chord sends selected text as a *distinct* argument to the executed command. This is all well and good for Edit, Look, etc. However, it keeps me from being able to, for instance, select “checkout .” or “pull —prune” and then 2-1 on “git”. So, two questions:
1.) Is there a way to do what I’m trying to do?
2.) What was the reasoning behind 2-1 chording sending distinct arguments?
next reply other threads:[~2015-07-15 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:06 Brian Zwahr [this message]
2015-07-15 15:41 ` dexen deVries
2015-07-16 15:44 ` Brian Zwahr
2015-07-16 16:54 ` Alexander Kapshuk
2015-07-16 17:15 ` Brian Zwahr
2015-07-16 17:39 ` Alexander Kapshuk
2015-07-16 17:45 ` Brian Zwahr
2015-07-16 18:06 ` Alexander Kapshuk
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=2967C352-8607-44E6-87FA-DB94B18688DC@icloud.com \
--to=echosa@icloud.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).