-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make ~
active in docstrip's initex mode
#636
Comments
Part of the blame is mine ;-) I could change Makes me wonder though: why use initex for unpacking? |
That was going to be my second suggestion, if you were so kind to do so. Third option being patching around it myself (I wouldn't want anyone actively maintaining my use case). I just though that it was inconsistent for docstrip to check for a setting to detect iniTeX, but the setting is not actually needed (and hence not set). That is why this was my first try at remedying the issue at hand.
I bootstrap a small TeX distribution (LuaTeX + OpTeX + a few packages) from a few sources. Essentially I do:
Processing the few By the way, while bothering you, I believe you can use |
Ah, minimal setups :-) I'd say providing plain is a must for any TeX distribution (kind of “the basics”), but that's digressing. I'll change the |
Thank you very much, @PhelypeOleinik. That solves my issue quite well. I still think the proposed change would make sense. But not sure if there is a point in pursuing this since it would be one of only backwards incompatible changes in Leaving the decision on closing the issue on you guys. PS: @PhelypeOleinik I used to package (TeX Live's) plain LuaTeX as well, but later decided against it. Many things I wasn't really fond of are deeply rooted in -- fonts, eTeX's |
I'm against making changes to docstrip for that. It is soooo core to basically everything (other than ConTeXt) so that it is bound to generate issues and history says it will. Don't think that is worth it. So it should be fixed in lipsum. |
Brief outline of the enhancement
I am using
docstrip.dtx
to process a few.ins
files withinitex
. However, recently one of those.ins
files started to expect that\catcode`\~=13
. I usually make these adjustments before processing the.ins
files, like this:This is not possible with for the
~
catcode, because that is howdocstrip
detects, that it is not run underinitex
:Would it be possible to set the
\catcode
of~
to 13 in this "plain TeX compatibility" piece of code?LaTeX2e generally cannot add new features without an extreme amount of care to accommodate backwards compatibility. Please do not be offended if your request is closed for being infeasible.
I am perfectly fine with patching around for my dubious use case. I understand that this subtle change is not desirable after such a long time.
Minimal example showing the current behaviour
Because of
\def~{ }%
Minimal example showing the desired new behaviour
With:
Context: vlasakm/mmtex#3
The text was updated successfully, but these errors were encountered: