From: Naofumi Yasufuku <naofumi@yasufuku.dev>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 59813@debbugs.gnu.org
Subject: bug#59813: 29.0.60; function-history: M-. fails to jump to defun if straight.el straight-cache-autoloads is enabled
Date: Thu, 15 Dec 2022 02:23:28 +0900 [thread overview]
Message-ID: <86edt1292n.fsf@yasufuku.dev> (raw)
In-Reply-To: <CADwFkmk-UzARCHopQj1YB+OD9Gy_8M4wpR2MX4zcrRgKN2xddQ@mail.gmail.com>
Hi Stefan,
Stefan Kangas <stefankangas@gmail.com> writes:
>
> I can reproduce this on master, but not every time. Sometimes it works
> even after one `eval-buffer'. For some reason, it seems to work more
> often when I remove the third line with `message'?
>
On my systems (debian bullseye box and x86 macOS laptop), M-. failure
happens every time. If the third (message .. (loadhist--foo-inc 1)) is
not exist, M-. on `loadhist--foo-inc' works:
#+begin_src emacs-lisp
(setq load-path (cons (locate-user-emacs-file "site-lisp") load-path))
(autoload 'loadhist--foo-inc "loadhist--foo")
;; (message "(loadhist--foo-inc 1): %s" (loadhist--foo-inc 1))
#+end_src
If the third (message .. (loadhist--foo-inc 1)) is replaced with
`require', M-. on `loadhist--foo-inc' also fails:
#+begin_src emacs-lisp
(setq load-path (cons (locate-user-emacs-file "site-lisp") load-path))
(autoload 'loadhist--foo-inc "loadhist--foo")
(require 'loadhist--foo)
#+end_src
It is that I actually noticed this issue for the first time.
Best regards,
Naofumi
next prev parent reply other threads:[~2022-12-14 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 9:44 bug#59813: 29.0.60; function-history: M-. fails to jump to defun if straight.el straight-cache-autoloads is enabled Naofumi Yasufuku
2022-12-13 1:20 ` Stefan Kangas
2022-12-13 20:20 ` Naofumi Yasufuku
2022-12-13 21:30 ` Stefan Kangas
2022-12-14 17:23 ` Naofumi Yasufuku [this message]
2022-12-14 3:26 ` Eli Zaretskii
2022-12-14 17:24 ` Naofumi Yasufuku
2022-12-14 17:34 ` Naofumi Yasufuku
2022-12-14 17:48 ` Naofumi Yasufuku
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=86edt1292n.fsf@yasufuku.dev \
--to=naofumi@yasufuku.dev \
--cc=59813@debbugs.gnu.org \
--cc=stefankangas@gmail.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.