3 ms·
tl;dr
by mjd 6y ago
tl;dr
- gruez 6y agoI was going to downvote this but after skimming the article I'm inclined to agree. There's no intro/conclusion summarizing what the post is about, and without them the body is just a stream of consciousness that's hard to follow and unengaging.
- loloquwowndueo 6y agoThere is a conclusion at the end if you bother to scroll down ;)
- chrisweekly 6y agoTLDR "Some first-draft-quality notes on incorporating git-related info into the shell prompt"
- 0zymandiass 6y agoIt's far less interesting than finding an exploit in git-shell, which was how I read the headline :|
- chrisweekly 6y agoyeah. that's why I posted the (sadly, downvoted) tldr you responded to: trying to help others avoid wasting time on the OP.
- rgoulter 6y agoThe author likes using long branch names, except for that this makes their prompt look ugly. One workaround they've used is to use a shorter branch name locally which tracks the longer remote branch name. This blogpost shows details about looking into abbreviating the branch name in the shell code for the git part of the prompt. The author found a way to do it by making use of a particular colorising hook.