cycle through reverse search in a custom command history file in bash

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I added a line to ~/.bashrc file which appends all issued commands to ~/.bash_eternal_history file in a date directory history-number command format, such as:



 2019-01-08.23:59:32 /home/sport/Desktop 745 pwd


I need a reverse-i-search feature to bring up commands from my custom history file ~/.bash_eternal_history searching key words and cycle through each result one by one using up or down keys



How can I achieve that?










share|improve this question


























    1















    I added a line to ~/.bashrc file which appends all issued commands to ~/.bash_eternal_history file in a date directory history-number command format, such as:



     2019-01-08.23:59:32 /home/sport/Desktop 745 pwd


    I need a reverse-i-search feature to bring up commands from my custom history file ~/.bash_eternal_history searching key words and cycle through each result one by one using up or down keys



    How can I achieve that?










    share|improve this question
























      1












      1








      1








      I added a line to ~/.bashrc file which appends all issued commands to ~/.bash_eternal_history file in a date directory history-number command format, such as:



       2019-01-08.23:59:32 /home/sport/Desktop 745 pwd


      I need a reverse-i-search feature to bring up commands from my custom history file ~/.bash_eternal_history searching key words and cycle through each result one by one using up or down keys



      How can I achieve that?










      share|improve this question














      I added a line to ~/.bashrc file which appends all issued commands to ~/.bash_eternal_history file in a date directory history-number command format, such as:



       2019-01-08.23:59:32 /home/sport/Desktop 745 pwd


      I need a reverse-i-search feature to bring up commands from my custom history file ~/.bash_eternal_history searching key words and cycle through each result one by one using up or down keys



      How can I achieve that?







      bash awk grep command-history bash-functions






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 8 at 21:16









      kennkenn

      3111617




      3111617




















          1 Answer
          1






          active

          oldest

          votes


















          2














          This, from man bash:



           HISTFILE
          The name of the file in which command history is saved (see HISTORY below). The default value is
          ~/.bash_history. If unset, the command history is not saved when a shell exits.
          HISTFILESIZE
          The maximum number of lines contained in the history file. When this variable is assigned a value,
          the history file is truncated, if necessary, to contain no more than that number of lines by remov‐
          ing the oldest entries. The history file is also truncated to this size after writing it when a
          shell exits. If the value is 0, the history file is truncated to zero size. Non-numeric values
          and numeric values less than zero inhibit truncation. The shell sets the default value to the
          value of HISTSIZE after reading any startup files.





          share|improve this answer























          • Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

            – kenn
            Jan 9 at 10:07











          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',
          autoActivateHeartbeat: false,
          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%2f493333%2fcycle-through-reverse-search-in-a-custom-command-history-file-in-bash%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









          2














          This, from man bash:



           HISTFILE
          The name of the file in which command history is saved (see HISTORY below). The default value is
          ~/.bash_history. If unset, the command history is not saved when a shell exits.
          HISTFILESIZE
          The maximum number of lines contained in the history file. When this variable is assigned a value,
          the history file is truncated, if necessary, to contain no more than that number of lines by remov‐
          ing the oldest entries. The history file is also truncated to this size after writing it when a
          shell exits. If the value is 0, the history file is truncated to zero size. Non-numeric values
          and numeric values less than zero inhibit truncation. The shell sets the default value to the
          value of HISTSIZE after reading any startup files.





          share|improve this answer























          • Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

            – kenn
            Jan 9 at 10:07
















          2














          This, from man bash:



           HISTFILE
          The name of the file in which command history is saved (see HISTORY below). The default value is
          ~/.bash_history. If unset, the command history is not saved when a shell exits.
          HISTFILESIZE
          The maximum number of lines contained in the history file. When this variable is assigned a value,
          the history file is truncated, if necessary, to contain no more than that number of lines by remov‐
          ing the oldest entries. The history file is also truncated to this size after writing it when a
          shell exits. If the value is 0, the history file is truncated to zero size. Non-numeric values
          and numeric values less than zero inhibit truncation. The shell sets the default value to the
          value of HISTSIZE after reading any startup files.





          share|improve this answer























          • Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

            – kenn
            Jan 9 at 10:07














          2












          2








          2







          This, from man bash:



           HISTFILE
          The name of the file in which command history is saved (see HISTORY below). The default value is
          ~/.bash_history. If unset, the command history is not saved when a shell exits.
          HISTFILESIZE
          The maximum number of lines contained in the history file. When this variable is assigned a value,
          the history file is truncated, if necessary, to contain no more than that number of lines by remov‐
          ing the oldest entries. The history file is also truncated to this size after writing it when a
          shell exits. If the value is 0, the history file is truncated to zero size. Non-numeric values
          and numeric values less than zero inhibit truncation. The shell sets the default value to the
          value of HISTSIZE after reading any startup files.





          share|improve this answer













          This, from man bash:



           HISTFILE
          The name of the file in which command history is saved (see HISTORY below). The default value is
          ~/.bash_history. If unset, the command history is not saved when a shell exits.
          HISTFILESIZE
          The maximum number of lines contained in the history file. When this variable is assigned a value,
          the history file is truncated, if necessary, to contain no more than that number of lines by remov‐
          ing the oldest entries. The history file is also truncated to this size after writing it when a
          shell exits. If the value is 0, the history file is truncated to zero size. Non-numeric values
          and numeric values less than zero inhibit truncation. The shell sets the default value to the
          value of HISTSIZE after reading any startup files.






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 8 at 21:55









          wefwef

          30414




          30414












          • Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

            – kenn
            Jan 9 at 10:07


















          • Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

            – kenn
            Jan 9 at 10:07

















          Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

          – kenn
          Jan 9 at 10:07






          Thank you for your answer. I didn't know that trick, I can use it as a last resort. But I thought of some awk, grep, sed etc. functions triggered by up or down keys.

          – kenn
          Jan 9 at 10:07


















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493333%2fcycle-through-reverse-search-in-a-custom-command-history-file-in-bash%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

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay