From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: dmitry@gutov.dev, 62974@debbugs.gnu.org
Subject: bug#62974: 29.0.60; New buffers created with project-switch-to-buffer aren't in the project
Date: Fri, 21 Apr 2023 15:00:07 +0300 [thread overview]
Message-ID: <83a5z14f94.fsf@gnu.org> (raw)
In-Reply-To: <CAO=BR8NdfdQ1jgBi+vHuLLnY3+xU4Ema5LrpCSVfgCEX0fhUpw@mail.gmail.com> (message from Spencer Baugh on Fri, 21 Apr 2023 07:46:14 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Fri, 21 Apr 2023 07:46:14 -0400
> Cc: Dmitry Gutov <dmitry@gutov.dev>, 62974@debbugs.gnu.org
>
> But if it is in a subdirectory of the root, it also belongs to the
> project, doesn't it? Exactly like the buffer from which this command
> is invoked, whose default-directory was a subdirectory of the root.
> No?
>
> That's fine, I wouldn't want to change that behavior, the behavior I'd want to change is when invoking
> the command from a buffer which is not in a project, or by invoking it after C-x p p to switch projects.
The recipe you posted didn't include "C-x p p", though.
next prev parent reply other threads:[~2023-04-21 12:00 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
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 [this message]
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=83a5z14f94.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62974@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--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.