9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme 2-1 chord arguments
Date: Thu, 16 Jul 2015 21:06:02 +0300	[thread overview]
Message-ID: <CAJ1xhMX0Wc3X299Bznx2BA23EX=pXfakZ1iBrDCgVJAJtnhZCQ@mail.gmail.com> (raw)
In-Reply-To: <F61F8036-437A-4109-B410-D400894DED24@icloud.com>

I see. Sorry. I don't have any other ideas for you to try at the moment.


On Thu, Jul 16, 2015 at 8:45 PM, Brian Zwahr <echosa@icloud.com> wrote:
> Sorry, let me be more clear. The issue when I need to send multiple arguments. For instance using 2-1 to add “pull” or “checkout” to “git” works. However, using 2-1 to add “pull --prune” or “checkout .” does not work. At least, not in +Errors. It does work in win, though, apparently.
>
>> On Jul 16, 2015, at 12:39 PM, Alexander Kapshuk <alexander.kapshuk@gmail.com> wrote:
>>
>> I just tried typing 'git' into my '/project/root/dir/+Errors' with
>> 'log' selected in a different Acme window. Executing chord 2-1 on
>> 'git' did work for me. The 'log' argument has to be selected in its
>> entirety, but not the trailing new line, which would generate an
>> 'invalid key error' message, if passed to 'git'. Alternatively, you
>> may just click with  button 1 on the argument being passed, and then
>> do the 2-1 chord on 'git'. This worked for me as well. Hope this
>> helps.
>>
>> Do you get any output when you try doing the 2-1 mouse chord on git?
>>
>> On Thu, Jul 16, 2015 at 8:15 PM, Brian Zwahr <echosa@icloud.com> wrote:
>>> I guess I should clarify that I’m not using win. I normally do everything in a +Errors window. So, for git, I run all the commands in /project/root/dir/+Errors.
>>>
>>> I just tried in a win window, and it does work. I’m assuming this is because win parses what’s passed in differently.
>>>
>>>> On Jul 16, 2015, at 11:54 AM, Alexander Kapshuk <alexander.kapshuk@gmail.com> wrote:
>>>>
>>>> On Wed, Jul 15, 2015 at 5:06 PM, Brian Zwahr <echosa@icloud.com> wrote:
>>>>> 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?
>>>>>
>>>>>
>>>>
>>>> Have you tried typing git into the win tag and typing and selecting
>>>> the subsequent arguments in another window, passing them to git via
>>>> the 2-1 chord?
>>>>
>>>> I've just tried doing that with 'git pull', and 'ls -ld .', both
>>>> commands working as expected for me.
>>>>
>>>> Is this what you've been trying to do, or am I thinking wrong here?
>>>>
>>>
>>>
>>
>
>



      reply	other threads:[~2015-07-16 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 14:06 Brian Zwahr
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 [this message]

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='CAJ1xhMX0Wc3X299Bznx2BA23EX=pXfakZ1iBrDCgVJAJtnhZCQ@mail.gmail.com' \
    --to=alexander.kapshuk@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).