poll: if you use Git, do you use a terminal text editor to edit your commit messages? (or other things that Git asks you to edit like interactive rebases etc)
(you can pick more than one)
Discussion
poll: if you use Git, do you use a terminal text editor to edit your commit messages? (or other things that Git asks you to edit like interactive rebases etc)
(you can pick more than one)
@b0rk _nearly_ got to tick all the boxes! I use emacs, but depending on the circumstances, it might be an emacs launched specially when I run 'git commit' from the shell prompt, or I may be running Magit in an emacs I had already. In either case the emacs may be GUI or tty-only, depending on whether I'm doing it at the other end of an ssh connection.
Alas, I couldn't think of any excuse to tick the 'other' box too :-)
(I do have a completely daft trick where I set VISUAL="cp file.txt", causing git to use the contents of that pre-prepared file instead of spawning an editor. But I only use that for prewritten 'git rebase -i' lists. For commit messages, there's no need: 'git commit' has a perfectly good -F option.)
That's horrible (complement).
(I'd be *way* too nervous to do that, and would just have the editor insert the prewritten text, though.)
@suetanvil @b0rk the usual reason I'm providing a prewritten 'git rebase -i' list in the first place is so I can try it over and over again until I get it right. For the same reason, I usually also make a separate clone of the git repo to do it in, so that I can mess up the first 10 attempts without doing any permanent damage!
Ah, okay. That sounds perfectly reasonable and slightly disappointing.
@b0rk I currently use gitui which is a TUI, which is perhaps not the same thing as a GUI? If I'm writing a longer commit message I'll open it in a terminal text editor, currently micro.