6:37 AM
@barbarabeeton Oohh, found it. I'll have a look at it those five minutes I might have free in the coming days. :p

2 hours later…
8:36 AM
@Skillmon ooh pxpic opportunities here kotaku.com/…

@PauloCereda oh, pixels.

@Skillmon :)
OH NO
US why

9:40 AM
@samcarter_says_quack ^^ we need a pirate duck

@UlrikeFischer OMG YES
Yo ho ho and a bottle of Coca-Cola

@PauloCereda we need a pirate map latex package :)

@samcarter_says_quack ooh

@PauloCereda vvv
2

9:49 AM
@DavidCarlisle ooh :)

@UlrikeFischer cleaver all ready for carving. Very useful.

@JosephWright Hi, you can activate "Discussions" in the learnlatex repository, I am interested in collaborating with the Spanish translation, preferably neutral Spanish, to avoid es-la or es-ms or es-something and I think that space is better suited for ideas :)

@DavidCarlisle When I rotated them in the video I had a quite hard time trying to avoid that they cut themselves and each other ;-) Swords are dangerous and should probably not be put in the hands of ducks ...

@PabloGonzálezL Sure will do

@PabloGonzálezL @JosephWright are discussions a new thing, I don't remember them before although as you probably saw they are being used in l3build at the moment. Not sure what they offer over issues, just the avoidance of implying there is a bug to be fixed?

9:54 AM
@DavidCarlisle Something like that: meant to be open-ended and I think a bit more like a classical mailing list. I'm mainly 'testing them out' in l3build. They can get linked to issues, I think

@UlrikeFischer ooh

@DavidCarlisle They are more a space to share an idea (rather than a request), for example, what is now in l3build are some nice ideas, but, they are not a formal request.

@PabloGonzálezL Like I said, like a mailing list :)
@DavidCarlisle My plan is that we see how they work in a place where we don't have an existing history clearly linked: LaTeX-L is great for general discussion of LaTeX, but l3build is ... mainly Lua and ... different

@JosephWright They are good for debugging ideas and see what is feasible or not...so the repository is a little cleaner.

@PabloGonzálezL You've used them elsewhere?

9:58 AM
ooh wir sind Piraten!

@JosephWright In the private repository of my work they have it, the webmaster got bored of requests and strange things we were doing :), so they left us that space.

@PabloGonzálezL Ah, right

@JosephWright In learnlatex it fits perfectly, when it comes to translations it is hard to agree, and it is not worth to reload a issue with that, a while ago I wrote about my beloved (Spanish) quotation marks, but, it does not fit in a issue, it is more like a discussion about the style and how it will be translated from one language to another.

@JosephWright which reminds me, I think LL needs a contributor guide...

@JosephWright I think there should be a special mention to the quotation marks, each country has its own style in this, it is not easy to hit them all at the first time in LaTeX :D

10:04 AM
@PabloGonzálezL csquotes?

@JosephWright Síiiiiiii
@JosephWright For example, the last issue you posted is perfect for discussions :)

@JosephWright No, I mean: you want to help? Create a GH account, click that fork button there, then you you have this... /steps follow... now do a pull request.

@PauloCereda Ah, right: good idea
@PauloCereda Can I assign that to you? ;)

@JosephWright If it wasn't for my beloved textcomp I would never have gotten my quotes when I started using LaTeX, I blame the LuaTeX developers for not starting earlier and the creator of csquotes for the same reason :)

10:09 AM
@JosephWright okay, I have IoT stuff to tackle, so I will put in my TODO list.

@PauloCereda You must have a big monitor to be able to read those full lines :)

@PauloCereda I was semi-joking, but if you could write something, that would be great: mnay thanks (as always)

@PabloGonzálezL I have a good editor. :)
@JosephWright so my answer can be semi-okay? :)

@PauloCereda :)

@PauloCereda :P

10:12 AM
@JosephWright jokes aside, I was kind of serious: LL cannot afford to lose good contributions just because contributors are not tech-savvy. :)

@PauloCereda Do the spaces at the end of the line in md have any meaning?

@PabloGonzálezL I actually forgot to break those lines. :)
@PabloGonzálezL sorry?

@PauloCereda Indeed: I would welcome a good guide

@PauloCereda Es una duda :)

@PabloGonzálezL You mean, for Markdowm?

10:13 AM
@PauloCereda Yes

@PabloGonzálezL ah, I don't think they have meaning, but with Markdown (and its handful of different specs and implementations) you can expect anything. :)
Well, any meaning other than hey, this is an empty line, look how empty it looks. :)

@PauloCereda By default I have my editor set to remove those spaces, if I remember correctly two or more spaces at the end of a line were significant in md.

Blank Lines

Markdown automatically joins elements such as text, list items, and code blocks, if there are no different types of elements between them. For example, if you create two lists (using the Markdown asterisk notation) with a blank line between them, the Markdown parser will automatically join them into a single list. You can use the following methods to add blank lines in your Markdown code:

To add a single extra line after a paragraph, add two extra spaces at the end of the text.
@PabloGonzálezL ^^ there you go
What an easy format
3 mins ago, by Paulo Cereda
@PabloGonzálezL ah, I don't think they have meaning, but with Markdown (and its handful of different specs and implementations) you can expect anything. :)

@PauloCereda Ohhh....I'll have to make a couple of changes :( I did a PR on a friend's repo, it looks like the line breaks make them that way...dang :(

@PabloGonzálezL blame your friends, it's a common practice here. :)

10:19 AM
@PauloCereda I blame those who leave spaces at the end of the lines...I don't like them at all :)

@PabloGonzálezL Damn those empty lines, they ruined the empty lines
@PhelypeOleinik ^^

@PauloCereda Technical question, CTAN has an automatic hyphenation system (gave me headaches copying characters I did not see in the past), does learnlatex have the same thing enabled behind the scenes?

@PabloGonzálezL it didn't unless Jonas added it in the big restyle just now, I'd need t check....
@PauloCereda or @UlrikeFischer

10:34 AM
@PabloGonzálezL no idea

@DavidCarlisle why "or"? Should that be "and"?

@UlrikeFischer means same thing I think (English isn't very good with logical connectives:-)
@PauloCereda I thought we had something about making Forks but found it in the translation guide learnlatex.org/TRANSLATIONS That could be made more general as it applies to any contributions not just translations. Also I think some of the details need updating to the new layout. (@JosephWright) learnlatex.org/TRANSLATIONS

10:52 AM

@PauloCereda because it mentions zz ?

@DavidCarlisle Because it wants users to do the repo mantainers job, like updating YAML files.

@PauloCereda I'm confused. If you want to add a translation for a new language in your fork, then you are the repo maintainer aren't you?

@DavidCarlisle you are the language contributor.

@PauloCereda yes but my idea writing that was that if you wanted to add the Greek (say) translation, you don't need to ask the central maintainers anything you can fork the repo add the yaml settings in your fork to add gr to the language switcher menu then translate your pages, and just make a PR when it is done. Is that not how you see the workflow?

10:56 AM
@DavidCarlisle I suggested languages to be mantained as separated modules, so they've nothing to do with the website and/or layout.
Languages, lessons... dunno the name.

@PauloCereda that's more technical:) and don't people want to see their translated pages rendered and if they have translated the examples test pressing the run online button, so need a working setup.
@PauloCereda eg while testing the (unfinished) Chinese setup I installed more fonts on the latexcgi server (and checked that those fonts were already on overleaf) you can't completely separate the text from the site setup I think.

@DavidCarlisle then you need way more than that brief text in the "adding your language" section. Anyway, I was just suggesting things, so they can be easily discarded. As anything else, I am used to it. :)

@PauloCereda not discarded I just don't think I understand quite what you are suggesting. Possibly because I have only used git submodules in one project (and never really understood how they were working:-)
@PauloCereda originally the "layout" part was just a couple of files with the page template, some css,and the javascript for the example submissions so there wasn't much to keep separate. There is a lot more stuff now but (I think) now we have moved back to github pages from netlify most of it can go (the local jekyll/ruby parts) so forking the repo needn't be so scary.

@DavidCarlisle keep the web designer around just in case. :)

11:15 AM
@PauloCereda I was trying to understand your suggestion but seems you don't want to clarify.

@DavidCarlisle I think the idea is that the main repo is just the design stuff, then each current <lang> subdirectory gets moved to it's own repo, which then only contains .md files

@DavidCarlisle language barriers from my end, most certainly. :) Thankfully, Joseph's crystall ball seems to be working today ^^

@PauloCereda I think one wrinkle is that there are places one needs a 'list of languages' or 'common language data'. Perhaps the latter could be moved to be inside the subdirs, but I'm not sure how you construct the top-level landing page/language menu without a file in the main repo listing languages

@JosephWright that should probably be thought before the entire endeavour, and now the whole thing is so entangled that it is challenging to reorganise. So simply scratch my suggestions, as the site is already officially announced.

In a previous project at work we used gitlab with some cookie cutter based thingy. This would allow users to easily create new projects from a template. Maybe something like this could be used to make steps like "copy the en folder, then change zzz" easier? [no idea if something like this exists for github]

11:25 AM
@PauloCereda I guess the question is whether submodules and whatnot would help potential contributors; I see the idea that it means a language has a very simple repo, but then it makes the whole site more tricky

14 mins ago, by Paulo Cereda
@DavidCarlisle keep the web designer around just in case. :)
@samcarter_says_quack GitLab <3

@PauloCereda The top-level file is manageable: one could argue that is only edited when a new translation is agreed/added
@samcarter_says_quack They do have a 'this is a template repo' thing
@PauloCereda I guess I'm wondering not about the technical side, but how much having separate repos helps people write translations: I'm honestly not sure

@JosephWright and I wonder how cloning the entire site with all bells and whistles and jewels (sapphires, rubies and whatnot) helps people write translations as well.
@JosephWright but again, my opinion does not matter at all. :) Thanks for LL and keep up the good work, it's highly appreciated! (@DavidCarlisle too with backend stuff) :)

11:45 AM
@PauloCereda Maybe you should consider adding a couple of my personal rules to your contribution file. First: Do NOT have lines as long as the arara manual :), Second: Configure the editor you use to avoid the blessed spaces at the end of a line (in md they do make sense) and Third: Do NOT use "hard tabs" to format the code.

@PabloGonzálezL quack :) Noted. :)

@PauloCereda you are not supposed to be able to reply to yourself:-) (I know how to cheat as well)

@PauloCereda I had to completely undo a PR I had done, all because I removed the blessed trailing spaces from ALL of the md I had edited :(

@PauloCereda Oh, your opinion matters a lot: you are in my mind one of the core team
@PauloCereda True: as @DavidCarlisle says, it may be a lot of that can go now we are back to a simple GitHub Pages setup (certainly I hope so: the reason for using GH Pages is the ease-of-setup)

12:02 PM
@DavidCarlisle And will it be implemented? ...I don't want to run into invisible characters :(

@PauloCereda Me gustan las Llamas :)

LOOK OUT, THERE ARE LLAMAS
3

@JosephWright OOH
@PabloGonzálezL it's from a Monty Python sketch. :)

@PauloCereda :D

12:05 PM

@JosephWright Thanks :)

@JosephWright Llama (Lama glama) are a protected species in my country :P

@PabloGonzálezL They are reputed to be vicious .. isn't it more that people need protection from llamas?

@PabloGonzálezL ooh Chileans are awesome

@JosephWright Jeje, YES
@PauloCereda Todo el rato :)

12:09 PM
@PabloGonzálezL ooh
Los patos son muy inteligentes

@PauloCereda Oh sí

@PauloCereda See Skype

@PabloGonzálezL the text is set ragged, so I guess not

@DavidCarlisle I don't think I'd want to enable it

@JosephWright agreed

12:17 PM
@DavidCarlisle Great, I won't run into hidden characters :)

@PabloGonzálezL we could add some by hand to catch you out

@DavidCarlisle Hehe... I comment it because I was writing something some time ago and I wanted to make a reference, of course, instead of going directly to the documentation I copied from CTAN...it was a headache to catch what the heck had happened...and it was those characters that are invisible :(

@PabloGonzálezL We want things to copy-paste, so you should be safe

@DavidCarlisle Technical consultation, when handling lists there are three parameters (that I have used) \@beginparpenalty, \@itempenalty and \@endparpenalty, when establishing some value to these, it affects all the levels of the list or only in the level that is assigned?
@JosephWright I can open a discussion in Spanish in learnlatex?

@PabloGonzálezL by default all levels nothing sets \@itempenalty within the default list handler for example

12:30 PM
@PabloGonzálezL I guess :)

@DavidCarlisle Ok, I get it, no need to define them by nesting level then :)
@JosephWright Thank you

12:46 PM
@JosephWright @PhelypeOleinik if one use two underscores in a key name, one gets lots of warnings from l3doc:
Package l3doc Warning: A control sequence of the form '...__internala' was
(l3doc)                used. It should only be used in the module 'internala'.
Can one avoid this?
\begin{filecontents}[overwrite]{test.dtx}
\ExplSyntaxOn
%<@@=test>
%    \begin{macrocode}
\keys_define:nn{test}
{
__internala .code:n=blub,
__test_internalb .code:n=blub,
test__internalc .code:n=blub,
_internald .code:n=blub,
k__internale .code:n=blub,
}
%    \end{macrocode}
\ExplSyntaxOff
\end{filecontents}
\documentclass[full]{l3doc}
\begin{document}
\DocInput{test.dtx}
\end{document}

^^ describe US today in one image

@UlrikeFischer Only by setting <@@=>

@UlrikeFischer You can use @@_internalb .code:n (it will complain if a __<name> is found, even if the <name> is the same as the current module)
@JosephWright <@@=> disables replacement but not nagging :)
@UlrikeFischer Or \InternalDetectionOff :)

@PhelypeOleinik but this makes the key names longer, and the module name is already in the \keys_define:nn {test}, so it feels unnecessary to guard the key names. I think I will simply use only one underscore ...

@UlrikeFischer Seems reasonable

1 hour later…
1:54 PM

2:21 PM
@yo' Drat, you were quicker than me! :)

@PauloCereda :D

1 hour later…
3:45 PM
folks
halp
I'm trying to read in from a file which contains a bunch of arguments
{arg11}{arg12}
{arg21}{arg22}
etc
I would like to read it in line by line and apply a command to each line
say

@EmilioPisanty \read should work fine
@EmilioPisanty I'd use expl3 and \ior_map_inline:Nnn

\def\formatargs#1#2{the 1 is #1 and the 2 is #2}
I can get \openin+\read to work fine
but it seems to be collapsing the braces
i.e. the output seems to come from a call like \formatargs{arg11arg12}{}
@JosephWright yeah, I would hope for as basic a solution as possible
@JosephWright i.e. I'll start up the expl3 road if needed, but I'm hoping there's something simpler

@EmilioPisanty How are you processing the result of the \read?

the current code looks like this:
      \newread\file
\openin\file=\jobname.looi
\loop\unless\ifeof\file
\@format@orcid@listing\fileline \
\repeat
\closein\file

\makeatletter
\def\@format@orcid@listing#1#2{%
\item #1: #2
}
\makeatother
in the previous notation
  \newread\file
\openin\file=\jobname.looi
\loop\unless\ifeof\file
\formatargs\fileline \
\repeat
\closein\file

@EmilioPisanty You need \expandafter before \@format@orcid@listing\fileline.

3:53 PM
@MarcelKrüger that's crashing the compilation
Runaway argument?
! Paragraph ended before \@format@orcid@listing was complete.

@EmilioPisanty Does your file contain empty lines?

@EmilioPisanty You need to check first that the line is not blank: that \fileline is not \empty

ah
yes, there's an empty line at the end
if I could figure out how to stop the write command from putting it then it'd be gone, but it's probably better to be resilient to empty lines

@JosephWright Wouldn't empty lines make \fileline be defined as \par instead of being empty?

@JosephWright is there a simple/standard way to do this?

4:01 PM
@MarcelKrüger Yes ...

hmmm coffee

OK, it's a bit better
I used the approach in this answer tex.stackexchange.com/a/312392/13423

> Microsoft Doubles Cost Of Xbox Live From What It Was A Year Ago

  \newread\file
\openin\file=\jobname.looi\relax
{\endlinechar-1
\loop\unless\ifeof\file
\expandafter \@format@orcid@listing\fileline
\repeat}
\closein\file
it compiles correctly
and it separates the two arguments for each line
but it's still reading in the final line as a separate item
@PauloCereda I thought that might be from the llama song, it'd be appropriate for you =)

4:17 PM
@EmilioPisanty ooh! :)

4:47 PM
@PauloCereda Llamas with swag

@JairoA.delRio LOL

why does biber complain about () in citation keys? bibtex handles that just fine
Hmm, found this one: tex.stackexchange.com/a/96918/3929, that is a super no go for this project. It uses a massive BIB file (1000s of entries) and they used () in every single key. Sigh
And since this bib file is reused in other projects you just don't rename them.

5:22 PM
> Apple Reportedly Looking to Revive MagSafe Charging in a New MacBook Air Too

@PauloCereda oh, duck science :)

@samcarter_says_quack we know it's true because they use maths. :)

@PauloCereda O.o

5:43 PM
@EmilioPisanty \par ? check for \par from blank lines/final line

6:05 PM
@PauloCereda Sounds good: I miss it

@JosephWright Since my MB 2007's battery has been dead for several years, I might've glued that damn thingy to the power inlet to ensure it never dies by accident. :)
> [...] For a select few in China, though, the death of Flash meant being late to work, because the city of Dalian in northern China was running their railroad system on it. Yes, a railroad, run on Flash, the same thing used to run “free online casinos” and knockoff Breakout games in mortgage re-fi ads.

@PauloCereda :)
@PauloCereda I've fixed the GitHub pings :)

6:22 PM
@JosephWright wrote something, take a look if it's sensible...

7:18 PM
Why in the movie Cars, where everyone is a car, there's a bus and a taxi?!

@PhelypeOleinik is there anything in l3doc that allows to document keys? (including adding them to the index)

@UlrikeFischer -- While I agree that any sharp-edged object in the hands of a duck is probably dangerous, a pirate wouldn't use a sword. A straight blade is inherently dangerous on shipboard, largely because there is too much stuff (like rigging) in the way. So a cutlass is a lot more useful. (Pirate duck does have a cutlass.)

@barbarabeeton I didn't know that you have pirate experience ;-)

@UlrikeFischer ooh

7:42 PM
@UlrikeFischer only from Penzance probably

@PauloCereda Thanks

@PauloCereda if I was mean I'd quote chat.stackexchange.com/transcript/41?m=55573061#55573061 but obviously I'm not mean.

@DavidCarlisle Ducks probably have short attention span and OOH A COOKIE

@PauloCereda s/attention span/life/

@DavidCarlisle oh no

7:53 PM
@UlrikeFischer Misusing commands here and there, this seems to work:
\documentclass{l3doc}
\begin{document}
\begin{documentation}
\begin{variable}{some-key}
This documents the key \cmd{some-key}.
\end{variable}
\end{documentation}
\begin{implementation}
\begin{macro}{some-key}
Here's the implementation
\begin{macrocode}
\keys_define:nn { package }
{
some-key .code:n { Blame Ulrike }
}
%    \end{macrocode}
\end{macro}
\end{implementation}
\PrintIndex
\end{document}
@UlrikeFischer Though it doesn't catch any occurrences of the key in the code due to the missing backslash (doc makes backslashes active to add the macro to the index)

8:17 PM
Does anyone know if they ever fixed SumatraPDF?

@Canageek We might need a clue as to what needed fixing!

@JosephWright i t w a s c o p y i n g t e x t l i k e t h i s
I thought there was a problem with my LaTeX until someone here clued me in
It broke in 3.1.2 I think?

Running l3kernel's test suite takes soooo long :(

@Skillmon Depends: it's not too bad on Travis-CI
@Skillmon It used take longer ...
@Skillmon How long is it taking for you?

@JosephWright on my local machine, when I just want to quickly try whether something I think should do breaks elsewhere horribly :)

8:26 PM
@Skillmon Running latex2e's test suite takes way longer :)

@Skillmon That's why people have CI systems: eyeball a few things, commit to some branch, push, find it breaks, fix, rebase so the mistake 'doesn't exist' ;)

(but yeah, you need patience :)

@PhelypeOleinik Oh yes
@PhelypeOleinik Newbie ;)

@JosephWright Also no rollback-often surprises on l3kernel

@JosephWright I think it takes perhaps 5-10 min. But it's currently running, I'll see the time afterwards.

8:28 PM
@PhelypeOleinik That, true
@Skillmon So quite quick then: I thought you said it was slow!!!

@PhelypeOleinik lucky me, can decide to just not touch LaTeX2e :)

@PhelypeOleinik why did no test catch that?

l3build check 457.39s user 98.27s system 99% cpu 9:19.97 total

@Skillmon Good choice :)

@JosephWright it feels like taking forever :)

8:29 PM
@UlrikeFischer Catch what?

@PhelypeOleinik the rollback error

@UlrikeFischer Ah, you mean that one... That only appears if you're on 2021-05-01, rolling back, so normal tests don't see that, and I don't think we have a “rollback-to-every-possible-date” test
@UlrikeFischer Maybe we should...

8:47 PM
@UlrikeFischer Ah, it was you who was submitting the bug reports on Github: Is it safe to move to new versions of SumatraPDF yet? I'm having trouble following if that is fixed yet, as the issues are closed but people are reporting it still being a problem

9:01 PM
@Canageek I didn't submit the bug. And I don't know if it safe, the sumatra on my laptop is still 3.1.2. But there is imho a portable version, so you can easily test yourself.

@UlrikeFischer Good call, I'm updating all the software on the lab computer. So many out of date programs as I'm the only one who ever does this (Adobe Reader 2017)

@PhelypeOleinik well perhaps not every rollback and not all details. But it would be good to catch if it works at all.

@UlrikeFischer Yeah, I see Frank already added one to roll back from whenever to 2020-10-01 due to that issue. It is a pain though, because every test that does rollback is a often test that surprise-breaks Travis :/
@UlrikeFischer I guess if we solve it right this time around, this problem won't happen again (because if we don't, ltcmd is just around the corner to break :)

@PhelypeOleinik well it more or less works, but there is place for improvement here imho. It would be e.g. nice if all the keys where under a main index entry "keys of module XYZ". I also think that we will have a growing amount of "non-commands" to document, e.g. hooks, keys, the export-formats in l3color etc.

@UlrikeFischer Yeah, l3doc needs a complete overhaul to be usable across all our applications. Also Lua code is basically un-documentable (properly) with l3doc. One day...

9:12 PM
@PhelypeOleinik It's all Will's fault

@UlrikeFischer What would be a good syntax to document keys? Three options come to my mind: 1) Use \key{module/name} all the time, 2) declare \newkey{module/name} then use \key{name} elsewhere, or 3) assume module=@@ and use \key{name} everywhere
@JosephWright Waiting for me to rewrite and redirect the blame :)
\blame_redirect_module:nnn { l3doc } { Will } { Phelype }

\def\blame_redirect_module:nnn#1#2#3{Ulrike}

@DavidCarlisle Seems like a good implementation to me :)

@PhelypeOleinik tricky getting all these nnn right isn't it?

@DavidCarlisle :)

9:22 PM
@PhelypeOleinik hm, well I guess the last but with the option to overwrite it. But if you want to cover hooks etc too, one need some more generic variant, where \key is then a more special case.

@UlrikeFischer Yeah, most likely all the same machinery, but \key sets something like \l__codedoc_type_tl to key and \hook sets to hook, then use that when indexing. Want to open an issue for that?

@PhelypeOleinik \cs_new:Npn would have been better than \def

@UlrikeFischer That was @DavidCarlisle butchering expl3 conventions

@UlrikeFischer bah humbug even @PhelypeOleinik would have managed to get #1#2#3 right first time, but counting n is tricky

@DavidCarlisle You could have avoided the counting with \cs_new:Nn ;-) Is "humbug" an english word too?

9:34 PM
@UlrikeFischer yes, usually prefixed by bah most famously exclaimed by Scrooge in Dickens' Christmas Carol.

@DavidCarlisle :)

@DavidCarlisle I just learned that it is actually english and that we stole it in the 19th century.

@UlrikeFischer naturally

OP says it doesn't work with MiKTeX

@PhelypeOleinik works fine for me--I just wanted to write the same as answer.

9:43 PM
@UlrikeFischer Sorry :)
@UlrikeFischer OK, so no MiKTeX issue. Let's see the log...

10:00 PM
@PhelypeOleinik as expected ... but I will write the author of the package.

@UlrikeFischer Ah, good. Thanks

10:11 PM
@PhelypeOleinik @UlrikeFischer Thanks always for your interest to you and everyone.

1 hour later…
11:34 PM
@JosephWright How do I tell l3build to copy a file to the installation dir? (I want to copy an unpacked xparse-generic.tex to the tex tree of xparse)
installfiles doesn't seem to be it

@PhelypeOleinik It should be ... exactly what do you have?

@JosephWright Hold on, I'll push to the (latex3) cmd branch
@JosephWright Pushed. Running l3build install in l3packages/xparse doesn't copy xparse-generic.tex over
@JosephWright Funnily enough it copies the other two .sty...

@PhelypeOleinik The are not being DocStripped so they need to be in sourcefiles too
@PhelypeOleinik as the standard set up is *.sty`

@JosephWright Ah
@JosephWright Okay, that did it. Thanks!

@JosephWright "setting the right global variables" :-)