From: "Tobias C. Rittweiler" <tcr@freebits.de>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: GNU Emacs 23.0.90.4 (2009-02-21) -- backtraces on startup
Date: Mon, 23 Feb 2009 13:06:30 +0100 [thread overview]
Message-ID: <87wsbhe4s9.fsf@freebits.de> (raw)
In-Reply-To: <b4m63j1ec8w.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 23 Feb 2009 18:25:19 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> For example:
> https://bugs.launchpad.net/ubuntu/+source/emacs-snapshot/+bug/293711
I was bitten by a wrong symlink. While (find-library "gnus") brought me
to the gnus.el of my build, C-h f gnus revealed that (gnus) actually
invoked a function from the gnus.el of an older build.
False Alarm, I'm sorry.
Thanks Katsumi!
-T.
--
Diese Nachricht wurde auf Viren und andere gefaerliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
Freebits E-Mail Virus Scanner
prev parent reply other threads:[~2009-02-23 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873ae7mnwz.fsf@freebits.de>
2009-02-23 9:25 ` Katsumi Yamaoka
2009-02-23 12:06 ` Tobias C. Rittweiler [this message]
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=87wsbhe4s9.fsf@freebits.de \
--to=tcr@freebits.de \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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 NNTP newsgroup(s).