VIM - running a shell command fails within a macro












0














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?










share|improve this question



























    0














    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?










    share|improve this question

























      0












      0








      0







      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?










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 11:28









      Simon Brahan

      1112




      1112






















          1 Answer
          1






          active

          oldest

          votes


















          1














          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.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            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

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            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.






            share|improve this answer


























              1














              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.






              share|improve this answer
























                1












                1








                1






                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.






                share|improve this answer












                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.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 23 '18 at 14:00









                Simon Brahan

                1112




                1112






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    AnyDesk - Fatal Program Failure

                    How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

                    QoS: MAC-Priority for clients behind a repeater