> The directory where you ran the command.

I love that mode in Atuin. I can never remember which of the run commands to use between make/cmake/bazel/yarn/npm/uv and hitting ctrl-r twice and scrolling up is better than having to root around in a readme, which I may or may not have bothered to write for my future self.

http://atuin.sh/

McFly sounds interesting! Added it to my list of things to investigate. Does it do multi-machine syncing?

▲

skydhash 3 days ago | parent [-]

You can settle on make (or just) and have consistent targets like run, test, build, deploy, etc….

I use emacs, so I have compilation buffers for those.

	▲	fragmede 3 days ago \| parent [-]
		Oh I forgot about "just"! (and I have Opinions about that name.) Add that to the list. Making order from chaos is not unfamiliar to me. Previously I standardized on make and was fastidious about making makefiles, but with atuin, command directory history the extra effort to create makefiles became superfluous. I used to have this fantasy that after I die, someone will care enough to go through my ~/projects folder and go through everything I worked on, and all those makefiles and readmes were going to help them, but no one cares that much for me. I'm okay with that, depressing as it is.