Adam Liter

Hope you have a good weekend too!

Thanks for all your help. I really appreciate it! I'll try looking into your two suggestions when I have more time.

I also unfortunately need to go in the next couple of minutes, but I really appreciate all that you've done to help me so far.

I stepped through all parts of pdf-view-revert-buffer both having run C-c C-l and having not run C-c C-l, but I didn't see any differences.

Okay, I'm now inside the defun for pdf-view-revert-buffer.

Oddly, it has the same value in both cases: #<buffer cp_tp_proposed_experiment_design.pdf>

I enter the defun in either case. And in both cases, the value for file is correct. However, when I've pressed C-c C-l, the PDF buffer doesn't revert. When I haven't pressed C-c C-l, it does revert.

I just tried it again with the debugger active, and even when the debugger is active, if I press C-c C-l, then it doesn't work. But if I don't press C-c C-l, then it does work.

Yes, I think I've discovered what the issue is. This might be a bug in AUCTeX. It works, so long as I do not press C-c C-l to display the results of the compilation. If I do press C-c C-l to see the results, then it will not automatically revert the PDF buffer.

It switches to the buffer with the PDF. Though this time the buffer seems to have actually reverted for me ... In the past, it has not, and I don't think I've done anything differently.

That returns pdf-view-mode.

Yes, buf is set to #<buffer cp_tp_proposed_experiment_design.pdf>. I'm now about to execute the (with-current-buffer buf line.

Sorry, I don't mean to make the chat complicated for you. But thank you. I really appreciate your help with this!

That returns the correct file path to the PDF document.

Sorry, just to clarify, should I be typing just "file" in the minibuffer and then hitting <RET>, or should I be typing "input file" in the minibuffer and then hitting <RET>?

Yes, the point is at the beginning of the first line with code inside the defun. That line has the following code: (let ((buf (find-buffer-visiting file)))

Okay, I've done that, and I just ran adamliter-TeX-make, which opened tex-buf.el at line 1014, which is the first line of TeX-revert-document-buffer. What should I do next?

No, I haven't. I'm still pretty new to Emacs and elisp. How do I debug TeX-revert-document-buffer?

Hi @Tobias, thanks for your help with this question.

@PauloCereda Lol, I also don't know anything about Java, so it's probably me ... But thanks! I'll update the issue sometime today with more info on the other options to knit().

@PauloCereda Thanks! That works. I should have asked you sooner. 😔😜

@PauloCereda No rush to respond. Take your time! I know you're busy.

@PauloCereda I procrastinated ... 🤪 github.com/cereda/arara/issues/112

@PauloCereda Okay, sounds good. Perhaps I'll send you an email this weekend. I have some other stuff I need to work on today. Thanks for the quick discussion though! 🦆

@PauloCereda Or is it possible to inject the correct file name into the (pdf|xe|lua)latex invocation using getBasename and the files parameter?

@PauloCereda Yes, I think so. But then one will also (I think?) need custom (pdf|xe|lua)latex rules that only use the file base name and not the file name, since the standard workflow with knitr is to edit a .Rnw file, compile the .Rnw file to a .tex file with knitr, and then compile the .tex file to PDF with a LaTeX engine.

@PauloCereda I think I might have some time this weekend where I can help. I can try to look back through my emails with you, too. I'm pretty sure you already had a working knitr rule with arara 4.0 at some point in time ...

@PauloCereda tex.stackexchange.com/questions/175311/… 🙃

@JosephWright Yeah, that makes sense. Thanks for the info and discussion! 😊

(With the caveat, of course, that people should update to the latest version. But I find that many new LaTeX users don't often do that ...)

Then I could show people who view the tutorial which versions of TeX Live they can expect the examples to work with.

@JosephWright Thanks for the info. I think you could in principle do the same thing with Docker and just run tlmgr update in the Docker container before compiling or testing anything. There's probably no good reason to (dis)prefer this, though. But I was thinking about Docker because I'm considering building out some images for recent versions of TeX Live in order to test example code for a LaTeX tutorial that I have.

@PauloCereda Hahah, that's a great picture. I'm good. In a hurry, too. I'm trying to get a lot of stuff done before classes start back up again for me ...

Hi @PauloCereda! 🦆 How's it going? Congrats again on the arara release. 🙃

@samcarter Thanks! This looks really helpful.

And thanks @samcarter. That link is helpful. I've come across a few other one-off Docker images like that, but I was hoping to find a set of images for at least the last few versions of TeX Live, too. But I'll probably use the one you linked to and some of the others I've found for inspiration when making images for a couple of the recent versions of TeX Live.

Thanks @egreg.

Does anyone know if there are canonical/official Docker images for (past and) present TeX Live versions? (Maybe @egreg, @DavidCarlisle, @JosephWright, or others would know?) I didn't see anything from a quick google search, but maybe I missed something? 🙃

@PauloCereda 😊🎉

@PauloCereda And yes! I've been following the development of it a bit, and I'm excited for it to be released. :)

@PauloCereda Good luck with the thesis! I'm sure you'll get it finished. :)

@PauloCereda Sounds like politics ... lol. Anyway, how are things going for you? Is your thesis going well? :)

@PauloCereda lol. :) You seem to be in disagreement with yourself! :P

@JosephWright Interesting. Thanks for the reply. That's good to know! :)

@AlanMunn Feel free to weigh in if you have further thoughts or suggestions for them (or if you think anything I said is wrong :P).

@AlanMunn I ended up saying something here: github.com/langsci/latex/issues/50

I want to make sure I have this right before I say something that is wrong. :)

When one submits a package to CTAN, not all of the files have to go into the same directory in the TeX Directory Structure, correct?

@AlanMunn And thanks for saying that about the testing. Hopefully it won't take too long. It'd be nice to try to wrap this project up.