From: Sam Steingold <sds@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Michael Albinus <michael.albinus@gmx.de>,
Lars Ingebrigtsen <larsi@gnus.org>,
50187@debbugs.gnu.org
Subject: bug#50187: 28.0.50; tramp is called from calendar
Date: Wed, 14 Sep 2022 14:57:08 -0400 [thread overview]
Message-ID: <lzv8pp3htn.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <87bkrifyxf.fsf@web.de> (Michael Heerdegen's message of "Wed, 14 Sep 2022 04:54:36 +0200")
> * Michael Heerdegen <zvpunry_urreqrtra@jro.qr> [2022-09-14 04:54:36 +0200]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>> I always run Emacs with `debug-on-error' set to t.
>> So `midnight-hook' runs `calendar', it errors out, and I see the
>> *Backtrace* first thing in the morning.
>
> I didn't know that you got an error.
Sorry, the original message was indeed unclear on that.
> And you can still reproduce the problem?
Alas, I have not seen this for quite some time.
I don't even recall _when_ the problem went away.
All I remember is that I saw it for a while, reported the bug, did
nothing specifically to correct the issue, and then it went away after
some time.
> Then you could try to use the calendar before midnight and see if that
> prevents that error at midnight. If it doesn't, my autoload theory
> would be wrong.
I do use calendar regularly, but I have not seen this recently.
_However_, I just called calendar from a Tramp buffer and the *Calendar*
buffer's `default-directory' is a tramp directory.
I don't think this is right.
--
Sam Steingold (https://aphar.dreamwidth.org/) on darwin Ns 10.3.2113
https://lastingimpactpsychology.com https://steingoldpsychology.com
https://iris.org.il https://honestreporting.com https://jihadwatch.org
A good programmer: language change is easy, editor change is ... huh?!
next prev parent reply other threads:[~2022-09-14 18:57 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 [this message]
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
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=lzv8pp3htn.fsf@3c22fb11fdab.ant.amazon.com \
--to=sds@gnu.org \
--cc=50187@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
/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.