Doing `test && cmd` means that the command as a whole fails if the test
fails, which causes Fresh to think the hook failed. Using a proper
conditional (or suffixing `|| true`) would have done the trick.
This seems to have changed quite a bit since I was using this regularly
(~8 years ago) and in my testing today seems to create a situation where
every separate session is bound to the same active window. So, while it
created a new tmux window (tab) each time I connected, it unfortunately
kept all my Terminal windows/sessions in sync so I couldn't view two
different Tmux windows within the same session using two different
terminal windows.
This is really annoying at the end of a line when you might actually
mean _next line_. I'd rather hit TAB then ENTER to explicitly tab
through the auto-complete list.
Before I switched to Fresh, I assembled my dotfiles with my own script
that ensured this was set, but it is no longer set. I don't need the
dot files directory to be customisable, so I'll just hard-code the path
I _do_ prefer code in narrower style than long lines, but I have been
persuaded that 80 characters is too narrow on today's high-DPI,
wide-screen monitors. 120 is pushing it in terms of readability
nonetheless (lots of research to show that humans have difficulty
reading long lines, mostly because progressing to the next line can mean
we lose our place).
- CtrlSF for project-wide find and replace
- vim-visual-increment allows numbering a visually-selected column
incrementally
- vim-visual-multi gives multiple cursors at once allowing for easy
refactors of certain kinds
These were on my old laptop uncommitted so I don't remember why some of
these changes were made, but I trust they were probably done for a good
reason :)