Of course, you can also use other escape codes to make your commits colored (e.g. [92m for green), underlined ([4m), etc.
Or change the terminal title. ^[]0;title^G
Or for screen and tmux:
^[ktitle^[\Blinking Commits
91–100 of 105 posts
Re: Blinking Commits
#92Earlier quoted context omitted.
Terminal attacks are not new and the solution isn't to expect every individual program to escape terminal escape codes. The ideal solution is to sanitize all data before displaying it on your terminal, however without a custom terminal application or data filter, you can't guarantee that every tool you use on the command-line is going to strip escape sequences. The responsibility should rest on the actual terminal em…
no? I mean, it would be super nice for your terminal emulator to just automagically filter out escape sequences when you, the user, do not want them and to allow them for programs that you do. a whitelist would work but would be super annoying to actually verify as so many programs output things from so many different inputs. it seems like programs themselves should decide if they need to output arbitrary data and, i…
Automagically? The terminal emulator's job is to parse and interpret those sequences.
Re: Blinking Commits
#93All this talk about ASCII control codes and no one mentions 0x07 aka ␇?
Re: Blinking Commits
#94Earlier quoted context omitted.
If they did they'd have to wrap it a tag. Anything else would just be sacrilege
Unfortunately most browsers don't have support anymore
Well, then it fits; many terminal emulators don't support \e[5m as blink anymore. Xterm, URxvt, and Konsole do, but the Linux terminal doesn't (gives it a grey background, not blinking), VTE-based terminals (gnome-terminal, lxterminal, ...) don't (ignored), Emacs term-mode doesn't (treats it as bold).
Re: Blinking Commits
#95iTerm2 supports images in the terminal. May as well take this as far as it will go. https://iterm2.com/images.html Edit: even animated gifs
Ranger utilizes this well on (not just on iterm) http://ranger.nongnu.org/ - a VIM-style terminal-based file explorer via w3m.
Unfortunately only with iTerm2 it seems able to play animated gif.
Re: Blinking Commits
#96Earlier quoted context omitted.
I didn't downvote you. (Downvotes are heavily rate-limited, at a guess, from very unscientific observation, I think I only get ten a day, so I save them for the really annoying comments.) I'm not sure why you think he/his pronouns are nongendered. The nongendered pronouns in English are they/them.
You're continuing to controversialize and divert from the original conversation. That said... > I think I only get ten [downvotes] a day, so I save them for the really annoying comments. 10 downvotes a day? Please reconsider your behavior. You are almost certainly unnecessarily alienating commenters, and in this case, misguidedly so. > I'm not sure why you think he/his pronouns are nongendered. When I said "it was no…
On the matter of education, singular they is historically supported: https://en.wikipedia.org/wiki/Singular_they#Older_usage_by_r...
Re: Blinking Commits
#97I actually quite like the idea of control codes in commit messages for internal teams where you can implement rules. It could be useful for highlighting risky commits in red or other visual markers. Would play merry hell with almost every other way of viewing commits though :D
>I actually quite like the idea of control codes in commit messages for internal teams where you can implement rules.
>It could be useful for highlighting risky commits in red or other visual markers.
Yeah... that is really not a good idea. You are not supposed to take this blog post seriously.
Why not just agree on some terminology like CRITICAL/MINOR/SECURITY, which a visual interface can then highlight?
SECURITY: Fix XSS in spline reticulation
Re: Blinking Commits
#98Funny timing, with the recent "Terminal escape sequence XSS" post on oss-security in mind: http://www.openwall.com/lists/oss-security/2015/08/11/8
> So the basic TL;DR: please don't use really ancient terminal programs that are vulnerable to this stuff.
Disappointing that he would make this statement and then not bother to recommend specific ones to avoid and/or use.
Re: Blinking Commits
#99Earlier quoted context omitted.
You're continuing to controversialize and divert from the original conversation. That said... > I think I only get ten [downvotes] a day, so I save them for the really annoying comments. 10 downvotes a day? Please reconsider your behavior. You are almost certainly unnecessarily alienating commenters, and in this case, misguidedly so. > I'm not sure why you think he/his pronouns are nongendered. When I said "it was no…
On the matter of education, singular they is historically supported: https://en.wikipedia.org/wiki/Singular_they#Older_usage_by_r...
Yes. I'm aware. I was trying to be as terse as possible on the diverting topic. It's disputed whether past singular they was considered grammatically correct at the time, despite the source. Of course, then you have to define what it means to be "considered grammatically correct" and who decides that and now you're entering a whole subjective can of worms that turns into circular logic, leading back to the realization that language is largely cultural and expressive, not technical, unfortunately. All of these are reasons why there's not much room for a logical argument here, and only an appeal to emotion, bandwagoning, and some historical bad actors making the "generic he" untenable.
Still, the OC was factually incorrect and this entire topic is diverting and as you've now contributed to with your sanctimonious desire to prove me wrong, controversialized and alienating here on HN.
Re: Blinking Commits
#100You were more concerned with whether or not you could you never stopped to think whether or not you should
Nah, they just want to watch the world burn.