he/him, 🇨🇦
mise rules tho, replaced many version managers and direnv (so far)
mise rules tho, replaced many version managers and direnv (so far)
1. listing bookmarks locally (cleaning old ones out, etc)
2. viewing them on github (github.com/<ORG>/<REPO>/branches)
3. telling someone a branch name verbally - they're more likely to remember "refactor-foo" rather than "jjt/push-xuniuir" :)
1. listing bookmarks locally (cleaning old ones out, etc)
2. viewing them on github (github.com/<ORG>/<REPO>/branches)
3. telling someone a branch name verbally - they're more likely to remember "refactor-foo" rather than "jjt/push-xuniuir" :)
jj-fzf isn't a type of tool i use, but ppl seem to like them (as they do lazygit) - maybe they value staying in the terminal more than a superior experience of a GUI?
idk, could just be novelty?
jj-fzf isn't a type of tool i use, but ppl seem to like them (as they do lazygit) - maybe they value staying in the terminal more than a superior experience of a GUI?
idk, could just be novelty?
even optimal GUIs have disadvantages over TUIs when context is considered: staying in terminal, getting stdout/err, look/feel of terminal command
ex. of latter is github.com/tim-janik/jj... which prints mutative jj commands to "help users in learning the jj CLI"
even optimal GUIs have disadvantages over TUIs when context is considered: staying in terminal, getting stdout/err, look/feel of terminal command
ex. of latter is github.com/tim-janik/jj... which prints mutative jj commands to "help users in learning the jj CLI"
room treatment if feasible is worth it, at least first reflection points
room treatment if feasible is worth it, at least first reflection points
sidenote: they use the end of base36 for change ids to disambiguate the two, so commit digits are [0-f] (like git) but change ids are [z-k]
sidenote: they use the end of base36 for change ids to disambiguate the two, so commit digits are [0-f] (like git) but change ids are [z-k]
like in git if you wanted to see a change between last git commit and current state in working tree/index
like in git if you wanted to see a change between last git commit and current state in working tree/index
evolog is neat, like a mini branch for a given commit/change
i changed a file 3 times, evolog shows commits from jj snapshotting from that (usually happens w/ jj cmd invocation, i have watchman integration which does it every file change)
rich history without cruft in top-level
evolog is neat, like a mini branch for a given commit/change
i changed a file 3 times, evolog shows commits from jj snapshotting from that (usually happens w/ jj cmd invocation, i have watchman integration which does it every file change)
rich history without cruft in top-level
op log for repo history (jj undo/redo), working copy is a commit instead of index (no stash!), rebases always succeed, great revset language, lots to love
some rough edges here and there but colocated jj repos can use git interchangeably
op log for repo history (jj undo/redo), working copy is a commit instead of index (no stash!), rebases always succeed, great revset language, lots to love
some rough edges here and there but colocated jj repos can use git interchangeably
the discord is also full of helpful and welcoming people discord.gg/PUDv9rtT
the discord is also full of helpful and welcoming people discord.gg/PUDv9rtT
auto-local-bookmark config might replicate `git pull`? jj-vcs.github.io/jj/latest/co...
auto-local-bookmark config might replicate `git pull`? jj-vcs.github.io/jj/latest/co...
i love flash.nvim in treesitter mode to do visual selection then act
i love flash.nvim in treesitter mode to do visual selection then act
effect was there before (pick popular, stable, widespread tech) just accelerated now
effect was there before (pick popular, stable, widespread tech) just accelerated now
i often wonder if democracies would be better off disallowing polls
i often wonder if democracies would be better off disallowing polls