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 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-
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 1
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 p
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, 2
On Wed, Jul 15, 2015 at 5:06 PM, Brian Zwahr 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
Thanks for the information! I must confess, I don’t fully understand your
idiomatic answer.
> On Jul 15, 2015, at 10:41 AM, dexen deVries wrote:
>
> dirty 1.) rc -c 'git '^
> note the space after git
>
> idiomatic 1.) use win(1), pass 'command' argument a script which executes git
> for ea
