all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: 24999@debbugs.gnu.org
Subject: bug#24999: closed (Re: bug#24999: 24.5; bad doc for invocation-directory)
Date: Thu, 24 Nov 2016 19:53:41 +0200	[thread overview]
Message-ID: <837f7s69y2.fsf@gnu.org> (raw)
In-Reply-To: <E1c9y5K-0002gt-Hl@tucano.isti.cnr.it> (message from Francesco Potortì on Thu, 24 Nov 2016 18:45:22 +0100)

> Date: Thu, 24 Nov 2016 18:45:22 +0100
> From: Francesco Potortì <pot@gnu.org>
> 
> I had written:
> 
> >The only way I found for obtaining the directory from which
> >Emacs was invoked is to get the default-directory of the *scratch*
> >buffer.
> 
> Can this be considered as a bug?  Or at least a wishlist?  Having a
> variable that contains the invocation directory?

IMO it's not meaningful in Emacs to ask which directory was the
"current" when Emacs started.  That's because Emacs pretends the
current directory is different for every buffer.





  reply	other threads:[~2016-11-24 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 10:23 bug#24999: 24.5; bad doc for invocation-directory Francesco Potortì
2016-11-24 17:23 ` Eli Zaretskii
     [not found] ` <handler.24999.D24999.148000823832450.notifdone@debbugs.gnu.org>
2016-11-24 17:45   ` bug#24999: closed (Re: bug#24999: 24.5; bad doc for invocation-directory) Francesco Potortì
2016-11-24 17:53     ` Eli Zaretskii [this message]
2016-11-24 18:02       ` Eli Zaretskii
2016-11-24 18:08         ` Francesco Potortì
2016-11-24 18:19           ` Eli Zaretskii
2016-11-25  8:44       ` Francesco Potortì
2016-11-25 13:27         ` Eli Zaretskii
2016-11-26  1:07           ` Richard Stallman
2016-11-26  7:20             ` Eli Zaretskii
2016-11-26  1:07         ` Richard Stallman

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

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

  git send-email \
    --in-reply-to=837f7s69y2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24999@debbugs.gnu.org \
    --cc=pot@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.