From: "N. Jackson" <nljlistbox2@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Typo in doc string of `gnus-dependencies-add-header'?
Date: Sun, 22 Jul 2018 15:24:13 -0400 [thread overview]
Message-ID: <87in57ysyq.fsf@moondust.localdomain> (raw)
In-Reply-To: <87zhyjp5nj.fsf@ericabrahamsen.net>
Hi Eric,
Thank you for the response.
At 10:00 -0700 on Sunday 2018-07-22, Eric Abrahamsen wrote:
>
> "N. Jackson" <nljlistbox2@gmail.com> writes:
>
>> In Gnus v5.13 in GNU Emacs 27.0.50
>> Repository revision: f3f67cf0b9a6388d423e048a7aafad2eb531b5a5
>
> If you're using Emacs 27, you shouldn't be loading Gnus
> externally!
Hmm... what makes you think that I am?
As far as I am aware, I am not running an external Gnus. I can't
see anything in my configuration that would load an external Gnus,
I don't have any Gnus-related load path shadows, and in Package
Manager it says I have the "built-in" Gnus.
So I think (probably) that I am okay here.
> FWIW, the docstring of `gnus-summary-ignore-duplicates' now
> reads:
>
> "If non-nil, ignore articles with identical Message-ID headers."
Yes, I see that here too. To be clear, this is about the doc
string of the function `gnus-dependencies-add-header', not the doc
string of the variable `gnus-summary-ignore-duplicates'.
> Your bug may still be there, but it will be much more productive to
> investigate the Gnus code in Emacs' master branch.
I just went and double checked that. (You had me worried for a
moment!) But I am looking at the sources checked out from Emacs
master, so no worries there.
Thanks,
N.
next prev parent reply other threads:[~2018-07-22 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 13:37 N. Jackson
2018-07-22 17:00 ` Eric Abrahamsen
2018-07-22 19:24 ` N. Jackson [this message]
2018-07-22 20:17 ` Eric Abrahamsen
2018-07-24 17:56 ` N. Jackson
2018-07-24 20:14 ` Eric Abrahamsen
2018-07-26 0:37 ` 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=87in57ysyq.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=info-gnus-english@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 NNTP newsgroup(s).