From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50187@debbugs.gnu.org, michael_heerdegen@web.de,
gregory@heytings.org, michael.albinus@gmx.de, larsi@gnus.org,
sds@gnu.org
Subject: bug#50187: 28.0.50; tramp is called from calendar
Date: Sun, 3 Sep 2023 01:36:56 -0700 [thread overview]
Message-ID: <CADwFkm=j69SmrriWv8eCKCbW-9EPW1EWrw9ErWkBy6mNv7cTgw@mail.gmail.com> (raw)
In-Reply-To: <83edwa34jt.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Sep 2022 09:20:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: Michael Heerdegen <michael_heerdegen@web.de>, 50187@debbugs.gnu.org,
>> Lars Ingebrigtsen <larsi@gnus.org>, Michael Albinus <michael.albinus@gmx.de>
>> From: Sam Steingold <sds@gnu.org>
>> Date: Fri, 16 Sep 2022 17:43:17 -0400
>>
>> It makes perfect sense for *occur* to inherit `default-directory', and
>> no sense for calendar.
>
> Then "M-x calendar" should take care of setting the default-directory
> of its buffer. It cannot be done by the infrastructure, because in
> many cases when a buffer is created, Emacs doesn't yet know its future
> purpose.
>
> But we are arguing about issues that might be purely academic.
> Michael asked you to collect some Tramp-related data, so he could look
> into what happens in this particular case. Please provide him the
> data he asked for: it could very well lead to a simple and
> uncontroversial solution.
We seem to need more information here to make any progress. Without
that information, I don't think it makes sense to keep this bug open.
Sam, could you please try to collect the information that Michael has
asked for? Thanks in advance.
next prev parent reply other threads:[~2023-09-03 8:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 15:06 bug#50187: 28.0.50; tramp is called from calendar Steingold
2022-08-22 14:28 ` Lars Ingebrigtsen
2022-08-22 16:18 ` Sam Steingold
2022-08-23 2:11 ` Michael Heerdegen
2022-08-23 2:18 ` Michael Heerdegen
2022-08-23 2:47 ` Sam Steingold
2022-08-23 3:24 ` Michael Heerdegen
2022-08-23 3:39 ` Sam Steingold
2022-08-23 4:00 ` Michael Heerdegen
2022-08-23 7:30 ` Michael Albinus
2022-08-23 10:00 ` Lars Ingebrigtsen
2022-08-23 19:13 ` Michael Heerdegen
2022-08-23 19:29 ` Lars Ingebrigtsen
2022-08-23 23:09 ` Michael Heerdegen
2022-09-12 18:49 ` Sam Steingold
2022-09-13 2:14 ` Michael Heerdegen
2022-09-13 14:29 ` Sam Steingold
2022-09-14 2:54 ` Michael Heerdegen
2022-09-14 18:57 ` Sam Steingold
2022-09-15 10:36 ` Michael Heerdegen
2022-09-15 16:10 ` Sam Steingold
2022-09-16 9:41 ` Lars Ingebrigtsen
2022-09-16 9:48 ` Michael Albinus
2022-09-16 10:04 ` Gregory Heytings
2022-09-16 14:31 ` Sam Steingold
2022-09-16 14:38 ` Michael Albinus
2022-09-16 15:02 ` Gregory Heytings
2022-09-16 16:56 ` Sam Steingold
2022-09-16 17:13 ` Sam Steingold
2022-09-16 17:30 ` Eli Zaretskii
2022-09-16 17:26 ` Gregory Heytings
2022-09-16 18:45 ` Sam Steingold
2022-09-16 18:51 ` Michael Albinus
2022-09-16 19:02 ` Eli Zaretskii
2022-09-16 19:30 ` Gregory Heytings
2022-09-16 21:43 ` Sam Steingold
2022-09-17 6:20 ` Eli Zaretskii
2023-09-03 8:36 ` Stefan Kangas [this message]
2024-01-10 11:02 ` Stefan Kangas
2022-09-17 6:48 ` Michael Albinus
2022-09-16 14:25 ` Sam Steingold
2022-09-16 14:31 ` Michael Albinus
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='CADwFkm=j69SmrriWv8eCKCbW-9EPW1EWrw9ErWkBy6mNv7cTgw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=50187@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
--cc=sds@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.