From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [PATCH] Extra information in autoload error
Date: Mon, 24 Oct 2016 13:21:08 -0600 [thread overview]
Message-ID: <87mvht4kpn.fsf@gmail.com> (raw)
In-Reply-To: <83lgxe5ke6.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Oct 2016 09:30:25 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex <agrambot@gmail.com>
>> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
>> Date: Sun, 23 Oct 2016 15:24:01 -0600
>>
>> I was wondering if you preferred the version that used
>>
>> SDATA (Fcar (Fcar (Vload_history)))
>>
>> or
>>
>> SDATA (Fcar (Fcdr (fundef)))
>>
>> to get the extra information. The first one gets the file path, while
>> the second one just gets what was in the autoload object.
>
> Don't we want both?
That would display more information, but it would also make the error
message more verbose.
> Can you show the textual description of the
> "autoload object" that is returned by the latter form?
Here, fundef is the autoload object. That is, it's a list of the form:
(autoload filename docstring interactive type)
So SDATA (Fcar (Fcdr (fundef))) just gets the filename of the autoload
object. The filename of the autoload object is just the 2nd argument of
the `autoload' function.
So the Vload_history version returns the whole path, while the fundef
version just uses whatever was passed into autoload. Usually that is
just the filename sans extension, e.g.:
(symbol-function 'linum-mode) => (autoload "linum" 1174895 t nil)
> (Sorry, too busy with more urgent issues to try that myself.)
No worries.
next prev parent reply other threads:[~2016-10-24 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 20:53 [PATCH] Extra information in autoload error Alex
2016-09-21 21:13 ` Davis Herring
2016-09-21 22:16 ` Alex
2016-10-22 16:23 ` Alex
2016-10-22 16:30 ` Eli Zaretskii
2016-10-22 19:40 ` Stefan Monnier
2016-10-22 20:23 ` Alex
2016-10-23 5:53 ` Eli Zaretskii
2016-10-23 21:24 ` Alex
2016-10-24 6:30 ` Eli Zaretskii
2016-10-24 19:21 ` Alex [this message]
2016-10-24 19:56 ` Eli Zaretskii
2016-10-25 5:47 ` Alex
2016-11-04 8:43 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvht4kpn.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).