Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Colin Baxter <m43cap@yandex.com>
Cc: ding@gnus.org
Subject: Re: gnus-extra-headers
Date: Mon, 06 Sep 2021 10:39:13 -0700	[thread overview]
Message-ID: <87bl55ioxq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87y2894qi7.fsf@yandex.com> (Colin Baxter's message of "Mon, 06 Sep 2021 17:29:04 +0100")

Colin Baxter <m43cap@yandex.com> writes:

>>>>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>

[...]

>     > No, none of that is expected, and it's not what I see here. Doing
>     > C-h v gnus-extra-headers does load a bunch of Gnus files, but not
>     > nndiary, and the value of the option doesn't change.
>
>     > And the fact that putting a call to (error) (actually, it should
>     > have been called with a string argument, but the effect is the
>     > same) in nndiary.el doesn't actually raise an error and give you a
>     > traceback means that you're not loading that file at all. Are
>     > there are multiple Emacs installations on your machine?
>
> Yes, all installed locally under $HOME:
>
> 1. ~/local/bin/emacs-27.1 (GTK)
> 2. ~/local/bin/emacs-27.2 (GTK)
> 3. ~/local/opt/emacs-lucid/bin/emacs-27.1 (lucid)
> 4. ~/local/opt/emacs-lucid/bin/emacs-27.2 (lucid)
> 5. ~/git/emacs/src/emacs (GTK)

Okay, so try:

1. emacs -Q
2. M-: (locate-library "nndiary")
3. Wherever that file is, delete the nndiary.elc file next to it
4. Visit the nndiary.el file itself.
5. At the top of the file, insert the line (error "Don't load me")
6. Save the file, exit emacs.
7. emacs -Q
8. C-h v gnus-extra-headers
9. Post resulting traceback



  reply	other threads:[~2021-09-06 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  8:15 gnus-extra-headers Colin Baxter
2021-09-02 22:12 ` gnus-extra-headers Eric Abrahamsen
2021-09-03  5:42   ` gnus-extra-headers Colin Baxter
2021-09-03 18:30     ` gnus-extra-headers Eric Abrahamsen
2021-09-04 14:39       ` gnus-extra-headers Colin Baxter
2021-09-04 15:15         ` gnus-extra-headers Eric Abrahamsen
2021-09-05  8:36           ` gnus-extra-headers Colin Baxter
2021-09-06  3:31             ` gnus-extra-headers Eric Abrahamsen
2021-09-06  7:14               ` gnus-extra-headers Colin Baxter
2021-09-06  8:37                 ` gnus-extra-headers Colin Baxter
2021-09-06 16:15                   ` gnus-extra-headers Eric Abrahamsen
2021-09-06 16:29                     ` gnus-extra-headers Colin Baxter
2021-09-06 17:39                       ` Eric Abrahamsen [this message]
2021-09-06 19:33                         ` gnus-extra-headers Colin Baxter
2021-09-06 17:16                     ` gnus-extra-headers Stephen Berman
2021-09-06 18:40                       ` gnus-extra-headers Eric Abrahamsen
2021-09-07  5:53                         ` gnus-extra-headers Colin Baxter
2021-09-07 18:56                           ` gnus-extra-headers Eric Abrahamsen

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=87bl55ioxq.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=m43cap@yandex.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.
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).