all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 62974@debbugs.gnu.org
Subject: bug#62974: 29.0.60; New buffers created with project-switch-to-buffer aren't in the project
Date: Thu, 20 Apr 2023 21:55:57 +0300	[thread overview]
Message-ID: <83ttxa4c3m.fsf@gnu.org> (raw)
In-Reply-To: <iercz3yz9g9.fsf@janestreet.com> (message from Spencer Baugh on Thu, 20 Apr 2023 14:37:26 -0400)

> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Thu, 20 Apr 2023 14:37:26 -0400
> 
> 
> 1. emacs -Q (in a directory not in a project)
> 2. Note current default-directory: some/dir
> 3. C-x p b (so that it will prompt for a project)
> 4. Select some project and RET
> 5. Enter a nonexisting buffer name and RET
> 6. The new buffer's default-directory is some/dir
> 
> Expected behavior:
> 6. The new buffer's default-directory is the project root of the project
> you picked.

??Really?  project.el changes the way Emacs creates new buffers?  Is
there a reason for such a deviation (if indeed there is a deviation)?
Because otherwise my expectation would exactly what you see, because
"C-x b" behaves like that.





  reply	other threads:[~2023-04-20 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 18:37 bug#62974: 29.0.60; New buffers created with project-switch-to-buffer aren't in the project Spencer Baugh
2023-04-20 18:55 ` Eli Zaretskii [this message]
2023-04-20 23:55   ` Dmitry Gutov
2023-04-21  5:43     ` Eli Zaretskii
2023-04-21 11:46       ` Spencer Baugh
2023-04-21 12:00         ` Eli Zaretskii
2023-04-21 13:17           ` sbaugh
2023-04-21 15:56             ` Dmitry Gutov
2023-04-21 16:25               ` Spencer Baugh
2023-04-21 23:31                 ` Dmitry Gutov

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=83ttxa4c3m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62974@debbugs.gnu.org \
    --cc=sbaugh@janestreet.com \
    /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.