Hacker News Reader

Comment by wodenokoto | Hacker News Reader

I have so many common one-liners I use in my current project (that I access using fuzzy search via ctr-R) that I'm thinking about having a file a'la "my-commands" and have it appended to my history, somehow.

That would truly be the opposite of this advice.

Maybe I need to think about this a bit more :)

View on HN

Shell aliases are your friend.

just give them some memorable names, and add them to your .bashrc. Or, if they are very context sensitive (that's not great), there is a way to source a file every time you enter a directory, I just don't remember it.

Shell functions do the same thing as aliases, and have fewer parsing problems, and they have more flexible arguments. Instead of:

    alias ls='ls --color'

Better:

    ls() {
      command ls --color "$@"
    }

(The "command" prefix avoids recursion)

Greenclips [1] works well for this if you're a rofi [2] user. You can set a staticHistoryPath that points to a file. When activating Greenclips, you can search for the desired command. I've been using this on my Linux box for the last year or so and haven't looked back.

[1] https://github.com/erebe/greenclip

[2] https://github.com/davatorium/rofi

I'm using navi (https://github.com/denisidoro/navi) for commands that long enough and used less frequently. And it works great.

There is a history command, with a way to reload, so this would be possible by writing to bash_history from bashrc, then reloading the history I think. Not tested.

This is a short guide that is an eye opener as to just how much can be done with bash history: https://www.digitalocean.com/community/tutorials/how-to-use-...

You can set up a per-directory bash history: https://unix.stackexchange.com/questions/305524/create-histo...

And a Makefile sounds like it'd be pretty helpful too!

Makefile!

You can also use direnv to add aliases when you enter a certain directory.

> have it appended to my history, somehow

isn't that what .aliases is for?

I honestly don’t know.

Reply on news.ycombinator.com