>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:


    Ted> Could you use nnir-original-group and nnir-original-subject in
    Ted> the let you said you would do?  I'll make the names more
    Ted> general if anyone else needs it but I was thinking this way
    Ted> it's clear that it's a nnir requirement.

    Ted> That way the registry will not care what nnir does to the
    Ted> subject or group name, it will just take the originals from the
    Ted> let-bound variables.


In fact I'm thinking about a different way (but this might not be best
way):


1. nnir ends up replacing the parsed header with a new one, so the
original subject isn't available anymore, but its easy enough to get
back with a simple string-match. And the only place the original subject
is used is in the registry, which is why I thought that it was best to
just modify gnus-registry-simplify-subject to:

(defun gnus-registry-simplify-subject (subject)
  (if (stringp subject)
      (progn
	(string-match "^\\[[0-9]+:.+/[0-9]+\\] " subject)
	(setq subject (substring subject (match-end 0)))
	(gnus-simplify-subject subject))
    nil))


2. As for the original newsgroup name, I am trying to avoid anything
nnir specific outside the nnir.el file. Its also possible that
other/future virtual backends might want to do something similar so I've
tried an approach that won't require special-casing. The trick is to
pass the original newsgroup name back in to gnus-summary-move-article. I
think this is easy---just introduce a let-bound variable
gnus-original-newsgroup-name initialized to gnus-newsgroup-name and let
the backend-specific 'request-move-article replace it as needed. So only
a few lines of changes and no need for nnir-specific code.


Sorry for being so wordy, and let me know if I'm off-base.  Here is the
proposed patch.