Re: PWD is not seen by my emacs installation

[Patrick Mahan]

On Tue, Aug 8, 2023 at 12:27 PM <stefan-husmann@t-online.de> wrote:

>
> Patrick Mahan <plmahan@gmail.com> writes:
>
> > Hardware -
> >
> >    Macbook Pro 14" (Apple M1 Pro)
> >    Mac OS 13.1 (Ventura)
> >
> > Emacs -
> >
> >    Emacs 28.2 (build 1, aarch64-apple-darwin21.1.0, NS appkit-2113.00
> > Version 12.0.1 (Build 21A559)) of 2022-09-12)
> >
> > My emacs does not see the current directory, but instead is expecting
> > everything to be under ~/.  I thought emacs grokked the PWD environment
> > variable.
> >
> > From my shell -
> >
> >     % echo $PWD
> >     /Users/mahan/src/PPP/ppp-master/pppd
> >
> > But inside my .emacs I have -
> >
> > (setq workingdir (getenv "PWD"))
> > message "PWD = '%s'" workingdir)
>
> There is  missing a ( at beginning of line? You should get an
> "unbalanced parantheses" message.
>
>
No, there is not, that was a cut-n-paste error.


> >
> > Which results in -
> >
> > PWD = ’nil’
> >
> > Unless I open using a Full pathname, it will not open the file
> > correctly.
>
> What file?
>

If I am in /Users/mahan/src/PPP/ppp-master/pppd and attempt to open
sys-linux.c, it opens an emacs window, but nothing is present.  If I look
at the buffers window -

.%* *Messages*              695 Messages
    sys-linux.c               0 C/*l             ~/sys-linux.c
    *scratch*               144 Lisp Interaction

It shows up as being in my home directory.


> >
> > Suggestions?
> >
> > Thanks,
> >
> > Patrick
>
>
> How did you invoke emacs? If you start it from some graphical MacOS
> environment, may PWD _is_ undefined (I know nothing about MacOS)? Did you
> cd into
> /Users/mahan/src/PPP/ppp-master/pppd in a shell and start emacs from
> the command line from there?
>
>
Thanks!  That was a good suggestion.  I was using the Mac OS X 'open'
command which is probably, as you suggested, not picking up the correct
environment, though oddly it is picking up the PATH correctly.

This was something I took from another user on a mailing list.

Dropping the 'open' and invoking Emacs directly fixes that issue!

Patrick