help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Duke Normandin" <dukeofpurl@gmx.com>
Cc: zsh-users@zsh.org
Subject: Re: Running emacs from fluxbox menu
Date: Wed, 21 Apr 2021 12:30:02 -0400	[thread overview]
Message-ID: <62a7d5a0-2b13-40ec-b6ab-2c34776a5405@www.fastmail.com> (raw)
In-Reply-To: <20210421071745.427a25f64cbc5dbccccd8f74@gmx.com>

On Wed, Apr 21, 2021, at 9:17 AM, Duke Normandin wrote:
> How/where do I "set the path correctly in the environment of emacs" ?

By ensuring that whatever process launches emacs provides it with
the PATH you want.  Your subject suggests that you're launching it
directly from fluxbox, so you'll want to figure out

- how to make fluxbox set a particular PATH when it launches emacs, or
- how to set PATH in the environment of fluxbox itself, so that it
  gets passed on to emacs.

Neither of these things really has anything to do with zsh.  There's
a fluxbox-users mailing list that you might try.


> I copied & pasted the PATH statement in my .zshrc into ~/.zshenv.
> Problem solved!!! Thanks!
> Does this mean that my existing PATH statement is built correctly, or 
> could it still be messed up?

I think setting or modifying PATH in .zshenv is really bad form and
should be avoided unless absolutely necessary.  I encourage you to
figure out how to properly configure the environment for emacs


  reply	other threads:[~2021-04-21 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  4:00 Duke
2021-04-21  4:10 ` Bart Schaefer
2021-04-21  4:21   ` Duke Normandin
2021-04-21  4:51     ` Lawrence Velázquez
2021-04-21  4:57       ` Duke Normandin
2021-04-21  5:14         ` Lawrence Velázquez
2021-04-21  6:10         ` Bart Schaefer
2021-04-21 13:17           ` Duke Normandin
2021-04-21 16:30             ` Lawrence Velázquez [this message]
2021-04-21 17:07               ` Duke Normandin
  -- strict thread matches above, loose matches on Subject: below --
2021-04-19  4:57 jdh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62a7d5a0-2b13-40ec-b6ab-2c34776a5405@www.fastmail.com \
    --to=larryv@zsh.org \
    --cc=dukeofpurl@gmx.com \
    --cc=zsh-users@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).