VIM - running a shell command fails within a macro
up vote
0
down vote
favorite
I have a list of items in a file, and I am trying to add an id on the line before each one. The id is generated by an external shell command and added to the buffer:
:r !php _setup/getid/php item | tail -1
This works fine in normal mode. However, when I record a macro containing only the above command and then run it I get the error:
Could not open input file: _set
added to the buffer.
Does anyone know what's happening here?
vim shell macros
add a comment |
up vote
0
down vote
favorite
I have a list of items in a file, and I am trying to add an id on the line before each one. The id is generated by an external shell command and added to the buffer:
:r !php _setup/getid/php item | tail -1
This works fine in normal mode. However, when I record a macro containing only the above command and then run it I get the error:
Could not open input file: _set
added to the buffer.
Does anyone know what's happening here?
vim shell macros
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a list of items in a file, and I am trying to add an id on the line before each one. The id is generated by an external shell command and added to the buffer:
:r !php _setup/getid/php item | tail -1
This works fine in normal mode. However, when I record a macro containing only the above command and then run it I get the error:
Could not open input file: _set
added to the buffer.
Does anyone know what's happening here?
vim shell macros
I have a list of items in a file, and I am trying to add an id on the line before each one. The id is generated by an external shell command and added to the buffer:
:r !php _setup/getid/php item | tail -1
This works fine in normal mode. However, when I record a macro containing only the above command and then run it I get the error:
Could not open input file: _set
added to the buffer.
Does anyone know what's happening here?
vim shell macros
vim shell macros
asked Nov 23 at 11:28
Simon Brahan
1112
1112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I was using tab completion to get the path to my script, which means the macro - literally just a recording of keystrokes - looked like gibberish.
Explicitly typing out the shell command resulted in a macro that worked.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I was using tab completion to get the path to my script, which means the macro - literally just a recording of keystrokes - looked like gibberish.
Explicitly typing out the shell command resulted in a macro that worked.
add a comment |
up vote
1
down vote
accepted
I was using tab completion to get the path to my script, which means the macro - literally just a recording of keystrokes - looked like gibberish.
Explicitly typing out the shell command resulted in a macro that worked.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I was using tab completion to get the path to my script, which means the macro - literally just a recording of keystrokes - looked like gibberish.
Explicitly typing out the shell command resulted in a macro that worked.
I was using tab completion to get the path to my script, which means the macro - literally just a recording of keystrokes - looked like gibberish.
Explicitly typing out the shell command resulted in a macro that worked.
answered Nov 23 at 14:00
Simon Brahan
1112
1112
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377785%2fvim-running-a-shell-command-fails-within-a-macro%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown