Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blinking Commits

blog.annharter.com

Post reply on HN
Print view View original

41–50 of 105 posts

Re: Blinking Commits

#41

Post by dantillberg »

im3w1l wrote: post #21

Haha, what a coincidence. Just the other day we discussed string special cases[0][1], to which I contributed ansi escapes. Unicode "fonts" 𝓵𝓲𝓴𝓮 𝖙𝖍𝖎𝖘 seem to work in commit messages as well. I think this is quite harmful, especially the character movement ansi escapes could be used for nefarious purposes. [0] https://news.ycombinator.com/item?id=10035008 [1] https://github.com/minimaxir/big-list-of-naughty-str…

I recently had to write some code[0] that handles strings of UTF-8 with ANSI color escapes sprinkled throughout.

A fun exercise is to write a function that overwrites string A with string B, starting at index N. It's hard enough with unicode, but ANSI escapes make it more fun.

[0]: https://github.com/tillberg/ansi-log (Go logging library with support for ANSI colors and interleaving multiple writers)

Re: Blinking Commits

#42

Post by caf »

GuiA wrote: post #3

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

Re: Blinking Commits

#43

Post by awendt »

Perceptes wrote: post #37

This works for me in OS X's built-in Terminal app, but not iTerm. Both report xterm-256color as $TERM, so I'm not sure what about iTerm is configured differently to prevent it from working there.

same here

Re: Blinking Commits

#45

Post by rquirk »

erikb wrote: post #30

Doesn't work in my gnome-terminal. Looks like the commands get escaped by git somehow. Did anybody test it?

Doesn't work on Xfce either. On a virtual terminal thingy (ctrl-alt-f1) it shows a grey background with white text. I suspect blink is only implemented on the Mac's terminal, not in Linux-land.

Re: Blinking Commits

#47

Post by thechriswalker »

Perceptes wrote: post #37

This works for me in OS X's built-in Terminal app, but not iTerm. Both report xterm-256color as $TERM, so I'm not sure what about iTerm is configured differently to prevent it from working there.

iTerm2 has an option in your Profile: Text tab > Text Rendering: "Blinking Text Allowed"

Off by default; enable and blink like its 1989.

Re: Blinking Commits

#48

Post by HerraBRE »

mahouse wrote: post #36
fit2rule wrote: post #34

Earlier quoted context omitted.

Just yesterday I ran across this example: "(っ˘▽˘)っ :cloud: ⊂(◕。◕⊂)" in the Parse SDK repo, which I found especially distracting, and in general, kind of turned me off from the project (even though I know Parse is awesome). I agree that UTF and special-chars should be permissable; I don't agree that if they don't actually communicate something, they should be used anyway. Maybe this cute 'moticon trend is trendy, but…

I personally just find the committer to be immature, nothing else.

Immature to one is playful to another. :-)

It's all going to depend on the team; it would be a mistake to conflate seriousness with competence.

Re: Blinking Commits

#49

Post by baghira »

rquirk wrote: post #45
erikb wrote: post #30

Doesn't work in my gnome-terminal. Looks like the commands get escaped by git somehow. Did anybody test it?

Doesn't work on Xfce either. On a virtual terminal thingy (ctrl-alt-f1) it shows a grey background with white text. I suspect blink is only implemented on the Mac's terminal, not in Linux-land.

It does work in urxvt and konsole (and there's an option to turn it off). And as tempodox said, this is just VT100 stuff.
Post reply on HN