not particularly? define "character"...
i think Apple/Swift is the only major proponent of "character ==
extended grapheme
cluster[https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries]";?
plan 9's wc used `-r` (for "rune") to make it clearer that it was
counting code points. coreutil
i'd argue that env(1)'s name has mislead you --- it's most _commonly_
used just for the "do a $PATH lookup" side-effect, so a shell script
only has assume that it knows where _env_ lives, without having to
assume that it knows where (say) python lives. so `#!/usr/bin/env
python` rather than `#!/usr
On Fri, Sep 1, 2023 at 6:59 AM Chet Ramey wrote:
>
> On 8/31/23 5:15 PM, Eric Blake wrote:
>
>
> > It's not hard to see why POSIX is choosing to have Issue 8 obsoleting
> > (not removing) %b's old semantics; in the short term, nothing about %b
> > changes, so your dusty-deck shell scripts will con
On Tue, Sep 5, 2023 at 4:31 PM Rob Landley wrote:
>
> On 9/5/23 15:44, Chet Ramey wrote:
> > On 9/5/23 4:32 PM, Dragan Simic wrote:
> >> On 2023-09-05 22:25, Chet Ramey wrote:
> >>> On 9/5/23 3:58 PM, enh wrote:
> >>>> On Fri, Sep 1, 2023 at 6:59 AM
about once a year i have this thought too, usually while looking at
[possible] malware with non-latin identifiers/strings ... my idea was
always that the character should take the first slot, and then i'd use
a unicode ellipsis (or something visually distinct from the usual `.`)
to show which bytes
tzset() returns void, so i don't think there's a good way to detect such
issues without date(1) having to make its own assumptions about how/where
tz data is stored.
On Thu, Sep 19, 2024 at 6:54 PM Philip Rowlands
wrote:
> On Thu, 19 Sep 2024, at 16:32, Chris Elvidge wrote:
>
> > "New Zealand" i
