Hi folks. Just wanted to solicit an opinion here, if anyone wants to give one.

The following question was posted to TeX SE some days ago.

But has unsurprisingly received no replies. Not even a comment.

I was wondering how best to proceed. Would it be better to (a) offer a bounty (b) ask for it to be migrated to SO?

I suppose I could offer a bounty on SO as well.

I've been using this code for a bit. It mostly works well. It's just this one case that is a bit annoying. I don't know why it is hanging, which is also annoying. I.e. the hanging is annoying. That I don't know why it's hanging is also annoying.

Hello. A quick question. Which files does zsh execute when I start off the terminal (on a Mac)? I suppose it executes .zshrc, but does it execute any other one? I am asking this because I am getting a parse error when I open the terminal (eval):18: parse error near Fusion.app/Contents/...'. I tried to look into .zshrc, but line 18 is [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm` for me

but that doesn't seem to be related to Fusion.app, which I think is related to VMware Fusion, which I have installed

The line 18 of my .bash_profile is unset __conda_setup and my .bashrc is empty. So, there must be another file that is called directly or indirectly when I open the terminal

@nbro See the "STARTUP/SHUTDOWN FILES" section of man zsh, there's quite a list

The (eval) means it's line 18 of an evaled string rather than of the host file, though. You may be able to unset the EVAL_LINENO option to get a physical line and filename instead

@MichaelHomer thanks! I read that section, I tried to open the files mentioned there, but I see no trace of something related to Fusion.app

@MichaelHomer how would you unset that?

zsh -o noevallineno

Might as well add -x while you're there. I don't know where "there" is though

by "there" I mean in the files listed under that section, like .zshenv

@MichaelHomer what would be the consequences of this? can then I go back to the previous state?

It will print out every command before it runs

You can go back to the same place and take it out. Ideally in Terminal preferences, in an early startup file (set -x o ...) otherwise