@FaheemMitha I wouldn't have guessed so but @PauloCereda and @Skillmon seem to claim it is a rabbit (I don't think they get out much to see real animals)
@HenriMenke thanks for the luatex patch, had you found that already or did you find it between getting my email and posting a reply (impressively quick if the latter:-)
\input hello
and
\input{hello}
both work but
\newread\1
\openin\1=hello
\ifeof\1 {\bf not found}\fi
\loop\unless\ifeof\1
\read\1 to\x
\x
\repeat
and
\newread\2
\openin\2={hello}
\ifeof\2 {\bf not found}\fi
\loop\unless\ifeof\2
\read\2 to\x
\x
\repeat
\bye
@yo' oh you are making the latex-dev releases available as well, I hadn't expected that (might even be worth a +0.9 to almost get you back in good books:-)
@daleif each compilation is dockerized for safety reasons; even if you managed to run rm -rf.... (you know what) from pdflatex, you wouldn't damage anything; the compilation would time out after 60 seconds and you'd get no output, and that's it.
@yo' given the number of users that mus mean many many servers. Perhaps I should consider using docker compilation for some of my PDF generating webapps.
@FaheemMitha well, the product is called Overleaf now. It used to be called WriteLaTeX. And there used to be a second project called ShareLaTeX, which merged in.
@DavidCarlisle no, not really. (I'm not the dev here, the only thing I care about is the texlive subtrees :-) ) But if you were really interested, I could probably contact you with some people here.
@FaheemMitha well, the company managed. (And we still keep TeXLive images from the old days for both SL and WL for compatibility.)
@DavidCarlisle haha. If you wish, installing the OL image might be quite easy and you already get a full texlive with it :-) (I have never done it myself though)
@PauloCereda I was trying to remember if it was the island thing or henri had announced docker images recently:-) so would a travis ci run using a docker tl image be quicker than just caching the tl directory in a basic travis vm ?
Hi! I just uploaded circuitikz 1.0.0-pre2... let's see if I can make a 1.0.0 on 20200202. Can I? Or it will be appropriation? (20200204 is also possible, it's a bittersweet date for me).
@DavidCarlisle I just cited you in the second line here tex.stackexchange.com/a/525337/38080 --- I do not know if you count the citations for you H index... ;-)
@Rmano yes there are no code changes planned , just sorting out final documentation things so pdflatex-dev should be pretty close if not identical to the main release.
dear community, I edited tex.stackexchange.com/questions/230112/… and believe the question is now sufficiently clear to warrant an answer. If not clear, please comment on what is not clear... cheers
@ingli I voted, but why run: ? when you say the #anchor is cut off so you mean you checked the internal link in the pdf or simply that your pdf viewer did not use it (that may depend on the viewer used, also does the run: http schema include fragment identifiers?)
@DavidCarlisle Thanks. I got curious about the run: ... I have seen such links in the past, but am not using the run: myself currently. I edit(ed) this question to learn about the case... I have now edited the question to specify that I used two pdf viewers. According to en.wikipedia.org/wiki/List_of_URI_schemes run is not an URI scheme.
I would have to check the PDF spec (or ask @UlrikeFischer, which is easier:-) but I suspect that this is as it should be and run and file protocols take a filename so # is not legal
@UlrikeFischer I'm a bit confused, if I compile from texlive-source on github I end ip withh 1.11.2 not 1.12.0 and ny test file fails, that would be OK, just wait for 1.12 tto be pushed to tl but the changelog already says
2019-07-27 Luigi Scarso <luigi.scarso@gmail.com> * Fixed \opein, to be consistent with pdftex in opening a file without extension (but not enclosed in {})
@DavidCarlisle I have in the experimental branch 1.12.0, Development id: 7264. And I just checked again: \openin\@inputcheck noextension doesn't work for me.
@DavidCarlisle but Luigi is doing $ cat test.tex so he isn't really testing a file without extension doesn't he?
@UlrikeFischer oh for **** do you want to reply (with a 1.12 test) or should I (although I only have 1.11, which is a bit odd as I did a git pull first, I thought, but perhaps it is not in the main texlive branch yet)
@JosephWright We in the end likely won't be removing [utf8]{inputenc}; a lot of our contents is commonly shared with people and places who have older TLs, such as arXiv.
We know it's not the optimal solution, but we think that at least as long as arXiv may need it, we better keep it as well.
@UlrikeFischer so if you reference a document that didn't use hyperref so only has two fields not 4 doesn't blow up (as far as i remember from my youth)
@UlrikeFischer not had time to look at the issue that just came in
@JosephWright yeah. Well, this is one that's difficult. You know well (and @DavidCarlisle even better) that you still meet people using \documentstyle :-) I think that once arXiv synchronizes to something that doesn't need utf8 inputenc, we will reconsider.
@JosephWright July hopefully (for TL2020) btw, will you be at Rochester?
@yo' I see. It would be nice to have a way to do that I think. Also, it's not obvious that that's what is happening. Although I understand the "no surprises" position, I think the default assumption of users is that as TL versions change, documents will use the current version not some older version.
@AlanMunn ah yeah. I'll make a note that this should be more explicitly written at least in the blog post
(remember that only in Sep'19 we upgraded to TL18, and only couple months before we finally merged the two previous platforms, so there's still some work with usability)
Ah the blog post's first two sections are: Will my existing projects work as usual? and How can I switch to TeX Live 2019 for existing projects? :-)
@yo' Yes, I understand. And those two sections sound good! I just wonder whether the number of people affected by having no direct path to upgrade a document is going to be greater than the number of people who would encounter problems with an existing document and an up-to-date system. I guess it does depend a lot on the packages you use.
@AlanMunn well, we decided that we prefer explaining users on support that their copied project does behave diffrently, than trying to find out that this project doesn't compile because it is supposed to be on TL2014 (yes, we do have such projects :-) )