all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Steingold <sds@gnu.org>, 50187@debbugs.gnu.org
Subject: bug#50187: 28.0.50; tramp is called from calendar
Date: Tue, 23 Aug 2022 12:00:01 +0200	[thread overview]
Message-ID: <87zgfvth3y.fsf@gnus.org> (raw)
In-Reply-To: <87wnazfmdj.fsf@gmx.de> (Michael Albinus's message of "Tue, 23 Aug 2022 09:30:00 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> I don't believe it is a load-path issue. calendar-cursor-to-visible-date
> is declared in cal-loaddefs.el (it has the ;;;###cal-autoload cookie),
> and this loaddefs file is loaded when loading calendar.el.
>
> That has been finished already, when calendar-basic-setup is applied.

Yes, cal-loaddefs had been loaded.  

> The question is rather: what is cal-move.so, and how and why is it
> checked for readability? In the directory emacs/lisp/calendar I cannot
> find any use of this file.

The backtrace shows that Emacs was trying to load cal-move.so, and
that's presumably something that Emacs tries to do when resolving the
`autoload' definition of `calendar-cursor-to-visible-date', I think?
(If I remember correctly, Emacs looks for all of so/elc/el, if Emacs is
built with module support, when doing a `require'/`autoload' lookup.)






  reply	other threads:[~2022-08-23 10:00 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 [this message]
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
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=87zgfvth3y.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50187@debbugs.gnu.org \
    --cc=michael.albinus@gmx.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.