Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As others have mentioned, the usual way to do that would be to store your long commands as either aliases or bash functions. A nice way to organise them would the to put them all in a file (say <code>$HOME/.custom_funcs</code>) then source it from <code>.bashrc</code>.</p> <p>If you <em>really really</em> want to be able to load commands into your bash history, you can use the <code>-r</code> option of the <code>history</code> command. </p> <p>From the <a href="http://ss64.com/bash/history.html" rel="nofollow">man page</a>:</p> <pre><code>-r Read the current history file and append its contents to the history list. </code></pre> <p>Just store all your entries in a file, and whenever you need your custom history loaded simply run <code>history -r &lt;your_file&gt;</code>. </p> <p>Here's a demo:</p> <pre><code>[me@home]$ history | tail # see current history 1006 history | tail 1007 rm x 1008 vi .custom_history 1009 ls 1010 history | tail 1011 cd /var/log 1012 tail -f messages 1013 cd 1014 ls -al 1015 history | tail # see current history [me@home]$ cat $HOME/.custom_history # content of custom history file echo "hello world" ls -al /home/stack/overflow (cd /var/log/messages; wc -l *; cd -) [me@home]$ history -r $HOME/.custom_history # load custom history [me@home]$ history | tail # see updated history 1012 tail -f messages 1013 cd 1014 ls -al 1015 history | tail # see current history 1016 cat .custom_history 1017 history -r $HOME/.custom_history 1018 echo "hello world" 1019 ls -al /home/stack/overflow 1020 (cd /var/log/messages; wc -l *; cd -) 1021 history | tail # see updated history </code></pre> <p>Note how entries <code>1018-1020</code> weren't actually run but instead were loaded from the file. </p> <p>At this point you can access them as you would normally using the <code>history</code> or <code>!</code> commands, or the <kbd>Ctrl</kbd>+<kbd>r</kbd> shortcuts and the likes.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I add certain commands to .bash_history permanently?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USShawn Chin
    1. USShawn Chin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I add certain commands to .bash_history permanently?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for the tip. I vaguely remember reading somewhere adding certain character (& or something else) before a command can make bash to remember the command forever. I am looking for that answer. If I don't get that answer then I will use the approach you gave.
      singulars
      1. PO
      1. USMahesh
    2. COI'm not aware of such a functionality, so I'd be interested to know if your do find something like that :) If you can't find such a feature, you can still get close to that behaviour by creating a function that appends commands to the custom history file. Good luck.
      singulars
      1. PO
      1. USShawn Chin
    3. COGreat answer. The only thing I'd add is, "... aliases, bash functions, *or scripts*.".
      singulars
      1. PO
      1. USDan Moulding
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload