4 ms·
It's already egregious when a site adds history pushState entries for just clicking through a gallery or something, but wow adding them just for scrolling down
by llm_nerd 2y ago
It's already egregious when a site adds history pushState entries for just clicking through a gallery or something, but wow adding them just for scrolling down on a page is simply bizarre, especially on a page about usability.
- nottorp 2y agoIt's in the spirit of adding emojis to compiler output...
- ender341341 2y agoI actually quite like the emojis they put in the output, it helps alleviate the balance of providing enough context while also giving a clear visual indicator for the actual error message. They aren't going overboard on it, they just put a warning emoji in front of the error message.
- nottorp 2y agoHow do you grep for it without taking your hands off the keyboard?
- perching_aix 2y agoWindows key + dot, then type in warning / if it was among the last ones you used, use the arrow keys, and hit Enter to insert it. If you use whatever OS other than Windows, I'm sure there are similar flows available if you search for it. And since it's just Unicode, I'm sure there are numpad based keybinds available too.
- nottorp 2y agowhy shouldn't i just type grep warning instead of bringing up some GUI that possibly takes forever to initialize? how does it work over ssh? :)
- johnisgood 2y agoIt makes too much sense.
- alisonatwork 2y agoEmoji selector is fast and works perfectly fine over SSH, it's no different to any other input method that needs to use characters beyond 7-bit ASCII. grep is a bit more iffy. UNIX command line tools seem to be a bit of a crapshoot in how or if they support Unicode, especially if you switch between different systems like Linux, BSD, Cygwin etc. You might need a bit of experimenting with the LANG variable to get it work (e.g. Git Bash on Windows needs LANG=C.UTF16 to match an emoji). I've also had cases where grep or sed works, but awk doesn't, or vice versa. On the whole it works a lot better nowadays than it used to, though, and that's a win for non-English users of the command line as well as emoji fans.
- nottorp 2y ago> that's a win for non-English users of the command line I am non english. I use ăâîșț. When writing a text document for humans. I also use :) but not . I'm still of the opinion that anything not 7-bit ascii doesn't belong in something that may be machine processed. Which includes compiler output. Edit: hey, HN erased my emoji. The dot was supposed to be the :) emoji style.
- alisonatwork 2y agoDidn't you ever grep a text document written in a language other than English? No processing of CSV files in different charsets? Not even encountered a file with a non-English character in the name? Not to mention the folks who deliberately set LANG so that their compiler and everything else will give them localized error messages. This stuff was all much worse 25 years ago, even 15 years ago. Like them or not, I do think emojis have helped drive forward much better Unicode handling across the whole stack, including the command line.
- nottorp 2y ago
- yazantapuz 2y agoTIL that winkey+dot in kde launchs the emoji selector ... but it is copied into the clipboard, so more keystrokes
- nottorp 2y agoAt least i didn't get a link to an youtube tutorial as an answer :)