@PauloCereda Are you running this chat? ;-)

If I use \tikzfillbetween[of=first and second,split,every even element/.style=...]{black} is there a possible value for ... to not use any fill on the even elements (so keeping the full transparency of tikzpicture)?

@DavidCarlisle The luaffi-article is open: guitex.org/home/images/ArsTeXnica/AT023/luaffi-article.pdf

@marmot quack :)

@AlanMunn Hi, Alan. No, <repo-root>/.git/.githeadinfo.gin is the right place. IFIRC that changed from gitinfo to gitinfo2.

ooh @Brent is here

@PauloCereda LOL. Sounds like playing Zork

@Brent.Longborough :D

@Brent.Longborough Hi Brent, yes, I understand that's where the file ends up, but the supplied sample script is supposed to be in the hooks directory, so the path in the script didn't work for me as written.

@AlanMunn Oh dear! That's weird, though. My understanding has always been that git runs in the root directory of the repo. And no-one has ever reported incorrect behaviour before. What does git version say?

@PauloCereda THESIS quae sera tamen!

@Brent.Longborough git version 2.14.3 (Apple Git-98)

@Brent.Longborough Hi! Long time no see!

@egreg Yeah, I've been too busy... I'm afraid I've lost touch a bit.

@Brent.Longborough Maybe I've just overinterpreted the documentation.

@AlanMunn Have you actually tried it (no offence!)

@Brent.Longborough You say "The gitinfo2 package includes a sample hook (placed in your git hooks directory), which extracts metadata from git and writes it to a TEX file"...

Yes

@AlanMunn Do you think that needs clarification?

@Brent.Longborough I interpreted that to mean that I should make a directory hooks inside the .git folder to put the scripts. Maybe that's what wasn't needed.

@Brent.Longborough So yes, I got it working, but because the scripts are in my hooks directory they needed to be modified to write to the correct place.

@AlanMunn Oh, could you paste the last (redirection) line?

@AlanMunn BTW, in a "normal" git rep, the hooks directory should already be there, full of .sample hooks.

@Brent.Longborough In the supplied script you have ` ]{gitexinfo}" HEAD > .git/gitHeadInfo.gin` which I changed to ../gitHeadInfo.gin.

@Brent.Longborough Mine have all been created with SourceTree which doesn't seem to generate one by default.

@AlanMunn Good choice. I've just tested creating a new repo with ST (mine is Windows), and the hooks dir and samples are all there.

@AlanMunn Where does .githeadinfo.gin end up in this case?

@AlanMunn AFAIK, my SOurceTree defaults in this area are unchanged

@Brent.Longborough It ends up in .git/ of the repo.

@AlanMunn That's strang. MacOS is basically BSD, amiright?

*Strange

@Brent.Longborough Yes.

@Brent.Longborough But none of my repos have a hooks directory unless I create one.

@AlanMunn git config --path --get init.templatedir = ?

@AlanMunn This may be of use: stackoverflow.com/questions/7065224/…

@Brent.Longborough returns nothing

@AlanMunn I'm sorry, I'm lost, then. If you code the hook precisely as in the sample, where does it actually go? (Or maybe nowhere, as there's no .git directory "in the right p[lace"?)

@Brent.Longborough Yes, I think it fails to generate the file with the script as written.

@AlanMunn I'm sorry, it's time to walk the doggo. If you like, by all means open an issue on github, ços I relly need to revisit gitinfo2! Meanwhile, perhaps you could add, for temporary debugging purposes at the start of the hook pwd > funny.name.txt and echo $0 >> funny.name.txt

Or we can continue here later

@Brent.Longborough Ok. It will take me a few days since I'm about to start a conference so I'll be unavailable this weekend. Thanks.

@AlanMunn OK, don't worry, whenever you can.

@Brent.Longborough :D

Apparently the \counterwithin in the new latexformat does not work as expected: github.com/latex3/latex2e/issues/38

which basically breaks memoir. Sadly I never tested the new format myself.

@daleif We'll e able to sort that in PL3 ... @DavidCarlisle???

@JosephWright PL3?

One issue would probably be that this error is now in MacTeX18 and and the TL18 ISO

@daleif Let's blame @DavidCarlisle

@egreg well, we have to, but it'll be me the mad memoir users will go after... Well, mistakes happen, and people should always remember to update, luckily there is a three line temp fix because the code is still in memoir.

"the mad memoir users" :D

@mickep they do exist

@egreg you can use git blame and it will blame someone else

Hello, could someone tell me what's wrong here

@DavidCarlisle Joseph?

I was having trouble with my bibtex yesterday, so I thought I would uninstall MikTex and then reinstall it to see if that fixed the problem. But when I try to reinstall I get this error. I am quite worried.

@Gragbow Well you now learn that deinstalling and reinstalling can make problems worse. initexmf can fail for a number of reasons (and some of them are actually harmless) but it is more difficult from far away to find out what happened than when e.g. bibtex fails where you can simply look at the blg. Check if pdflatex works.

@UlrikeFischer I have no latex programmes anymore though.

github.com/latex3/latex3/issues/452

@UlrikeFischer I only uninstalled because you said you had no problem when I sent the file to you. So that made me think there was something wrong with my MikTex so I thought uninstalling would be the best option, now I am in more of a predicament

@Gragbow Your error message gives no clue what could be wrong, and I really don't have the time to guide you through an investigation. Install texlive or try the miktex portable. Btw: Whatever was wrong with your bibtex files will probably reappear after the installation.

@JosephWright looks like it will be needed I'm just on the phone today so can't really check anything

@HaraldHanche-Olsen regarding your placement bug with stix math. This is my output with luatex 1.08 which just came out:

\documentclass{article}
\RequirePackage{fontspec,unicode-math}
\setmainfont{STIX Two Text}
\setmathfont{STIX Two Math}
\begin{document}
$\gamma_{e}\ne\gamma_{\symrm{e}}$
\end{document}

(with \symrm, not \mathrm!)

@HaraldHanche-Olsen with luatex 1.07 the placement is wrong, so it looks as if it really was an engine bug (in context with cambria it works now too).

@UlrikeFischer Hooray! :)

@UlrikeFischer Ah, excellent! (But I will stick to TL2017 and luatex 1.07 for my current project, for I am getting ready to ship it and value stability over anything else right now.)

@UlrikeFischer Thanks for your help! I'll try and use TexLive

Could I just ask why Uninstalling MikTex and then reinstalling it causes it to break

Seems a bit stupid

@daleif and @JosephWright -- i've gotten a report via ams tech-support that there's a problem with counters. it was reported with amsbook, but that's just a coincidence i think; i think it may be a conflict with \numberwithin in amsmath, and i'm trying to boil the report down to a tiny example to send you.

@barbarabeeton I thin people were discussing counterwithin earlier today. I'm on phone, so I cannot scroll up easily at the moment.

@mickep -- yes, that's what my comment was responding to. (but thanks for the pointer.)

@barbarabeeton oh, sorry. Did not see. Hope it will get resolved...

@mickep -- yeah, so do i. (i've already spent two days on the debugging, but without a usable 2018 installation -- the latest i've got access to is 2016 -- i have to keep going back to the submitter of the report. fortunately, he's very cooperative.)

Doctor Strange is a strange movie.

@PauloCereda You got mail (but not very constructive I guess).

@TeXnician in spam, but arrived. :) Let me check the paths.

@PauloCereda How could I have guessed ;)

@TeXnician :D

@PauloCereda Doctor Strangelove is a classic, but Doctor Strange? Never heard of it.

@HaraldHanche-Olsen Marvel, I guess. :)

@PauloCereda Oh. Should have googled it. I thought you were just confused.

@TeXnician: the FX path fixed it. :)

@TeXnician: deeply sorry, I wasn't aware there were hardcoded paths.

@PauloCereda Great. I really should not use local paths in build scripts I distribute ;)

@PauloCereda It's not your fault, but a pretty obvious copy & paste error from private projects.

@PauloCereda I just saw your post on depositing the thesis. Congrats on finishing the MS, when are you going to start writing your PhD thesis ;)

@TeXnician No worries. :) The non-existent class error suggested me it was a missing dependency. I was almost sure it would fix it. :)

@StrongBad Thanks. :) And that was actually the PhD thesis. :)

@PauloCereda Actually you don't even need that dependency :D

Hi, I'm currently downloading TexLive and it's taking ages to install. Is this normal?

@Gragbow That depends what you install. scheme-full does take ages (and should be the default) as it downloads the full TeX distro.

Guess that's what I've done lol

Woops

@TeXnician /gasp

@UlrikeFischer I tried to download TexLive and ended up getting a similar error message as before ¯_(ツ)_/¯

I have a bash script for parsing text files that has grown out of control with hundreds of calls to sed and few to awk, perl, and other tools. The number of things I have to extract and the number of files I have to process means it takes forever. Is perl still the best thing to use with regex heavy code or can I get away with something like python?

@StrongBad I'd say Python is your friend for it user-friendliness

Is there a good way to check whether graphicx is loaded (the test should be false if only the graphics package is loaded)?

\@ifpackageloaded{graphixc}{<true>}{<false>}

@Gragbow You mean regarding the bibtex problem? Your files were fine, one only needed to run pdflatex on main.tex twice to get the references.

@StrongBad thank you very much! (why didn't I know that command...)

@UlrikeFischer No I don't mean that. You know that error I was getting when I tried to reinstall MikTex? Well I tried to install TexLive and I'm getting a similar error. I am currently unable to run any latex documents

@Skillmon there is a whole bunch of cool stuff in latex-project.org/help/documentation/clsguide.pdf

@Gragbow Sorry but texlive never, really never would give an error with initexmf in it.

@UlrikeFischer Ok, sorry, let me rephrase. TexLive gave me an error, but I accidentally clicked off it before I could copy it. This is so frustrating. but basically the error wouldnt let me install TexLive

@Skillmon there is also a version that can be used after \begin{document} in ctan.math.washington.edu/tex-archive/macros/latex/contrib/…

@yo' it looks like python has a pcre package so it can probably handle any expression I can figure out how to write.

@StrongBad no need for that, but thank you anyway :)

@Gragbow I hope you know that without exact error messages nobody can help you ...

@UlrikeFischer I know, I'm reinstalling it now, but it takes a couple of hours lol

@Gragbow When I do a fresh install, I clone the mirror with rsync first and then install directly from that as a local repository, that way when something crashes it is much quicker to reinstall. I think it is close to the same download size since I install the full version.

Hello, could I ask for some help with a small question I have? I

Im using \begin{compactitem}. In the first \item, I would like to write some things, and then on the next line I would like to write some things, but align it a bit to the right. How would I do this?

Nevermind, I got it.

A wonderful way to end the Friday ↑↑↑

@DavidCarlisle and @daleif -- i've just sent (to david) a test showing a nasty effect of the newly incorporated chngcntr in tex live 2018 (comparison file run with 2016). hope it's useful in tracking down the problem.

@barbarabeeton can I get it too?

@UlrikeFischer -- copy on its way, provided nothing goes wrong.

@barbarabeeton Thanks, I'm always interested in such errors, in case I see it in some question.

@barbarabeeton not at pc at the moment, is it more than the missing dot in counterwithin?

@daleif @barbarabeeton well the new definition redefines \theXXX globally, which imho is more logical as the resetting of the counter is global too. But I don't understand why \counterwithin is used here. It looks as if it is used only for the side effect on \theenumi. Why not simply

\newcommand\StartLabelItem[1][theorem]%[1]
{\def\labelenumi{\csname the#1\endcsname.\theenumi:}}