https://gitlab.synchro.net/main/sbbs/-/merge_requests/570#note_7594
Nope.. I was debugging something else
Something I do that helps prevent accidental changes from being included in commits is to *always* do a diff (or difftool or equivalent) before a commit (and before I write the commit message). That helps me to catch all the accidental/incidental changes and write better commit messages.
Re: DDMsgReader fix: Fix: When listing messages in lightbar mode in revers
By: Digital Man to Eric Oulashin on Sun Sep 07 2025 05:29 pm
Something I do that helps prevent accidental changes from being included in commits is to *always* do a diff (or difftool or equivalent) before a commit (and before I write the commit message). That helps me to catch all the accidental/incidental changes and write better commit messages.
Generally I do at work, though for my Synchronet stuff, I haven't been in the habit of doing that for some reason, but I should. I use Visual Studio (in Windows) a lot at work, and its Git integration shows all the files you've changed in the repo and lets you diff them, which is convenient; I'm wondering if there's something that does similar for Linux.
I usually will install perforce perge (p4merge, it's free) as a git diff viewer in a *nix environment, so running "git difftool" will use that instead of the normal text/diff view, if you prefer a GUI diff.
If you want a full git GUI (that does more than just diff viewing), there are a lot of options: gitk, gitkraken, Github Desktop, etc. And of course, there's Visual Studio Code (vscode) which runs in Linux and has plenty of git integration.
| Sysop: | CyberNix |
|---|---|
| Location: | London, UK |
| Users: | 26 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 19:43:40 |
| Calls: | 926 |
| Files: | 6,171 |
| D/L today: |
27 files (7,248K bytes) |
| Messages: | 917,549 |