From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Subject field in summary buffer modified
Date: Thu, 29 Jan 2015 22:15:58 +0100 [thread overview]
Message-ID: <8761bpp9td.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87a912q6ey.fsf@topper.koldfront.dk>
Adam writes:
>> It could be... er... `gnus-simplify-subject-functions', perhaps? Or
>> `gnus-simplify-ignored-prefixes'.
> Let me see... Well, they are both nil :-/
Here is an article that exhibits the problem in Gnus for me:
news.gmane.org gwene.dk.gaffa.anmeldelser.cd:106
Hm. Let me just ngrep what happens when I read it, to see what comes
over the wire..
Oh. Encryption. Great.
Ok, let me telnet:
$ telnet news.gwene.org nntp
Trying 80.91.229.13...
Connected to news.gwene.org.
Escape character is '^]'.
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
group gwene.dk.gaffa.anmeldelser.cd
211 107 1 107 gwene.dk.gaffa.anmeldelser.cd
article 106
220 106 <x1-uNZ7JGyTNme0mVkrfXTsQk2zjXE@gwene.org> article
[...]
Subject: Mindi Abair: Wild Heart [4/6]
[...]
.
xover 106-106
224 Overview information for 106-106 follows
106 Mindi Abair: Wild Heart [4/6] unknown <post@gwene.org> Tue, 27 Jan 2015 08:00:00 +0100 <x1-uNZ7JGyTNme0mVkrfXTsQk2zjXE@gwene.org> 999 2 Xref: news.gmane.org gwene.dk.gaffa.anmeldelser.cd:106
.
quit
205 Bye!
Connection closed by foreign host.
$
This makes me think that it is Gnus doing this. Hm.
Can I find the right function to edebug? Ok, found it - by trial and error:
gnus-summary-remove-list-identifiers
is the culprit. It removes "^[A-Z ]*?: " (!)
My elisp fu fails me now, this function:
(defun gnus-group-get-list-identifiers (group)
"Get list identifier regexp for GROUP."
(or (gnus-parameter-list-identifier group)
(if (consp gnus-list-identifiers)
(mapconcat 'identity gnus-list-identifiers " *\\|")
gnus-list-identifiers)))
returns "^[A-Z ]*?: " even though gnus-list-identifiers is nil?!?
Something is setting gnus-list-identifiers behind my back locally, somehow?!
Because if I run: (gnus-group-get-list-identifiers
"nntp+news.gwene.org:gwene.dk.gaffa.anmeldelser.cd") directly, it
returns nil, as I expect.
I can't for the life of me figure out how that happens, when I edebug
the function and do C-h v on gnus-list-identifers, I'm told it is nil.
But edebugging I can see that consp returns t and the function returns
"^[A-Z ]*?: ".
If I change it to:
(defun gnus-group-get-list-identifiers (group)
"Get list identifier regexp for GROUP."
nil)
The summary looks as I expected it to do, nothing removed.
Ok, elisp experts - enlighten me!
Best regards,
Adam
--
"Har du computer, som starter op i DOS, så' det: Adam Sjøgren
*blah* *blah* Adios amigos!" asjo@koldfront.dk
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2015-01-29 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18148.1421683311.1147.info-gnus-english@gnu.org>
2015-01-29 3:14 ` Lars Ingebrigtsen
2015-01-29 9:31 ` Adam Sjøgren
2015-01-29 21:15 ` Adam Sjøgren [this message]
[not found] ` <mailman.18934.1422566175.1147.info-gnus-english@gnu.org>
2015-02-05 3:40 ` Lars Ingebrigtsen
2015-02-05 13:33 ` Adam Sjøgren
2015-01-19 16:01 Adam Sjøgren
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=8761bpp9td.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).