Another quick tip of something I use frequently in Terminal, is:
open .
Which will open the current directory in Finder.
So if you’re in /Users/Aston/Projects, it will open the Projects folder.
AstonJ
frankdugan3
In vim, you can change the current/next search match with cgn. It’s also repeatable with ., and you don’t even need to use n to advance if you know you want to replace the next match.
Bonus tip: * will start a search for the word under the cursor and jump to the next match.
5
hauleth
That is why I created GitHub - hauleth/sad.vim: Quick search and replace for Vim · GitHub, which is a plugin that utilises that functionality to provide repeatable replaces.
2
gmile
One small from me - I’ve added a function in my fish-shell that looks like this:
function dbg
set test_path $argv[1]
iex --dbg pry -S mix test $test_path --trace
end
Provided there’s a dbg() macro anywhere in the Elixir code under test, this allows me to enter an interactive debugging session quickly by going from:
mix test test/my_app/permissions/api_test.exs:627
to:
dbg test/my_app/permissions/api_test.exs:627
7
muelthe
sodapopcan
Dang, can’t believe I never knew this, thanks!
I like to remap * like so:
nnoremap <silent> * :let @/ = '\<' . expand('<cword>') . '\>'<bar>setlocal hlsearch<cr>
This set the search register to the current keyword under the cursor, turns on highlighting for the current buffer, and leaves the cursor in place. This works like an opt-in traces.vim that I find much less jarring. Incidentally, I leave # as-is. I can’t explain why but it’s just what feels right 
EDIT: I can explain 
It seems most of the time I’m not sure which way I’m looking, so remapping * this way gives me context. If I know for sure I want to go up then # just takes me to the first thing. Sometimes I know that I want to go down which means I have to press *n which is semi-annoying but not the worst.
2
Samjowen
If you’re ever doing a capture the flag challenge and you have managed to get onto the box, always make sure to check the terminal history. You might find a clue as to what to do next in the puzzle.
1
AstonJ
Now that I know where the file is I have created an alias for it 
alias bashhistory="mate ~/.zsh_history"
Something that would be handy is directory specific history - do you (or anyone) know if that’s possible?
0
eksperimental
I have been using this shell script for years to easily find the latest modified Git branches, specially when dealing with a crazy amount of branches per repo.
~/bin/git-branch-by-commit-date
#!/bin/bash
# Lists Git branches sorted by commit dates in descending order.
# Originally taken from: http://stackoverflow.com/questions/2514172/listing-each-branch-and-its-last-revisions-date-in-git/2514279#2514279
for k in $(git branch | perl -pe s/^..//);
do echo -e "$(git show --pretty=format:"%Cgreen%ci %Cblue%cr%Creset" "$k" -- | head -n 1)"\\\\t"$k";
done | sort -r
And the output looks like:
❯ git-branch-by-commit-date
2025-11-04 12:31:53 +0100 3 days ago main
2025-10-30 22:06:07 +0100 7 days ago chore/remove-br-deprecations
2025-10-30 08:18:13 -0500 7 days ago chore/update-mix-tasks-new-reserved-app-names
2025-10-29 01:06:47 -0500 9 days ago feature/mix-new-sample-code
2025-10-08 12:02:21 -0500 4 weeks ago chore/fix-spdx-summary
…
2025-07-09 23:08:13 -0500 4 months ago chore/use-commas-in-numbers
2025-05-09 21:01:53 -0500 6 months ago feature/ci-docs-warnings-as-errors
2025-05-09 21:00:06 -0500 6 months ago feature/makefile-docs-options
…
2023-05-12 08:43:45 -0500 2 years, 6 months ago improve-error-message-supervisor-child-spec
2018-12-06 13:07:49 +0100 7 years ago v1.3
4
Samjowen
I have never considered that before, but I have seen a few people hooking into PROMPT_COMMAND in bash to make some solutions. I see that you’re using zsh, so this might be of interest to you: https://superuser.com/questions/735660/whats-the-zsh-equivalent-of-bashs-prompt-command
I also saw this GitHub repo that looks useful, although it is for bash specifically: GitHub - wolfwoolford/dish: Store and retrieve directory specific shell history · GitHub
Finally, an interesting StackOverflow for you to check out for zsh specifically https://unix.stackexchange.com/questions/71189/per-directory-history-in-zsh.
1