Shouldn't this answer tex.stackexchange.com/a/285837/101651 be closed as not-an-answer?

And this useless one: tex.stackexchange.com/a/406128/101651?

@CarLaTeX well it's an answer, just wrong, on other sites it would have been downvited to -500 by now, but we're too polite.

@DavidCarlisle LOL, hence is the correct action to downvote them?

@CarLaTeX Zapped

@CarLaTeX That's the network model, yes: downvote bad answers

@CarLaTeX Where they are objectively wrong, we have been happy to simply delete

@JosephWright Thank you, I downvoted the other one.

@DavidCarlisle ooh :)

> Microsoft has added its own ssh client to Windows

wow

@PauloCereda With a delay of 20+ years...

@TeXnician That's what I thought. :)

What's the best way to get a starred version of a LaTeX3 environment so that it functions the same as a 2e one? This old question has an answer, but is it still valid?

@Robbie well the question there was specifically asking about using an s argument spec but I'd have thought the most natural way is just to define the environment as normal. for example tabular* is just an environment name, it is not a * form of tabular in the way that \section* is a star form of \section.

@DavidCarlisle I was looking at more towards the latter case, defining a starred version of an environment as being an unnumbered version of the unstarred environment.

@Robbie We did at one point try that (turning a trailing star into an argument): didn't really work

@Robbie sure but in for example align* compared with align the two environments are quite separately defined, but using common internal code. It is not that align looks for an optional *. so you can do same in l3, your expl3 internal functions handle both cases, then make two xparse declarations for the top level environments

Ok, that makes sense

I've got a long way to go before I grok LaTeX3

That being said, I don't think I really grok anything… but I guess one should start somewhere, right?

@egreg Why does this answer of mine work also without \makeatletter/\makeatother? What have you done in xpatch? :)

@campa The function \xpatch_main:NN starts off by doing \tl_set:Nx \l__xpatch_name_tl { \cs_to_str:N #2 }; here #2 is the macro to be patched. I need the stringified name in order to do later processing. What happens without \makeatletter is that \@ is stringified, but not setref. If you try \xpatchcmd\@setref{}{}{}{} you'd get errors.

@campa In the further processing only \l__xpatch_name_tl is used.

@campa Maybe I should add a check that the argument is a single token.

Something else to distract @PauloCereda from writing his thesis.

@AlanMunn LET'S DO THIS BOIS

some people use paint, some tikz, and some an Airbus A380

@DavidCarlisle wow

@DavidCarlisle Looks a lot like picture mode.

@AlanMunn probably more expensive

@DavidCarlisle Not quite as portable either.

@AlanMunn ^^ :)

And one for @yo':

@yo' ^^ PRAGUE <3

@PauloCereda :) nothing surprising, I know Prague is perfect :)

@PauloCereda It's a cute comment. \begin{soapbox} But the argument being made is total crap. Of course there are bad journals, and some of the open access ones like PLOS One are exactly that, but this is not cause and effect. And being a Society Journal doesn't preclude being Open Access. \end{soapbox}

@yo' I went to a conference in Sorrento, it was raining like mad.

@AlanMunn You are right.

@PauloCereda Two of the best journals in our field are now open access. One was formed when the entire editorial board of a major Elsevier journal (Lingua) resigned and created their own open access version (Glossa). The old one is now called Zombie Lingua. :)

@AlanMunn Damn those tongues. :)

@JosephWright @PauloCereda How can I tell l3build to copy a sty into the ctan-zip? I don't have a dtx or an ins, only one simple .sty in the build folder and it refuses to go into the zip ;-(.

@UlrikeFischer you could classify it as doc and add it to docfiles I think?

@UlrikeFischer or for graphics-def where nothing is extracted from doc we have

-- Just the one file to worry about
installfiles = {"*.def"}
sourcefiles  = {"*.def"}
typesetfiles = {}

@UlrikeFischer Like @DavidCarlisle says ;)

We could use some manifest...

/runs

@DavidCarlisle @JosephWright oh well. It should be "sourcefiles" not "sourcefile" ;-(. (btw: I tried at first with typesetsourcefiles but then I got the sty only in the tds.zip. Is this normal?)

@JosephWright next you'll be accusing me of copying bits of code:-)

@UlrikeFischer The setting typesetsourcefiles is for where you have some DocStrip sources that need to be unpacked for the docs, but not for installation in the TeX tree. Not sure whether it ends up in TDS doc or sources (without looking)

@PauloCereda Rather the other way around: the manifest is a result of the various matches from the variables

@JosephWright you are no fun. :)

@JosephWright how can one add a date to the zip name?

@PauloCereda I guess that what you mean is one approach to a manifest is to use it to work out which files are 'live'

@UlrikeFischer At present, you can't: never been needed

@JosephWright On a more serious note, yes. :) I was thinking towards a spec itself. :)

@JosephWright I guessed that he was just trying to stir up trouble

@PauloCereda Doesn't work with wildcards: doesn't that result in more work?

@JosephWright ah ok, so that's why I didn't found it. Btw I think this variable is a typo: "sourcfiledir".

@UlrikeFischer Quite possibly :)

@JosephWright It depends on how post handling happens. :) And yes, it's more work.

@PauloCereda I meant that somewhere the user had to set up the spec. With the current approach, we can have defaults as wildcards and they largely work, and from those one can generate a file manifest (of greater or lesser complexity). If you start from the manifest, doesn't the user have to type in the name of ever file they want?

@JosephWright I don't follow, sadly. I think widcards can be used wherever need. :)

I want an iMac Pro...

@PauloCereda You do realise that with a Portuguese pronuciation, iMac will require you to change editors to match it.

@AlanMunn ooh that's very evil of you :)

@PauloCereda :)

@AlanMunn I have it installed here, but there's an evil layer. :)

@PauloCereda Well a manifest is meant to be a full list of all files, so you can't say *.sty you have to say foo.sty ...

@JosephWright hm

@JosephWright must admit I haven't followed the full details of the manifest stuff but doesn't the end result have to be the same as saying build ctan ;unzip -l zzz.zip ?

@DavidCarlisle That's one view :)

@DavidCarlisle :)

@JosephWright David is clever

@DavidCarlisle Will is keen more on a 'full' manifest of what is in the source repo, including all of the test files, etc., and (optionally) with descriptions

@DavidCarlisle github.com/wspr/unicode-math/blob/working/MANIFEST.md for example

dl.acm.org/citation.cfm?id=3103015

@DavidCarlisle github.com/latex3/l3build/pull/34#issuecomment-351129006

@JosephWright yes, I know:-)

@DavidCarlisle :)

@DavidCarlisle I have to say my starting point was not dissimilar to yours: for example, in siunitx I list the source and derived files, which means they match more-or-less the TDS-style zip (though I have to admit that doesn't cover the README)

@PauloCereda nah you want to read this amazon.co.uk/dp/1108414451/ref=rdr_ext_tmb

@DavidCarlisle wait a minute, it's your area of expertise!

@JosephWright -- while trying to post an update to ctan for the amscls collection, i was severely chided by petra that the manifest file in the *.tds.zip must be identical to the one in the zip for ctan. (the manifest in the amsmath collection follows that dictum.) so if you're posting to ctan and the manifest files have different content in the tds and ctan (flat) versions, you are likely to get scolded too.

@PauloCereda my phd supervisors retired then had the time to spend 10 years writing a two book set, just came out:-)

@DavidCarlisle ooh :)

@barbarabeeton Interesting

@JosephWright -- if you get different treatment, please let me know.

@barbarabeeton Currently, I don't have a separate manifest, just a listing in the source (done by hand). Will is working on automation for l3build, but his aims are perhaps different ...

@barbarabeeton github.com/latex3/l3build/pull/34#issuecomment-351129006 and (bottom of) github.com/latex3/l3build/pull/34#issuecomment-351215091

@barbarabeeton it's OK: once l3build has implemented the ctan upload API it will automatically insert into the "additional notes" field "I'm a bot don't argue with me"

@DavidCarlisle @PauloCereda is on that ;)

@barbarabeeton I'll note this and explore with CTAN

@DavidCarlisle default_err = "I am a bot, blame Joseph Wright at " .. emails['jw']

@PauloCereda good plan, rot13 the source and he'll never find it.

@DavidCarlisle ooh

@StrongBad new avatar. :)

@PauloCereda the hats didn't fit on the old one and this one is wearing a lab coat which makes strongbad even badder.

@StrongBad :)

@StrongBad the what?

@yo' sorry, I meant to say this version is wearing a lab coat which makes strongbad even badder it also has a little space at the top of the picture so nothing gets cut off.

good evening. I have a quick question about custom font features and how to enable them in fontspec

anyone here who would be able to help me out?

I think my question has a very easy solution

@ClintEastwood don't ask if you can ask, just ask. People will answer if they know or (better, usually) ask on the main site

alright. I use a font developed by our dear Khaled Hosny. a few versions ago he added a font feature "ss05".

how can I use that feature with fontspec?

\newfontfamily\khaledsfont[xyz]{FontName}

this is what I use in the preamble for selecting the font

@ClintEastwood something like \addfontfeatures{Letters=UppercaseSmallCaps} but with the font and feature you want

by code I mean the "ss05"

@ClintEastwood isn't that the feature name?

@ClintEastwood oh it's probably StylisticSet={05} isn't it?

nice... at least it's compiling now. let's wait

@ClintEastwood see section 2.8.1 of fontspec manual

ah yes, did not see that.

I never used custom features that have no "names"

nice. works. fantastic!

@ClintEastwood what does it do? :-)

many thanks! (as also often before)

it places a vowel sign in Arabic script at a different place, above the word and not below the line

@ClintEastwood things are so much simpler in english:-)

that's why most of the book is in English

@StrongBad I should say sorry; I tried to make a joke on the fact that I ignore all this hat frenzy and the joke did not work.

@yo' I got the joke, but apparently you did not find my reply humorous which shouldn't be too surprising since you hate hats.

You know the only reason I use SE is for the hats and badges.

hello, someone know Arabetext?

@StrongBad I might have heard it before, yes.

Anyway, it's time to enjoy my free evening and go to bed to catch some sleep.