Viewing man pages in vim











up vote
5
down vote

favorite












I wrote a function in bash to see manpages in vim



viman () { man "$@" | vim -R +":set ft=man" - ; }


This works fine, the only problem occurs if I pass a manpage to it which doesn't exist. It prints that the manpage doesn't exist but still opens vim with an empty buffer.

So, I changed the function to check the error code ( which is 16 here ) and exit if the manpage doesn't exist. The modefied function looks somewhat like this -



viman () { man "$@" | [[ $? == 16 ]] && exit 1 | vim -R +":set ft=man" -  ; }


But, now it doesn't do anything!!



I just want to quit the program if the manpage doesn't exist otherwise open the manpage with vim










share|improve this question




























    up vote
    5
    down vote

    favorite












    I wrote a function in bash to see manpages in vim



    viman () { man "$@" | vim -R +":set ft=man" - ; }


    This works fine, the only problem occurs if I pass a manpage to it which doesn't exist. It prints that the manpage doesn't exist but still opens vim with an empty buffer.

    So, I changed the function to check the error code ( which is 16 here ) and exit if the manpage doesn't exist. The modefied function looks somewhat like this -



    viman () { man "$@" | [[ $? == 16 ]] && exit 1 | vim -R +":set ft=man" -  ; }


    But, now it doesn't do anything!!



    I just want to quit the program if the manpage doesn't exist otherwise open the manpage with vim










    share|improve this question


























      up vote
      5
      down vote

      favorite









      up vote
      5
      down vote

      favorite











      I wrote a function in bash to see manpages in vim



      viman () { man "$@" | vim -R +":set ft=man" - ; }


      This works fine, the only problem occurs if I pass a manpage to it which doesn't exist. It prints that the manpage doesn't exist but still opens vim with an empty buffer.

      So, I changed the function to check the error code ( which is 16 here ) and exit if the manpage doesn't exist. The modefied function looks somewhat like this -



      viman () { man "$@" | [[ $? == 16 ]] && exit 1 | vim -R +":set ft=man" -  ; }


      But, now it doesn't do anything!!



      I just want to quit the program if the manpage doesn't exist otherwise open the manpage with vim










      share|improve this question















      I wrote a function in bash to see manpages in vim



      viman () { man "$@" | vim -R +":set ft=man" - ; }


      This works fine, the only problem occurs if I pass a manpage to it which doesn't exist. It prints that the manpage doesn't exist but still opens vim with an empty buffer.

      So, I changed the function to check the error code ( which is 16 here ) and exit if the manpage doesn't exist. The modefied function looks somewhat like this -



      viman () { man "$@" | [[ $? == 16 ]] && exit 1 | vim -R +":set ft=man" -  ; }


      But, now it doesn't do anything!!



      I just want to quit the program if the manpage doesn't exist otherwise open the manpage with vim







      bash vim man function






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 4 hours ago









      Jeff Schaller

      37.5k1052121




      37.5k1052121










      asked 4 hours ago









      Ritajit Kundu

      315




      315






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          4
          down vote



          accepted










          Try this: capture the man output, and if successful launch vim



          viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man" - ; }





          share|improve this answer





















          • Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
            – Ritajit Kundu
            4 hours ago




















          up vote
          3
          down vote













          I like the idea of checking the man return code; you can't pipe to the test, though. You could just run man twice:



          viman () { man "$@" >/dev/null 2>&1 && man "$@" | vim -R +":set ft=man" - ; }


          This runs man ... | vim ... only if the first invocation of man was successful.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            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',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2funix.stackexchange.com%2fquestions%2f487415%2fviewing-man-pages-in-vim%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            4
            down vote



            accepted










            Try this: capture the man output, and if successful launch vim



            viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man" - ; }





            share|improve this answer





















            • Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
              – Ritajit Kundu
              4 hours ago

















            up vote
            4
            down vote



            accepted










            Try this: capture the man output, and if successful launch vim



            viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man" - ; }





            share|improve this answer





















            • Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
              – Ritajit Kundu
              4 hours ago















            up vote
            4
            down vote



            accepted







            up vote
            4
            down vote



            accepted






            Try this: capture the man output, and if successful launch vim



            viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man" - ; }





            share|improve this answer












            Try this: capture the man output, and if successful launch vim



            viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man" - ; }






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 4 hours ago









            glenn jackman

            49.9k569106




            49.9k569106












            • Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
              – Ritajit Kundu
              4 hours ago




















            • Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
              – Ritajit Kundu
              4 hours ago


















            Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
            – Ritajit Kundu
            4 hours ago






            Capturing the output in a text is a simple and brilliant idea. Putting all things together the viman function is ready - viman () { text=$(man "$@") && echo "$text" | vim -R +":set ft=man nomod nonu noma nolist colorcolumn=" - ; }
            – Ritajit Kundu
            4 hours ago














            up vote
            3
            down vote













            I like the idea of checking the man return code; you can't pipe to the test, though. You could just run man twice:



            viman () { man "$@" >/dev/null 2>&1 && man "$@" | vim -R +":set ft=man" - ; }


            This runs man ... | vim ... only if the first invocation of man was successful.






            share|improve this answer



























              up vote
              3
              down vote













              I like the idea of checking the man return code; you can't pipe to the test, though. You could just run man twice:



              viman () { man "$@" >/dev/null 2>&1 && man "$@" | vim -R +":set ft=man" - ; }


              This runs man ... | vim ... only if the first invocation of man was successful.






              share|improve this answer

























                up vote
                3
                down vote










                up vote
                3
                down vote









                I like the idea of checking the man return code; you can't pipe to the test, though. You could just run man twice:



                viman () { man "$@" >/dev/null 2>&1 && man "$@" | vim -R +":set ft=man" - ; }


                This runs man ... | vim ... only if the first invocation of man was successful.






                share|improve this answer














                I like the idea of checking the man return code; you can't pipe to the test, though. You could just run man twice:



                viman () { man "$@" >/dev/null 2>&1 && man "$@" | vim -R +":set ft=man" - ; }


                This runs man ... | vim ... only if the first invocation of man was successful.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 1 hour ago

























                answered 4 hours ago









                Jeff Schaller

                37.5k1052121




                37.5k1052121






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • 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%2funix.stackexchange.com%2fquestions%2f487415%2fviewing-man-pages-in-vim%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

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    TypeError: fit_transform() missing 1 required positional argument: 'X'