From: Patrick Mahan <plmahan@gmail.com>
To: David Masterson <dsmasterson@gmail.com>
Cc: Rudolf Schlatte <rudi@constantly.at>, help-gnu-emacs@gnu.org
Subject: Re: PWD is not seen by my emacs installation
Date: Mon, 21 Aug 2023 21:24:12 -0700 [thread overview]
Message-ID: <CAFDHx1KFC1gMNyiirN7bZq0CwO+gQ1ReNUDkNST3S1Gg4Mc7SA@mail.gmail.com> (raw)
In-Reply-To: <LV8P223MB0920E2D4D7A9453C4DBD0F45A21FA@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM>
Thanks, I'll check it out.
On Mon, Aug 21, 2023 at 6:14 PM David Masterson <dsmasterson@gmail.com>
wrote:
> Patrick Mahan <plmahan@gmail.com> writes:
>
> > Yes, that is what occurs, but my issue is the need to give the full path
> > (or even a relative path off of '~'). I just want to edit the file in
> the
> > local directory. I do not want to have to say "open -a Emacs.app
> > $PWD/file.txt" just to open a local file.
> >
> > I also tried using the --env option to the open command but it does not
> > seem to work.
> >
> > Invoking it directly works correctly.
>
> This sounds like the same problem of starting Emacs from an icon in many
> window managers. The standard icons often don't load your "profile",
> but rather uses a default "slimmed down" profile. Try this:
>
> 1. Start Emacs from the icon
> 2. Check your environment by either of these ways:
> 2a, 'M-x shell' and then 'env'
> 2b. 'C-h v process-environment'
> 3. Compare that environment with your "directly" environment
> 4. If $HOME is correct in #2 & #3, you can fix other key environment
> variables using early-init.el (see 'Init File' in the Emacs infodocs).
> 5. Use 'setenv' in early-init.el to adjust your environment as needed.
>
> --
> David Masterson
>
next prev parent reply other threads:[~2023-08-22 4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 1:58 PWD is not seen by my emacs installation Patrick Mahan
2023-08-08 12:44 ` tpeplt
[not found] ` <CAFDHx1Jk=jtHhLdThFUeFpfa=yGTXoKYuu0bADYAN-j-7FjSHw@mail.gmail.com>
2023-08-09 0:59 ` tpeplt
2023-08-08 19:07 ` stefan-husmann
2023-08-08 21:21 ` Patrick Mahan
2023-08-09 5:37 ` Rudolf Schlatte
2023-08-09 20:21 ` Patrick Mahan
2023-08-22 1:14 ` David Masterson
2023-08-22 4:24 ` Patrick Mahan [this message]
2023-08-30 22:29 ` Rudolf Adamkovič
2023-08-30 23:43 ` Patrick Mahan
2023-09-03 15:27 ` Rudolf Schlatte
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFDHx1KFC1gMNyiirN7bZq0CwO+gQ1ReNUDkNST3S1Gg4Mc7SA@mail.gmail.com \
--to=plmahan@gmail.com \
--cc=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rudi@constantly.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).