4 ms·

Emoji 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

Emoji 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 ago
  Didn'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
    > Didn't you ever grep a text document written in a language other than English? Yes but it was for humans originally? Not for machine processing. > Not to mention the folks who deliberately set LANG so that their compiler and everything else will give them localized error messages. The horror! Who even works on translations for compiler error messages ?!? It makes absolutely no sense! Next they'll want to localize programming language keywords. I wonder how well that will work at this current project of mine that has people native to 3 countries, none english speaking ...
    - perching_aix 2y ago
      It's not a next, but more a previously :) Localized development tooling is an old timer thing.
      - nottorp 2y ago
        How old? I'm old enough that my first Linux experience included a stack of floppy disks and recompiling a 0.9x kernel in late high school, and my first c++ program was done with Borland C++ 3.1. It never occured to me to look for a localized UI for either of them. Older than that?

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 ago
Didn'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
  > Didn't you ever grep a text document written in a language other than English? Yes but it was for humans originally? Not for machine processing. > Not to mention the folks who deliberately set LANG so that their compiler and everything else will give them localized error messages. The horror! Who even works on translations for compiler error messages ?!? It makes absolutely no sense! Next they'll want to localize programming language keywords. I wonder how well that will work at this current project of mine that has people native to 3 countries, none english speaking ...
  - perching_aix 2y ago
    It's not a next, but more a previously :) Localized development tooling is an old timer thing.
    - nottorp 2y ago
      How old? I'm old enough that my first Linux experience included a stack of floppy disks and recompiling a 0.9x kernel in late high school, and my first c++ program was done with Borland C++ 3.1. It never occured to me to look for a localized UI for either of them. Older than that?