On third thought, it's pretty tricky to locally change the value of `TeX-command-extra-options' once it's set. The only simple way I found is to manually edit the auto saved file and then revert the *TeX buffer, not the best option indeed.
Three years ago I tried to implement support for jobnames different from default one, but jobname was to be set locally in master file and shared among other files of the same project. I gave up (also) because I didn't find a simple way to share the value of a variable that was set locally. Bye, Mosè 2016-04-14 0:49 GMT+02:00 Mosè Giordano <[email protected]>: > On second thought, isn't it better to store the variable only if it's > local bound (local-variable-p 'TeX-command-extra-options > (current-buffer)) rather than testing if it's the empty string? If > one has that variable set to a non-empty string globally but an empty > string locally, that would result in an unexpected result. > > Bye, > Mosè > > 2016-04-13 21:06 GMT+02:00 Mosè Giordano <[email protected]>: >> Hi Matt, >> >> 2016-04-13 20:09 GMT+02:00 Matthew Leach <[email protected]>: >>> Hi all, >>> >>> Please see the attached patch that saves the value of >>> `TeX-command-extra-options' to the auto-save file so it gets set >>> project-wide. >> >> Looks good, go ahead. >> >> Thanks, >> Mosè _______________________________________________ auctex-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex-devel
