Follow-up Comment #12, bug #66392 (group groff):
[comment #9 comment #9:]
> I had no way to know if an
> environment had already been created. That makes it harder for a
> package (or, less likely, document) author to manage environment
> initialization. I'm pondering a new `E` conditional opera
Follow-up Comment #8, bug #66675 (group groff):
I sure don't want to undo progress toward a major goal. But I feel like a lot
of what is described here is missing the bigger picture.
Most places in groff that a \[] character comes up, whatever's inside the
brackets has no _meaning_ to groff. It
Follow-up Comment #20, bug #66392 (group groff):
Fun fact: not all emptiness is equivalent.
$ cat hla_strings
.ev 1
.if '\?\n[.hla]\?'' .tm hla is undefined
.if '\?\n[.hla]\?'\?\?' .tm hla is REALLY undefined
$ groff-latest hla_strings
hla is REALLY undefined
_
Follow-up Comment #13, bug #66392 (group groff):
At 2025-02-01T10:53:15-0500, Dave wrote:
> Follow-up Comment #12, bug #66392 (group groff):
> [comment #9 comment #9:]
>> I had no way to know if an environment had already been created.
>> That makes it harder for a package (or, less likely, docume
Follow-up Comment #17, bug #66392 (group groff):
[comment #15 comment #15:]
> It wouldn't--he said without looking at the code--be hard
> to make `.hla` interpolate "undefined".
If the register .hla always exists, I don't really have an issue with it
returning an empty string: it's just as easy t
Follow-up Comment #18, bug #66392 (group groff):
Why is \n[.hla] not global regardless of ev? It seems an eminently reasonable
expectation that a document's hyphenation language will apply throughout the
whole document. I can only think of edge cases where one might want to switch
hla's, e.g. a
Follow-up Comment #19, bug #66392 (group groff):
[comment #18 comment #18:]
> Why is \n[.hla] not global regardless of ev?
By my reading of bug #66387, the salient sentence is, "Pretty weird to pop the
environment stack and have the hyphenation mode, but not the hyphenation
_language_, change."
Follow-up Comment #14, bug #66392 (group groff):
[comment #13 comment #13:]
> meeting your expectations would make `.hla`
> the only predefined register, I think, that would automatically
> come and go from existence as one changed environments.
I did consider (but didn't write down, so you'd hav
Follow-up Comment #15, bug #66392 (group groff):
At 2025-02-01T11:29:08-0500, Dave wrote:
> Follow-up Comment #14, bug #66392 (group groff):
> [comment #13 comment #13:]
>> meeting your expectations would make `.hla` the only predefined
>> register, I think, that would automatically come and go fr
Follow-up Comment #16, bug #66392 (group groff):
[comment #14 comment #14:]
> For most (maybe all) of them, a value of 0 doesn't correspond to
> "undefined," but to "off" or an actual measurement of 0.
It didn't take me long to think of an exception.
$ echo '.if r rst .tm rst defined' | groff
rs
10 matches
Mail list logo
