4 ms·

Or you could stick the command in a shell script. #!/bin/sh find . -iname '*.php' -print0 | xargs -0 -n1 php -l Save it to ~/bin/phplint (you do have ~/bi

• ibotty 13y ago
  no you are not. but some one-offs are good enough to reuse, but not good enough to open an editor for, depend on environment variables (which might be spelled out in the command), or something. so although i do use a pretty well populated ~/bin (well ~/usr/bin) and many shell functions, i will adopt that practice. it might even work out for script files (i.e. recordings of your shell session).
  • drdaeman 13y ago
    > not good enough to open an editor for It's just a keystroke away (`C-x C-e` in bash and zsh, in emacs-like line editing mode) if you have $EDITOR set properly.
    • ibotty 13y ago
      that's interesting. i did not know that shortcut (well, it doesn't work with vi keybindings), but that sounds useful. that was not the whole point though.
      • kragniz 13y ago
        Using vi keybindings, <esc>v does the same.
        • ibotty 13y ago
          not in my zsh.
• zaptheimpaler 13y ago
  I think this approach is cleaner and you have the added advantage of having a permanent stash of useful commands you can move around systems. Personally, I would use the hashtags, and also use something like inotify to automatically add any hashtagged commands to seperate scripts and store them in something like ~/usr/bin/custom/
  • pyre 13y ago
    It depends on how large your shell history is. I often have useful commands scrolled out of my history just because I got busy doing something orthogonal that involved a lot of shell commands.
• twic 13y ago
  What you may be missing is the difference in length between: Create a file ~/bin/phplint Type out the shebang Copy the command from the terminal into the file Save the file chmod +x the file And: type #phplint I'm sure Mr Venkat wouldn't claim that he has rendered script directories overnight. But he has come up with a way to make your shell history a little more usable. I observe that people vary a lot in how hard they lean on their history. I live and die by mine; it serves as a combination of replacement short-term memory and treasury of tricks. Some of my colleagues don't really use it at all, using scripts or aliases, or even just retyping commands every time, like savages. If you're not a heavy user of history, then this idea won't help you. If you are, it might.
  • mooism2 13y ago
    You're right, the first alternative is disgustingly long-winded. Let's automate it. Create a new shell script called `empty` somewhere on your PATH: #!/bin/bash set -e exec >"$1" printf '#!' which "$2" chmod +x "$1" cat Next, add a new shell function to your ~/.bashrc: save-history() { history -p "$1" | empty ~/bin/"$2" bash } To save the most recent command in your history to a shell script called ~/bin/phplint, run save-history '!!' phplint You have to single-quote the '!!'; sorry about that. I'm using bash; maybe zsh has some way of making this easier to use. Having said that, if you're happy (I'm speaking generically here, not specifically to twic) relying on your history, then more power to you. It doesn't work for me because I haven't worked out yet how to keep my shell history straight between several shell sessions on the same PC, let alone syncing it between different PCs.
    • jpk 13y ago
      In the spirit of the OP, I did a similar thing, but using a tag to initiate writing the script file. https://github.com/thatjpk/bashtag-save https://github.com/thatjpk/bashtag-save So, tagging a command line with "#save:scriptname" will save the command to ~/scripts/saved/scriptname.sh That way you can get the history search token and a script on disk in one fell swoop.
• samatman 13y ago
  What you are describing is persisting a command; the parent article describes a caching technique. Caching a name for a command, as you issue it, makes it easier to retrieve later if you decide you want it as a proper script or alias. Among other things.