« first day (3354 days earlier)      last day (139 days later) » 

5:46 AM
@UlrikeFischer -- I agree with @DavidCarlisle. There isn't any such thing as a "layer interface", at least nothing common, so a hyphen isn't helpful. "Programming layer" is the proper association; it's common enough that a hyphen isn't really needed, but it enforces the association. A similar situation (but without hyphens), from my long-ago linguistics studies, illustrates the desirability of proper parsing: "light housekeeping" vs. "lighthouse keeping".
5:56 AM
@UlrikeFischer -- "Native English speaker" is rather more slippery. It's readily rearranged as "native speaker of English", so if someone insisted on a hyphen, I'd put it in "English-speaker" (but I'd really prefer no hyphen). There's an organization, The English-Speaking Union, which is hyphenated as indicated. Getting the right association is the important thing.
4 hours later…
9:34 AM
@barbarabeeton English is funny (says the German).
@Skillmon I realise that the interpretation of inter-word spaces would seem alien to you.
@DavidCarlisle there can be spaces in between letters? I thought that big key on my keyboard was only meant for navigation purposes.
@Skillmon start from there, move slightly up and to the left and you should find a z key.
@DavidCarlisle this one? yyyyyyy.
@UlrikeFischer exactlz
9:42 AM
@DavidCarlisle for me it is directly over that strange long key: zzzzzzz (remember, I'm weird and use some non-standard layout: neo-layout.org)
@DavidCarlisle "löuäwtk" is what happens if I type "exactly" on the locations of QWERTY.
3 hours later…
12:58 PM
@Skillmon "löuäwtk" looks almost how a drunk swede would write LuaTeX in Swedish.
@mickep then it's decided, I'm a drunk Swede.
@Skillmon Ohh, welcome to the club.
@mickep I can't speak Swedish though... Jeg elska TeX?
ooh Swedish
@Skillmon Jag älskar TeX, so close!
1:05 PM
@mickep :( Only remembered how it sounds (probably in Danish)
@Skillmon Ah, then it is closer, if not, correct.
@mickep at least I can't tell the two languages apart.
@Skillmon Hehe, I live ~30 minutes by train from Denmark, and I can tell them apart. Swedish is the language I understand when it is spoken, Danish is the other one. :)
@PauloCereda Ohh, hello!
@mickep are they that different? I thought Swedes would understand Danish -- at least a fair share of it like we Germans understand a fair share of Austrian or Swiss German)
@Skillmon The spoken Danish is difficult to understand (without practice), but written is easy.
1:12 PM
@mickep I see. Well actually to really understand Swiss or Austrians we have to get a bit of practice as well :)
1:28 PM
@mickep ooh hi
2 hours later…
3:06 PM
@Skillmon -- Even though it's my "native" language (@DavidCarlisle will, of course, disagree), I think it's not only funny, but downright peculiar. English speakers will steal from anybody, often with mutually unintelligible results.
@Skillmon Tenho um problema semelhante ao entender as tentativas de @PauloCereda em português
@DavidCarlisle oh no
@PauloCereda so how good was my Portuguese?
@DavidCarlisle razoável. :)
3:14 PM
@barbarabeeton aren't you a native speaker of English simplified? :)
3:25 PM
@Skillmon -- Not simplified; adapted and transmogrified. Some words look and sound the same, arise in the same context, and are used with exactly opposite meanings; viz. "table", as a verb in committee or parliamentary usage. And of course there's different local vocabulary. But the syntax remains the same, and (especially) if you're reading an academic disquisition, is equally obfuscatory.
3:37 PM
Hello friends.
When we use \to \dots \to the dots between \to are well vertical aligned. How to obtain the same but with \xrightarrow{} instead? I know that we can use \cdots but I'm wondering if it is possible to keep using \dots.
I suppose that \to and \xrightarrow have different categories.
4:00 PM
@Sigur \longrightarrow is prefixed with \DOTSB but \xrightarrow is not hmmmm @barbarabeeton
Did it ever occur to you that fat chance and slim chance mean the same thing?

Or that we drive on parkways and park on driveways?

[paulo@cambridge ~] $
@PauloCereda I'm fairly sure I've never driven on a parkway
@DavidCarlisle ooh
@PauloCereda it's a railway station with a car park (for English speakers)
How does one get an \endinput at the end of a file created with l3docstrip. Is there any possibility?
4:08 PM
@DavidCarlisle, so, thanks. Lets see what happens.
@Skillmon you can always add it as source code
@DavidCarlisle doesn't look like it. If it is enclosed by \begin{macrocode}...\end{macrocode} it still doesn't end up in the created file.
@Skillmon how can that be? It's not as if docstrip vets the code and only adds code it likes? not that I have looked at the l3 version recently
@DavidCarlisle it looks like the \endinput inside of macrocode gets actually evaluated (no idea though)
@Skillmon Can you log an issue with an example?
4:14 PM
@JosephWright in the l3 github?
@Skillmon Please, yes
4:26 PM
@DavidCarlisle (and @Sigur) -- Makes sense that the two arrows should be treated the same. I'm not sure when \xrightarrow (which is based on \ext@arrow) became part of amsmath, and it's not easy for me to check. But it seems to me that incorporating \DOTSB in \ext@arrow should be seriously considered. (Don't remember anything being submitted to AMS tech-support about this.)
@JosephWright issue created.
@barbarabeeton, @DavidCarlisle, thanks for attention.
@PauloCereda -- Although "fat chance" and "slim chance" do mean essentially the same thing, the occasions on which each is used are quite different. "Fat chance" is usually used (at least in my experience) sarcastically; "slim chance" is more appropriate for a factual utterance.
@barbarabeeton oh
@JosephWright WAIT WHAT
@JosephWright good to see BBC keeping on top of the important news
5:19 PM
@DavidCarlisle Auntie
@daleif AGDQ is on, if you are interested. :) gamesdonequick.com
@PauloCereda you know nobody has called the bbc auntie since about 1956
@DavidCarlisle Daily Mail probably has
@DavidCarlisle Blame @JosephWright
@JosephWright I wouldn't know:-)
5:51 PM
  \draw (0,0) circle[] (1,0) circle;
If I remove the [], the above produces an error: Missing number, treated as zero.
That's odd, isn't it? It seems that the first circle reads ahead into the (1,0) part and gets confused. But that is not documented, as far as I can see. Bug?
@HaraldHanche-Olsen that is a side effect of an older, still existing syntax. You can use circle (1pt) for the radius. So you must protect the following coordinates.
6:24 PM
@UlrikeFischer Ooooh, I see it in the documentation now – at the end of section 14.6. Urgh.
6:40 PM
@mickep Jag är TeX-fan. Vad fan är du? ;-)
@HaraldHanche-Olsen Akta så jag inte drar fram Norge-visan! :)
@Skillmon sorry about @UlrikeFischer spoiling the party with documentation references again:-)
@mickep Off-topic her, hvis den ikke handler om ender, pizza eller der Bär.
@DavidCarlisle well actually it is not in the (user) documentation but in the commented code so you could reopen the party by suggesting that it gets properly documented so that the non-existing people reading the manual can find it ;-)
@HaraldHanche-Olsen Offtopic, then.
6:48 PM
@DavidCarlisle True Englishmen attack each other with fish, not with seagulls. (@PauloCereda)
7:00 PM
@HaraldHanche-Olsen ooh MP
7:27 PM
@DavidCarlisle yes, lets blame her.
7:41 PM
@PauloCereda SLAP!
@HaraldHanche-Olsen ouch
@PauloCereda it's good that ducks are good swimmers
@HaraldHanche-Olsen ooh
8:08 PM
Mornings, and happy new years to y'all!
8:24 PM
It has been three days I was so much interested in learning programming and coding in LaTeX and Tikz that I could not focus on my main career and papers... I wonder!
Kind of TeX side effect I think! :))
it's easy to get TeXcited.
@EnthusiasticEngineer My second highest voted answer:
A: What are the most common mistakes that beginners of (La)TeX and Friends make?

David CarlisleThe most common mistake is spending too long on TeX coding and not getting the document written.

@FélixGagnon-Grenier exactly!
@DavidCarlisle upvoted it. Is it a mistake indeed?
I mean, at some point coding became more interesting than the main paper of mine! :))
@EnthusiasticEngineer I used this once in a talk about "why using latex":
8:42 PM
@UlrikeFischer yes... it is kind of procrastination with a very good reason behind... TeX does worth it!
@UlrikeFischer do you have content of your talk available? The topic seems interesting.
9:12 PM
is it me, or is there really Elvish in the style of the tex stack?
@FélixGagnon-Grenier It's Elvis, yes
9:30 PM
@egreg Hi prof. Excuse me for this intrusion but I have occured of you help to traslate a question on Math.SE. math.stackexchange.com/questions/3499665/… Into this site in italian language "https://www.matematicamente.it/forum/asintoto-obliquo-t56608.html there is written "punto di accumulazione al finito" and "punto di accumulazione all'infinito". How can I translate it?
@Sebastiano I have never heard about “infinite accumulation points”.
@egreg I don't even :( Excuse me if I took your time. Thank you very much.
@Sebastiano Remove your question, please.
@Sebastiano The site is just saying that the domain of the function is not upper bounded.
@egreg "Comandi comandante" :-)..done!
@Sebastiano Talvolta si dice che +inf è un punto di accumulazione del dominio. Lo faccio anch'io. È solo un modo di dire.
2 hours later…
11:16 PM
Hello everyone,

Sorry for asking this naive question: for the following, if I want the spacing between two consecutive lines to be exactly measured as 1cm on the printed paper, what I should write inside \\[ ]?

\foreach \i in {1,...,10} {\noindent\rule{\linewidth}{\SolLineWidth}\\[ ]}
@Diaa if you mean baseline to baseline then [\dimexpr1cm-\baselineskip] or more simply set \baselineskip to 1cm and don't use [] at all
@Diaa if you mean the gap from the bottom of one rule to the top of the next you need an extra \SolLineWidth of space
11:43 PM
For the following, the output PDF in 100% zoom doesn't tell me the lines are exactly separated by 1mm.

\foreach \i in {1,...,10} {\noindent\rule{\linewidth}{0.2pt}\\}

« first day (3354 days earlier)      last day (139 days later) »