From: William G. Gardella <wgg2@member.fsf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Line number where eval-after-load is defined in my .emacs file
Date: Wed, 13 Nov 2013 17:05:04 +0000 [thread overview]
Message-ID: <87iovwgrlr.fsf@motoko.kusanagi> (raw)
In-Reply-To: 86mwl88d9a.fsf@somewhere.org
Hi Seb,
"Sebastien Vauban" <sva-news@mygooglest.com>
writes:
[...]
> Is there a way to "link" the messages to the `eval-after-load' blocks in my
> .emacs file by showing the line number where those blocks are defined?
>
> Or is there some other way to get such more or less the same type of
> information?
>
> Best regards,
> Seb
This seems analogous to the management problem that one can have after
putting a lot of lambdas which all look alike inside a hook variable.
Maybe a similar solution is warranted. I would rewrite your
`eval-after-load' blocks such that each of them calls one named function
(instead of an anonymous `progn'), which in turn contains all the stuff
to be done inside that `eval-after-load'. That way, when something goes
wrong, the backtrace will name the offending function.
Best,
WGG
next prev parent reply other threads:[~2013-11-13 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 16:42 Line number where eval-after-load is defined in my .emacs file Sebastien Vauban
2013-11-13 17:05 ` William G. Gardella [this message]
[not found] ` <mailman.5986.1384362332.10748.help-gnu-emacs@gnu.org>
2013-11-13 20:12 ` Sebastien Vauban
2013-11-14 8:19 ` Thien-Thi Nguyen
[not found] ` <mailman.6043.1384418405.10748.help-gnu-emacs@gnu.org>
2013-11-15 13:43 ` Sebastien Vauban
2013-11-16 1:40 ` Michael Heerdegen
2013-11-13 21:03 ` Sebastien Vauban
2013-11-13 22:09 ` Stefan Monnier
2013-11-13 23:26 ` Michael Heerdegen
[not found] ` <mailman.6018.1384385233.10748.help-gnu-emacs@gnu.org>
2013-11-15 13:46 ` Sebastien Vauban
2013-11-22 16:47 ` jack-mac
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=87iovwgrlr.fsf@motoko.kusanagi \
--to=wgg2@member.fsf.org \
--cc=help-gnu-emacs@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.
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).