After the emoji, the blinking... Will git commits become like the 2000s web? :p
Wait 'till someone figures out he/she can store a webpage inside commit message.
and wait 'till someone figures out they can store ads inside commit messages.
Blinking Commits
71–80 of 105 posts
Re: Blinking Commits
#72Surely, there is a way to do this in Sublime?
Re: Blinking Commits
#73This is a really entertaining writing style: technical enlightenment through demonstration via humorous examples. For the lazy (and additional humorous demonstration), I wish he'd provided an example gif showing it in action (i.e., Github, terminal, Sourcetree, etc...).
(The terminal would be the only place it would display correctly it seems, but it would be nice to see the chaos it may or may not cause in Github and other tools.)
Finding someone who can write very technically while also being funny and charismatic is pretty rare (We computer types aren't always the biggest hits at parties). I also really appreciate his "last time on" opening paragraphs... it gives some context to the blog post and where's coming from in his headspace. Neat.
Re: Blinking Commits
#74Earlier quoted context omitted.
"XSS has nothing to do with {my website framework}, it just applies javascript that work anywhere in a compatible browser." Actually it has something to do with git. Git should strip or escape the user input before displaying. XSS and SQL Injections are the same kind of issue -> do not trust the user input and escape the input before interaction with it happens.
I see your point, and I agree. The OP didn't mention that aspect, but yes, git is darned crappy software, repeating stupid mistakes that are long forgotten elsewhere. Some developers don't seem to be learning from past mistakes.
> git is darned crappy software
Let's not go crazy now.
Re: Blinking Commits
#75Surely, there is a way to do this in Sublime?
If you can insert the ESC character, u001B, it's easy. (Though note that it appears as the two characters ^[ in the blog post, so your code should start ESC[5m with only one bracket.)
Unfortunately Sublime wasn't happy with me trying to type it through the Mac Unicode Hex input, but I was able to copy-paste it in, and I was also able to enter it directly in other programs, like GitHub desktop.
Re: Blinking Commits
#76This is a really entertaining writing style: technical enlightenment through demonstration via humorous examples. For the lazy (and additional humorous demonstration), I wish he'd provided an example gif showing it in action (i.e., Github, terminal, Sourcetree, etc...).
The author uses female pronouns.
Re: Blinking Commits
#77 git commit -F Re: Blinking Commits
#78Re: Blinking Commits
#79Has nothing to do with git, or committing, it just applies VT100 control codes that work anywhere in a compatible terminal.
"XSS has nothing to do with {my website framework}, it just applies javascript that work anywhere in a compatible browser." Actually it has something to do with git. Git should strip or escape the user input before displaying. XSS and SQL Injections are the same kind of issue -> do not trust the user input and escape the input before interaction with it happens.
Why would git strip formatting from my message? If my team wants colorful messages why should git be the one to say we're wrong?
Git commit messages are used for lots of different things, but at the end of the day it's just another piece of data included in a hash in a content-addressable file system.
If you're doing something with that tool where including formatting like this would be considered a vulnerability, it's on you to take care of that. It's exactly the same with any other bug or exploit in your codebase: it's not git's fault that you committed it.
Re: Blinking Commits
#80Earlier quoted context omitted.
"XSS has nothing to do with {my website framework}, it just applies javascript that work anywhere in a compatible browser." Actually it has something to do with git. Git should strip or escape the user input before displaying. XSS and SQL Injections are the same kind of issue -> do not trust the user input and escape the input before interaction with it happens.
Why would git strip formatting from my message? If my team wants colorful messages why should git be the one to say we're wrong? Git commit messages are used for lots of different things, but at the end of the day it's just another piece of data included in a hash in a content-addressable file system. If you're doing something with that tool where including formatting like this would be considered a vulnerability, it…
If you need to have this feature, then you should have to opt in (git config for example). But i have very good reasons to say that the default should properly escape the messages before printing them. I would not like it to clone a repo from github and having "git log" let my terminal go crazy. You unterstand, that this issue can have bigger impact than blinking commit messages, right?