6 commits

Author	SHA1	Message	Date
Stefan Haller	373b1970ca	Show divergence from base branch in branches list	2024-06-03 13:59:43 +02:00
Stefan Haller	5b613f5bc7	Remove ColoredBranchStatus and branchStatusColor ... Previously the entire status was colored in a single color, so the API made sense. This is going to change in the next commit, so now we must include the color in the string returned from BranchStatus(), which means that callers who need to do hit detection or measure the length need to decolorize it. While we're at it, switch the order of ↑3↓7 to ↓7↑3. For some reason that I can't really explain I find it more logical this way. The software out there is pretty undecided about it, it seems: VS Code puts ↓7 first, and so does the shell prompt that comes with git; git status and git branch -v put "ahead" first though. Shrug.	2024-06-03 13:02:46 +02:00
Stefan Haller	0aba686f97	Rename Pushables/Pullables to AheadForPull/BehindForPull ... In preparation for adding AheadForPush/BehindForPush in the next commit.	2024-05-19 09:44:38 +02:00
Stefan Haller	c59e6b6451	Cleanup: don't mess with globals in tests without resetting them ... Changing globals in the init() function of a test file is a bad idea, as it affects all other tests that run after it. Do it explicitly in each test function that needs it, and take care of restoring the previous value afterwards.	2024-03-29 10:55:33 +01:00
Stefan Haller	36e57d16bd	Don't try to shorten branch names that are already 3 characters or less ... This fixes a potential crash when the available width is very small and the branch name is one to three characters long.	2024-01-15 13:27:49 +01:00
Stefan Haller	c550737a4f	Truncate long branch names to make branch status visible	2023-10-16 13:15:05 +02:00