Re: environment variables?
Tom Sgouros writes: > I'm using a Mac (MacOs 13.2), and if anyone is familiar with the best > way to set environment variables for an Emacs started from the Finder > where there is no environment to inherit I'd love to hear about that, > too. /etc/rc.common does not appear to work for this. I've read a couple of times that the lisp library exec-path-from-shell.el is made for this[1]. I've never used it, though. I always start Emacs from the CLI. Best, Arash Footnotes: [1] https://github.com/purcell/exec-path-from-shell
Re: environment variables?
Hi Tom, > Tom Sgouros writes: > How can I set an environment variable necessary for my TeX installation to > find my local class files? Is there a way within Auctex to do this? > I'm using a Mac (MacOs 13.2), and if anyone is familiar with the best way > to set environment variables for an Emacs started from the Finder where > there is no environment to inherit I'd love to hear about that, too. > /etc/rc.common does not appear to work for this. You can use elisp function `setenv'. Put something like this in your init file (e.g. ~/.emacs.d/init.el): (setenv "TEXINPUTS" "/abc/def/xyz//:") Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
Re: environment variables?
Hi Tom,
Why not just embed these settings in a .bashrc file (or equivalent)?
### Settings that are defaults--can be updated below
# Set up the TeX environmentals
TEXINPUTS=.:${HOME}/tex/latex:
export TEXINPUTS
BIBINPUTS=.:${HOME}/litbase/bibtex:
export BIBINPUTS
BSTINPUTS=.:${HOME}/tex/bibtex:
export BSTINPUTS
Best,
Rob
> On Oct 23, 2023, at 6:26 AM, Tom Sgouros wrote:
>
> Thank you Arash and Ikumi. That gives me something to go on.
>
> -Tom
>
> On Mon, Oct 23, 2023 at 4:42 AM Arash Esbati > wrote:
>> Tom Sgouros mailto:tsgou...@gmail.com>> writes:
>>
>> > I'm using a Mac (MacOs 13.2), and if anyone is familiar with the best
>> > way to set environment variables for an Emacs started from the Finder
>> > where there is no environment to inherit I'd love to hear about that,
>> > too. /etc/rc.common does not appear to work for this.
>>
>> I've read a couple of times that the lisp library
>> exec-path-from-shell.el is made for this[1]. I've never used it,
>> though. I always start Emacs from the CLI.
>>
>> Best, Arash
>>
>> Footnotes:
>> [1] https://github.com/purcell/exec-path-from-shell
smime.p7s
Description: S/MIME cryptographic signature
Re: environment variables?
Thank you Arash and Ikumi. That gives me something to go on. -Tom On Mon, Oct 23, 2023 at 4:42 AM Arash Esbati wrote: > Tom Sgouros writes: > > > I'm using a Mac (MacOs 13.2), and if anyone is familiar with the best > > way to set environment variables for an Emacs started from the Finder > > where there is no environment to inherit I'd love to hear about that, > > too. /etc/rc.common does not appear to work for this. > > I've read a couple of times that the lisp library > exec-path-from-shell.el is made for this[1]. I've never used it, > though. I always start Emacs from the CLI. > > Best, Arash > > Footnotes: > [1] https://github.com/purcell/exec-path-from-shell >
Re: environment variables?
Am 23.10.23 um 10:42 Uhr schrieb Arash Esbati: > I've read a couple of times that the lisp library > exec-path-from-shell.el is made for this[1]. This is right. I use it with the current Vanilla Emacs, and it works. I ran into trouble when I noticed that GNU Emacs on the Mac does not inherit environment variables when you start it from Finder. Both the locale for aspell and the env LuaTeX needs were missing. You may use setenv, but the preferred way on the Mac is to use exec-path-from-shell. Regards, Jürgen.
master ecc00591: ; * admin/release-process.org: Fix typos
branch: master commit ecc00591208abb16f19e6316fced2797f39d42ea Author: Ikumi Keita Commit: Ikumi Keita ; * admin/release-process.org: Fix typos --- admin/release-process.org | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/admin/release-process.org b/admin/release-process.org index a0da4130..3348cf07 100644 --- a/admin/release-process.org +++ b/admin/release-process.org @@ -40,7 +40,7 @@ everything goes well, before actually doing the release. - The instructions may mention how to build the XEmacs and Windows packages, but you do not need to do that if you decided to stop providing those -packages +packages. - Make sure that the patch for =gendocs.sh= in the =www-docs= target applies correctly, otherwise you will need to update it. Remember to update it in the =gendocspath= branch of the AUCTeX remote repository too. @@ -81,7 +81,7 @@ You can also browse the [[http://web.cvs.savannah.gnu.org/viewvc/auctex/][conten - [ ] Update AUCTeX version and date in files in =src/= directory. When you are done, run the script =./genpages.sh= - [ ] Update the =ChangeLog= -- [ ] Register all changes. You can use for example =vc-mode= in Emacs: [0/2] +- [ ] Register all changes. You can use for example =vc-mode= in Emacs: [0/3] - [ ] Register all new files with =i= - [ ] Select all files in the same state with =m= and do check in/out with =v= @@ -172,7 +172,7 @@ AUCTeX is kept in the ~externals/auctex~ branch of the ELPA repository. 3. Merge the commits which have taken place in the normal auctex development on the ~master~ branch using ~git merge origin/master~. 4. In case of conflicts, edit, and commit. -5. Check that everything compiles by running ~make -f GNUMakefile~. +5. Check that everything compiles by running ~make -f GNUmakefile~. 6. Push your changes to the elpa remote (~git push~). Just updating the ~externals/auctex~ branch by merging in the changes from the @@ -181,7 +181,7 @@ Emacs' package manager. To do an actual release which will be published, you have to do the following steps in addition. 7. Edit the line ~;; Version: X.Y.Z~ in the file ~auctex.el~. For ELPA - releases, Y and Y match the latest AUCTeX version and Z is incremented for + releases, X and Y match the latest AUCTeX version and Z is incremented for every ELPA release of that AUCTeX version. Z starts with 0, so AUCTeX 12.2.0 should be (almost) identical to the AUCTeX release 12.2. 8. Commit that change with this Git commit message (but do not push yet!). The @@ -194,7 +194,7 @@ Release GNU AUCTeX X.Y.Z * GNU AUCTeX Version X.Y.Z released. #+END_EXAMPLE -9. Run ~make -f GNUMakefile~ again. In the output you should see that the +9. Run ~make -f GNUmakefile~ again. In the output you should see that the above version is inserted into several files, e.g., the info documentation. The version change is gotten from the current HEAD of the branch. That's the reason the commit message has to be in exactly this format.
