unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Patrick Mahan <plmahan@gmail.com>
To: Rudolf Schlatte <rudi@constantly.at>
Cc: help-gnu-emacs@gnu.org
Subject: Re: PWD is not seen by my emacs installation
Date: Wed, 9 Aug 2023 13:21:36 -0700	[thread overview]
Message-ID: <CAFDHx1L4TVAW6YVtUU9qb3=oRJQM_vOQigxakUeM2NmEs+UoNg@mail.gmail.com> (raw)
In-Reply-To: <m15y5opyhe.fsf@constantly.at>

On Tue, Aug 8, 2023 at 10:38 PM Rudolf Schlatte <rudi@constantly.at> wrote:

> Patrick Mahan <plmahan@gmail.com> writes:
> >> 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.
>
> In that case, you can write "open -a Emacs.app /path/to/somefile.txt"
> and it will be opened by Emacs as expected.
>
> Note that in Emacs, each buffer has its own "current directory", so
> e.g. starting dired when in the "somefile.txt" buffer will display the
> contents of "/path/to".
>
>
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.

Thanks,

Patrick


  reply	other threads:[~2023-08-09 20:21 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 [this message]
2023-08-22  1:14         ` David Masterson
2023-08-22  4:24           ` Patrick Mahan
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='CAFDHx1L4TVAW6YVtUU9qb3=oRJQM_vOQigxakUeM2NmEs+UoNg@mail.gmail.com' \
    --to=plmahan@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).