Hi, Eberhard:
Please excuse: I've already solved this problem. "sudo rm
/usr/local/bin/pdflatex" did the trick.
You may be right that I should reformat my hard drive and
restore from my TimeMachine. However, that sounds too much like
"do-it-yourself lobotomy" to me. I don'
Spencer,
If you just google
https://www.google.com/search?q=uninstallpkg
the first link coming up is the right one. But see below.
Do you have a ~/Downloads directory? Did you look in there?
So the removing of /usr/local/bin/pdflatex did not remove the old 2019
version. Which is w
Thank you all for your comments on this. I'm overwhelmed, not
just with the volume of the discussion, but my own ignorance of the
standard command line protocols.
After trying some but on all of Eberhard Lisse's and Peter
Dalgaard's suggestions below, the problem disappeard after
Peter,
as far as I understand this the idea is to make the binaries of whatever
MacTeX you use available in
/Library/TeX/texbin
so that it survives the (annual) upgrade of MacTeX or a switch from the
Basic to the Big MacTeX or whatever.
I would personally not remove the pdflatex, but
Ah, yes,
brew install coreutils
:-)-O
Existing accounts using bash remain under bash when upgrading to
Catalina. And bash remains available so all bash script will continue
to run :-)-O
el
On 13/05/2020 15:44, Marc Schwartz wrote:
> Hi,
>
> I will stand to be corrected, but from wha
Hi,
I will stand to be corrected, but from what I can tell, 'realpath' is not part
of a default macOS installation, and would need to be installed from a third
party repo (e.g. homebrew).
There appear to be shell script incantations that would accomplish the same
functionality, but in the end
Not sure if this helps, but for some reason my TeX Live was not installed in
Library/TeX/texbin, but in:
~ % realpath $(which pdflatex)
/usr/local/texlive/2019/bin/x86_64-darwin/pdftex
> On 13 May 2020, at 16:34, peter dalgaard wrote:
>
> Hmm, like Eberhard, I'm not too sure this is right.
Hmm, like Eberhard, I'm not too sure this is right.
A look at ls -l /usr/local/bin should be informative though.
I haven't been paying that close attention, but I think the history is that TeX
programs used to live in /usr/local/bin, but then Apple did something(?) so now
they go to Library/TeX
Marc,
this is not necessarily correct, it can be a symlink, hence my suggestion of
realpath $(which pdflatex)
which will give you the final executable, in my case
/usr/local/texlive/2020basic/bin/x86_64-darwin/pdftex
But, I agree, this looks like an ancient installation :-0-O
Spencer,
FWIW, this may be a situation where you need to remove your current/older
installations of TeXLive and start fresh with a clean install of TeXLive 2020.
It is possible that there is some conflict or corruption of the current
multiple installations.
That 'which pdflatex' is pointing di
> On 13 May 2020, at 13:00, Spencer Graves wrote:
>
> Hi, Peter et al.:
>
>
> It looks like you've properly diagnosed my problem. How do I fix it?
>
>
> "which pdflatex" and "echo $PATH" are as follows:
>
>
> $ which pdflatex
> /usr/local/bin/pdflatex
>
>
> $ echo $PATH
>
realpath $(which pdflatex)
pdflatex --version
On 13/05/2020 13:00, Spencer Graves wrote:
> Hi, Peter et al.:
>
>
> It looks like you've properly diagnosed my problem. How do I fix it?
>
>
> "which pdflatex" and "echo $PATH" are as follows:
>
>
> $ which pdflatex
> /usr/local/bi
Hi, Peter et al.:
It looks like you've properly diagnosed my problem. How do I fix
it?
"which pdflatex" and "echo $PATH" are as follows:
$ which pdflatex
/usr/local/bin/pdflatex
$ echo $PATH
/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/sbgraves/anaconda3/bin:
13 matches
Mail list logo
