Stack Exchange
log in

muzimuzhi Z

 TeX, LaTeX and Friends

\begin{chat}
17
13
muzimuzhi Z
Nov 25, 2024 05:16
@mbert huge thanks ^_^
muzimuzhi Z
Nov 25, 2024 04:59
Great!
BTW, does the tug.org/svn support any sort of searching by filename?
muzimuzhi Z
Nov 25, 2024 04:02
encountered tlmgr info --json when posting github.com/teatimeguest/setup-texlive-action/issues/…
muzimuzhi Z
Nov 25, 2024 04:01
The doc for `tlmgr info --json` [1] says the format of its JSON output is documented in `tlpkg/doc/json-formats.txt`, but I even don't have the `doc` directory under `$(kpsewhich --var-value TEXMFROOT)/tlpkg`, in a/an (incomplete) basicTeX installation on macOS.

Would anyone with complete installation help me check whether `tlpkg/doc/json-formats.txt` exist? Is there any copy of it available from the internet? I searched in the texlive-source repo [2] but found nothing.

[1]: https://www.tug.org/texlive/doc/tlmgr.html#info
muzimuzhi Z
Oct 1, 2024 22:43
@cfr The situation that I was not the solely affected user. (me accompanied with affected others). Sometimes it gives me more confidence that the noticed issue will soon be resolved.
muzimuzhi Z
Oct 1, 2024 22:41
@cfr I have no idea about such per-CTAN-ann emails before the last weekend too.
muzimuzhi Z
Oct 1, 2024 20:34
Thanks. That's good news (for getting accompanied).

BTW the last Digest email I received had the "Ctan-ann Digest, Vol 1049, Issue 5" topic and was received at Fri, 27 Sep 2024 03:00:51 -0700 (PDT).

But three weeks ago per-announcement emails were already sent
- "[Ctan-ann] CTAN update: verifycommand" received at Wed, 4 Sep 2024 11:57:15 -0700 (PDT), from petra at ctan.org
- "[Ctan-ann] CTAN update: heria" received at Wed, 4 Sep 2024 23:18:25 -0700 (PDT) from petra too
muzimuzhi Z
Oct 1, 2024 20:20
The CTAN page on announcements and the mailing list:
https://ctan.org/ctan-ann?lang=en
muzimuzhi Z
Oct 1, 2024 20:19
Is is just me that recently CTAN-ann Digest emails are no longer sent but replaced with emails one for each CTAN announcement?

Even worse, I'm unable to open https://lists.dante.de/mailman/listinfo/ctan-ann right now.
muzimuzhi Z
Nov 23, 2023 20:39
@DavidCarlisle Done, see github.com/latex3/luaotfload/issues/270.
muzimuzhi Z
Nov 23, 2023 20:26
In my diff, wasn't the same callback successfully inserted?

> Inserting `luaotfload.dvi' in `pre_shipout_filter'.
muzimuzhi Z
Nov 23, 2023 20:03
Comparing full logs generated by lualatex and dvilualatex, I found most differences are caused by luaotfload.
https://www.diffchecker.com/41Oz5JO3/
muzimuzhi Z
Nov 23, 2023 19:33
Does LuaLaTeX in dvi mode (`lualatex --output-format=dvi') need special (font) setting?

I got `Missing character: There is no @ (U+0040) in font nullfont!` from

```tex
\documentclass{article}
\begin{document}
A-B
\end{document}
```

(simplified from https://github.com/mgieseki/dvisvgm/issues/255)
muzimuzhi Z
May 11, 2023 21:45
A light LuaLaTeX question:

Function `luatexbase.module_warning(<mod>, <msg>)` writes `<msg>` to log on its own line(s), but not surrounded by empty lines like how LaTeX2e or expl3 warnings do. Is this the designed behavior?
muzimuzhi Z
Jun 16, 2022 13:13
\documentclass{article}
\usepackage{pgfkeys}

\begin{document}
\pgfkeys{
  key a/.code={\texttt{\detokenize{#1}}},
  key b/.style={key a={#1}},
  key c/.style={key b={#1}}
}

\pgfkeys{key c={{{{{{{{xx}}}}}}}}} % output "{xx}", eight levels!
\end{document}
muzimuzhi Z
Jun 16, 2022 13:13
@FaheemMitha Even worse, when for example a style key (defined by /.style handler) passes its value to another key, which is another style key that passes the value on. :(
muzimuzhi Z
Jun 16, 2022 13:04
@DavidCarlisle thx. Then pgf will receive a new issue.
muzimuzhi Z
Jun 16, 2022 13:01
The example above works and gives expected output, but if that usage is officially supported?
muzimuzhi Z
Jun 16, 2022 12:59
\documentclass{article}
\usepackage{amsmath}

\begin{document}
\[
  \begin{matrix}
    a & b & c \\

    d &

    e & f
  \end{matrix}
\]
\end{document}
muzimuzhi Z
Jun 16, 2022 12:58
Regarding tex.stackexchange.com/q/646983, I wonder is an empty line between (traditional hence non-tikz) matrix cells a supported syntax?
muzimuzhi Z
Jan 9, 2022 17:19
got it
muzimuzhi Z
Jan 9, 2022 17:11
The following lines explaining the `[default]` uses `family` consistently,

% A declaration of the form:\\
% |\define@key{family}{key}[default]{...}|\\
% Defines a macro |\KV@family@key| as above, however it also defines the
% macro |\KV@family@key@default| as a macro with no arguments, and
% definition\\
% |\KV@family@key{default}|.
muzimuzhi Z
Jan 9, 2022 17:02
BTW, in the keyval package manual,

% A declaration of the form:\\
% |\define@key{family}{key}{...}|\\
% Defines a macro |\KV@prefix@key| with one argument. When used in a
https://github.com/latex3/latex2e/blob/c7ce5c12653100d7677362cabd27748cb3ab3de3/required/graphics/keyval.dtx#L178

It the `\KV@prefix@key` a typo? To me it should be `\KV@family@key`
muzimuzhi Z
Jan 9, 2022 16:59
I slightly dislike this way because the family is read and set twice. The pro is it uses only the two public macros \define@key and \setkeys.
muzimuzhi Z
Jan 9, 2022 16:54
You mean sth like
\define@key{fam}{mystyle}{\setkeys{fam}{<key-val>}} ?
muzimuzhi Z
Jan 9, 2022 16:47
@JosephWright Why the "key name"? It seems to me what needed is to replace the user-specified key value #1 with \KV@do#1,\relax,.
muzimuzhi Z
Jan 9, 2022 16:35
@FaheemMitha well, keyval.sty is short enough
muzimuzhi Z
Jan 9, 2022 16:27
The situation is, pkgA uses keyval, users use pkgA. For me it's easier to patch keyval than to change the key-val package that pkgA is based on. though it's not the ideal way.
muzimuzhi Z
Jan 9, 2022 16:24
@DavidCarlisle I understand. It is not a feature request to keyval, only casual/personal attempts.
muzimuzhi Z
Jan 9, 2022 16:22
@FaheemMitha Cause there're plenty packages using keyval and users might want to have "key style".
muzimuzhi Z
Jan 9, 2022 16:19
The main aim is to extend `keyval` so that packages based on it can define key styles. Seems this does the trick
```tex
\NewDocumentCommand{\define@key@style}{ m m o m }{%
\IfNoValueTF{#3}{%
\define@key{#1}{#2}{\KV@do #4,\relax,}
}{%
\define@key{#1}{#2}[{#3}]{\KV@do #4,\relax,}
}%
}
```
muzimuzhi Z
Jan 9, 2022 15:07
May I ask that are there any existing extensions/packages that bring pgfkeys' "style key" to keyval?

There are calls for this feature from time to time, among which the latest one is https://tex.stackexchange.com/q/629489
muzimuzhi Z
Aug 2, 2020 18:11
@Szabolcs \hyperref[#2]{#1~\ref*{#2}} is better. \ref* won't create hyperlink. See use example of \ref* on page 21 of hyperref manual.
muzimuzhi Z
Aug 2, 2020 15:00
@AndréC I will have a try. Which form is more preferable, a pdf file (uploaded to CTAN or not) or a github url (for example, a markdown file including several svg images)? Personally I slightly prefer the latter one. It is lighter.
muzimuzhi Z
Aug 2, 2020 14:15
Actually the related documentation is just commented out in, but not deleted from, source file of pgfmanual: github.com/pgf-tikz/pgf/blob/master/doc/generic/pgf/text-en/…
muzimuzhi Z
Aug 2, 2020 14:13
@AndréC It's simple to provide a one- or two-page doc introducing functionality of deprecated libraries "arrows" and "arrows.spaced", but for pgfmanual maybe their use should be restricted, at least not at tutorial sections.
muzimuzhi Z
Aug 2, 2020 13:04
@AndréC @Rmano I've made a pull request to pgf, which replaces those two usages of deprecated arrow tips "to" with ">" in tutorial sections of pgfmanual. See github.com/pgf-tikz/pgf/pull/905.
 

 Discussion between muzimuzhi Z and an…

Imported from a comment discussion on tex.stackexchange.com/qu...
muzimuzhi Z
Jun 8, 2020 23:32
After a rather amount of trying, it turns out that currently I am not capable of patching amsmath pacakge. Sorry. To become capable of, I might need to read and understand the source code of amsmath pacakge (file amsmath.sty) thoroughly. And that should take days or even weeks.
muzimuzhi Z
Jun 8, 2020 17:39
I really doubt whether we are at the almost-done stage. Usually there would be more uncovered edge cases. Then gradually the implementation will need more and more patching lines. For a technical attempt, I will have a try; for practical usages, I recommend to not use LaTeX in this way.
muzimuzhi Z
Jun 8, 2020 17:12
Can I know when you want to use this auto-delimited utility? Maybe it is already supported by LaTeX editors.
muzimuzhi Z
Jun 8, 2020 17:07
I will have a try, but I cannot make a promise right now.
muzimuzhi Z
Jun 8, 2020 17:07
I understand what you require would be useful in some cases, and that requirement is understandable from a programming perspective. But restricted by how LaTeX2e and its packages are designed and implemented, adding another kind of usage may really require many tough works.
muzimuzhi Z
Jun 8, 2020 17:03
@antshar In this mulline* env, the second \autoScoped is not normally ended. I need to read more source code of amsmath pacakge, before telling you why it's wrong and how to automatically end a scope at the end of amsmath env.
muzimuzhi Z
Jun 8, 2020 16:55
3) The missing bracket is caused by "nesting is not supported", which I have mentioned in my answer.
muzimuzhi Z
Jun 8, 2020 16:53
2) What's the corresponding input of imgur.com/VV4dY3B (problematic multline output)?
muzimuzhi Z
Jun 8, 2020 16:52
1) As you have noticed, if you want to use this auto-delimited-scoping to actually adding characters, you must be careful about the space character.
muzimuzhi Z
Jun 8, 2020 16:51
I'm not sure I have the interest to continue this patch.
muzimuzhi Z
Jun 8, 2020 16:50
@antshar Support for list and amsmath envs is added.
muzimuzhi Z
Jun 8, 2020 16:50
@antshar 1) TeX automatically converts consecutive new line characters to \par, so the patch to \par works. 2) Because in those environments, the definition of \` or \par` (or both of them) is changed.
muzimuzhi Z
Jun 8, 2020 16:50
@antshar 1) No, my answer cannot handle double Enter new line. 2) Generally, \autoScoped and \end@scope@if@in can only contain declarative commands, which means it should not produce any output. 3) Yes, and there are many many more cases (in center env, in tabular env, ...) it doesn't work. As I pointed in my answer, you almost should not use latex in this way.