Follow-up Comment #4, bug #63635 (group groff):
[comment #3 comment #3:]
> A) The hyphenation mode itself is already a property of the
> environment.
True, but this to me doesn't argue either for or against having the _default_
also be per-environment. (The .hy default before this change was global
despite the hyphenation mode being per-environment.)
> B) Different environments might be used for setting text in
> different languages.
That's a valid point.
> C) Having the hyphenation mode default also be per-environment
> means that you can invoke `hy` without arguments in any given
> environment and it will "do the right thing".
This seems situational. Since new environments can be created on the fly, if
one creates an environment to, say, handle a footnote region, and calls
argumentless ".hy" in that environment, it seems like the "right thing" is to
use the hydefault set for the rest of the document, and the less right thing
(which this request was specifically designed to avoid) is to set it to 1.
(Side note: comment #0 here mentions that hydefault defaults to 1, but the
Texinfo manual does not.)
The multiple-language use case is compelling. However, since the new knob
exists at all as a safety net for those who don't read the documentation
closely enough to know that .hy doesn't work like other requests, I wonder if
there's a case to be made for making it work best for those doing simple
things, and assuming advanced users have done their homework.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63635>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
