Sep 19, 2019 11:29
@JosephWright thank you. Have just raised an issue there
Sep 19, 2019 11:11
That info needs to be included in the CTAN page for the package
Sep 19, 2019 11:10
@UlrikeFischer thank you
Sep 19, 2019 11:04
@JosephWright may I ask a quick question? How do I report a bug with the biblatex-ieee package?
Feb 13, 2019 20:27
@DavidCarlisle I just have a single 20 line main.tex. It's difficult for the eyes to parse it when you have 21 other support files visually cluttering the project's root rolder. That is why I wish to move it over to their own subfolder
Feb 13, 2019 20:03
@DavidCarlisle There are 21 such files and they clutter the project directory
Feb 13, 2019 19:55
@UlrikeFischer Does merely dropping in all the .cls, .sty files into /tmp/texlive/texmf-local suffice without a full-blown TDS structure?
Feb 13, 2019 19:55
@UlrikeFischer thank you. And TEXMFLOCAL /tmp/texlive/texmf-local must be a standard TDS structure, right?
Feb 13, 2019 19:38
@DavidCarlisle Thank you!
Feb 13, 2019 19:37
@DavidCarlisle got it. Thank you
Feb 13, 2019 19:31
@DavidCarlisle thank you. So, just run a shell script in the before_install section?
Feb 13, 2019 19:29
@UlrikeFischer How do I set the TEXINPUTS environment variable in .travis.yml to prepend the local texmkf tree?
Feb 13, 2019 19:28
@UlrikeFischer so, on windows machine, use local texmf trees, and on travis, just set $ENV{'TEXINPUTS'}='./custom_cls_sty_files//:' . $ENV{'TEXINPUTS'};
Feb 13, 2019 19:20
@UlrikeFischer not good enough since the doc has to travel & build in Travis too
Feb 13, 2019 19:19
I am too scared to replace the files in the original texmf-dist folder
Feb 13, 2019 19:19
@UlrikeFischer Yes. I can't do that. The package on CTAN is not maintained anymore, and somebody on github has forked it and improved it, and I want to use that
Feb 13, 2019 19:16
@UlrikeFischer really quick question. For detection of project-specific .cls & .sty files in a subfolder, I tried the solution proposed in tex.stackexchange.com/questions/50697/… , but this does not work for me on Windows10. Any thoughts?
Feb 11, 2019 19:46
@UlrikeFischer and @DavidCarlisle I feel guilty that I didn't get around to posting a MWE for that luatex 1.07 vs luatex 1.09 issue
Feb 8, 2019 19:54
:)
Feb 8, 2019 19:52
@marmot can I ask a quick biblatex question?
Feb 8, 2019 19:52
hmm
Feb 8, 2019 19:48
was dangerous
Feb 8, 2019 19:47
in America
Feb 8, 2019 19:47
I remember my first experience with zero traction conditions
Feb 8, 2019 18:40
"historic-texlive is a set of scripts and binary executable for Unix for easy
and convenient installation of TeX Live 2008--2018. All Unix platforms are
supported. Windows (i386-cygwin, x86_64-cygwin, win32) isn't supported.
historic-texlive is useful for compiling old .tex documents reliably, to
reproduce the original output files (.dvi, .ps and .pdf)."
Feb 8, 2019 18:39
it looks like Peter Szabo has just solved my problem!
Feb 8, 2019 18:39
David had suggested to create a virtual machine
Feb 8, 2019 18:39
@DavidCarlisle and @UlrikeFischer remember my earlier query on completely archiving my Phd thesis for posterity?
Feb 8, 2019 18:09
I mean tex-live [at] tug [dot] org
Feb 8, 2019 18:09
emailed [email protected] even though I am not subscribed to this list
Feb 8, 2019 18:00
@UlrikeFischer yes, will do
Feb 8, 2019 17:55
Can't spawn "cmd.exe": No error at //icnas1.cc.ic.ac.uk/kg314/texlive/2018/tlpkg/TeXLive/TLUtils.pm line 2484.
Feb 8, 2019 17:55
Since yesterday's infrastructure update for TLMGR, things have broken for me (Windows 10). Now, I get weird messages like
Feb 7, 2019 21:13
1
Q: tlmgr update --self fails with a weird error message (Windows 10)

KrishnaI have TL2018 on windows 10. When trying to update packages with tlmgr, it said that tlmgr itself needs to be updated. However, the command tlmgr update --self failed for me with the following error message λ tlmgr update --all --self tlmgr.pl: package repository http://anorien.csc.warwick.ac.u...

Feb 7, 2019 21:12
Today's tlmgr update broke everything on my computer
Jan 30, 2019 20:44
Yes, and is there any way to do it for includepdf also?
Jan 30, 2019 20:33
Yes, in addition to the requirements posted in the question, I require that for all the includepdf pages in the document
Jan 30, 2019 19:41
I also filed a bug report for draftwatermark that it incorrectly places watermark on the foreground of included PDFs github.com/callegar/LaTeX-draftwatermark/issues/17
Jan 30, 2019 19:40
My PhD supervisor had asked for this specific requirement (watermark-free frontmatter) for internal distribution until the university releases the embargo on the thesis
Jan 30, 2019 19:39
@AlanMunn thank you. I already used Ulrike's solution
Jan 30, 2019 19:34
I have also filed an issue here for the author to consider providing this command here github.com/callegar/LaTeX-draftwatermark/issues/16
Jan 30, 2019 19:33
Since your solution truly stops watermarking
Jan 30, 2019 19:33
@UlrikeFischer Yes, that's why I accepted your solution over @marmot
Jan 30, 2019 19:24
Ulrike's solution is highly general, since it disables watermarking entirely at the required places, enabling us to manually control watermarking with includepdf type of constructs
Jan 30, 2019 19:23
Clearly, this is not a drawback of what you propose, but is simply the limitation of the package itself
Jan 30, 2019 19:23
In this case, the watermark gets drawn in the foreground, rather than the background. When the grayness level is set to 1, like you proposed, we can see outline of the watermark text in white!
Jan 30, 2019 19:22
@marmot Sorry, this is for yesterday's question about draftwatermark. Your solution works okay with the base case given in the question. Therefore, it is correct obviously and answers the question. But there are some cases where it fails completely. A notable example is when watermarking over a PDF imported into the document with the pdfpages package (includepdf )
Jan 30, 2019 17:01
@UlrikeFischer Ulrike, thank you for the answer. I have acknowledged its usefulnes in the comments section to your answer
Jan 30, 2019 16:57
@DavidCarlisle I can only accept one answer, but both answers worked for me