| 6 Oct 2021 |
 hmenke | In Lua you can have a file at gd/library/doc.lua and then in the code write require("gd.library.doc") and it will be looked up correctly (by the Lua interpreter) | 17:25:11 |
 josephwright | In reply to @hmenke:matrix.org
Regarding the Lua stuff: Till used Lua the way Lua should be used, i.e. using directories for nesting modules. The thing that is odd, quite apart from the names, is that they are in the tex tree not the lua one | 17:25:31 |
| josephwright | In reply to @hmenke:matrix.org
In Lua you can have a file at gd/library/doc.lua and then in the code write require("gd.library.doc") and it will be looked up correctly (by the Lua interpreter) I know - I think it's ... odd ... I'd call the file gd-library-doc.lua (cf. l3build itself) | 17:25:59 |
| josephwright | In reply to @hmenke:matrix.org
In Lua you can have a file at gd/library/doc.lua and then in the code write require("gd.library.doc") and it will be looked up correctly (by the Lua interpreter) Anyway, it's not my business to break that, it's a question of making some adjustments to support it | 17:26:27 |
| hmenke | Feel free to move them to a lua tree but keep in mind that these files are included by the manual, so you might have to adjust the relative paths in the manual sources. | 17:26:48 |
| josephwright | In reply to @hmenke:matrix.org
In Lua you can have a file at gd/library/doc.lua and then in the code write require("gd.library.doc") and it will be looked up correctly (by the Lua interpreter) I guess he did this years ago before CTAN brought in all of the automatic checking | 17:26:51 |
| josephwright | In reply to @hmenke:matrix.org
Feel free to move them to a lua tree but keep in mind that these files are included by the manual, so you might have to adjust the relative paths in the manual sources. I'm trying to change as little as possible, I just wondered what was going on and if it was deliberate | 17:27:34 |
| josephwright | In reply to @hmenke:matrix.org
In Lua you can have a file at gd/library/doc.lua and then in the code write require("gd.library.doc") and it will be looked up correctly (by the Lua interpreter) Of course, means one cannot have multiple . in a file name :) | 17:27:50 |
| hmenke | In reply to @josephwright:matrix.org
Of course, means one cannot have multiple . in a file name :) Not sure. I'd have to read the Lua reference. Maybe it only strips trailing .lua and .so (for C modules). | 17:28:31 |
| josephwright | In reply to @hmenke:matrix.org
In Lua you can have a file at gd/library/doc.lua and then in the code write require("gd.library.doc") and it will be looked up correctly (by the Lua interpreter) I guess I worry (a) about copying files with such generic names and (b) about e.g. typesetting them using listings | 17:28:43 |
| josephwright | In reply to @hmenke:matrix.org
Not sure. I'd have to read the Lua reference. Maybe it only strips trailing .lua and .so (for C modules). Fair point | 17:28:55 |
| josephwright | hmenke: Like I said, l3build is meant to be flexible, it's just this particular case hasn't come up before: I will look to support it | 17:29:44 |
| josephwright | hmenke: Anyway, back to the test part of the question. That seems to be working | 17:31:44 |
| hmenke | In reply to @josephwright:matrix.org
Just that at present you have (at least) three places for the source files: text-en, version-for-luatex and images, and it would be easier to have all the files in one directory (and not then have subdirectories inside them) I assume that at some point Till expected that there'd be other versions than English. | 17:32:05 |
| josephwright | @h It occurred to me that I could add it in a subdirectory such that the build.lua file I've written would fit 'around' the one you have. But perhaps that's an over-complication | 17:32:31 |
| josephwright | In reply to @hmenke:matrix.org
I assume that at some point Till expected that there'd be other versions than English. Quite possibly; I guess I'd set that up as an entirely independent set of files (or perhaps share just the demos) | 17:33:17 |
| hmenke | Yes, eventually it would be nice to get rid of my handrolled build.lua. | 17:33:27 |
| hmenke | In reply to @josephwright:matrix.org
Quite possibly; I guess I'd set that up as an entirely independent set of files (or perhaps share just the demos) You can go ahead and flatten the doc tree. That should be quite easy because it mostly relies on TEXINPUTS instead of using relative paths. | 17:34:30 |
| josephwright | In reply to @hmenke:matrix.org
Yes, eventually it would be nice to get rid of my handrolled build.lua. I've only I think got two things to deal with, both to do with copying a 'predetermined' tree structure. That is likely to need some l3build changes, so I might try to rope Marcel or Paulo Cereda in (better Lua authors than me by far) | 17:34:46 |
| josephwright | In reply to @hmenke:matrix.org
You can go ahead and flatten the doc tree. That should be quite easy because it mostly relies on TEXINPUTS instead of using relative paths. Ah, cool | 17:35:02 |
| josephwright | In reply to @hmenke:matrix.org
You can go ahead and flatten the doc tree. That should be quite easy because it mostly relies on TEXINPUTS instead of using relative paths. That would cut down to one issue: the Lua stuff we've just discussed | 17:35:21 |
| josephwright | hmenke: I'll also have to check on what you do for source tagging - that's likely to be a straight copy-paste of your code | 17:35:52 |
| hmenke | Merging the version-for-*/pgfmanual-*.cfg will be annoying though. | 17:36:57 |
| hmenke | In reply to @josephwright:matrix.org
hmenke: I'll also have to check on what you do for source tagging - that's likely to be a straight copy-paste of your code Which one? The pgf.revision.tex? | 17:37:31 |
| josephwright | In reply to @hmenke:matrix.org
Merging the version-for-*/pgfmanual-*.cfg will be annoying though. I'll see what I can do to avoid changes, like I said - I think I might simply have run into a bug in l3build | 17:37:39 |
| josephwright | In reply to @hmenke:matrix.org
Which one? The pgf.revision.tex? whatever revisionfile does - I'd not looked at it | 17:38:26 |
| josephwright | hmenke: I've got to pop out - back in about 30 minutes | 17:38:36 |
| hmenke | Yes, that's the one. | 17:38:42 |
| josephwright | In reply to @hmenke:matrix.org
Yes, that's the one. OK, I'll try that next before the bigger issues | 18:09:19 |
| josephwright | hmenke: Does the testing look usable? | 18:09:27 |
