Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: wrong unread count after INBOX change
Date: Wed, 06 Jan 2016 19:20:11 +0800	[thread overview]
Message-ID: <878u43vtsk.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k2nn3ts9.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> david.goldberg6@verizon.net (Dave Goldberg) writes:
>>
>>>>
>>>> But even running (require 'gnus-util) doesn't cause this to be loaded, I
>>>> have to go and C-x C-e on it. Which I find very weird!
>>>
>>> Most likely that's because a different gnus-util is already loaded.
>>> Perhaps you've got a load-path shadow assuming you run gnus from git
>>> in a directory different from the gnus provided with your emacs
>>> distribution.
>>>
>>> At one point probably two or three years ago (you can find my ranting
>>> about it on this list's archives if you care ;-)) Fedora's emacs
>>> distribution included a site-start configuration that caused gnus-util
>>> to be loaded at start up. Perhaps that's what's happening in your
>>> case? If you do an "emacs -q" does (featurep 'gnus-util) return t? If
>>> that's the case you can overrule it by loading (not requiring)
>>> gnus-util explicitly somewhere in your .emacs.
>>
>> No, I'm pretty sure it's the code itself -- I never had this problem
>> before, and emacs -q cannot find the gnus-util feature, and... reverting
>> 9b59bbc fixes the problem!
>>
>> I don't know why having the defalias at top level would prevent it from
>> working, but apparently it does...
>
> Hmm, there may be more going on than I realized. It looks like I really
> am loading the gnus-util.el that comes with Emacs, not from the Gnus git
> repo. But then why did reverting that commit seem to fix it? I'll try a
> few more times...

Well I'm not any closer to making sense of this. I do seem to be loading
the gnus-util that comes with Emacs, no matter what. And yet,
reverting/replacing that commit pretty clearly breaks (or fixes) whether
I'm able to use gnus-format-message. I'm stumped!




  reply	other threads:[~2016-01-06 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  9:04 Alan Schmitt
2016-01-05  9:18 ` Eric Abrahamsen
2016-01-05  9:32   ` Eric Abrahamsen
2016-01-06  3:41     ` Dave Goldberg
2016-01-06  9:17       ` Eric Abrahamsen
2016-01-06 10:07         ` Eric Abrahamsen
2016-01-06 11:20           ` Eric Abrahamsen [this message]
2016-01-05  9:52   ` Alan Schmitt
2016-01-05  9:55     ` Eric Abrahamsen
2016-01-05 10:32       ` Alan Schmitt
2016-01-05 11:02         ` CHENG Gao
2016-01-05 13:41           ` Alan Schmitt
2016-01-05 11:08         ` Eric Abrahamsen
2016-01-05 13:44           ` Alan Schmitt
2016-01-05 15:13             ` 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=878u43vtsk.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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).