gnus-subscribe-topics

gnus-subscribe-topics

[Xavier Maillard]

Hi,

I have thiss in my .gnus file:

(setq gnus-subscribe-newsgroup-method 'gnus-subscribe-topics)

I have created a Topic named "emacs" for which I added a topic
parameter via Gp:

((subscribe . "emacs"))

If I am subscribing to a group matching this regexp say,
fr.comp.applications.emacs, it is not put under the right topic.
If I am doing:

(gnus-subscribe-topics "fr.comp.applications.emacs")

manually, it is filled under the right Topic.

What's wrong ?

Xavier

P.S: please keep me in the Cc as I am not subscribed to this list yet.

Re: gnus-subscribe-topics

[Reiner Steib]

On Sun, Jan 04 2009, Xavier Maillard wrote:

> (setq gnus-subscribe-newsgroup-method 'gnus-subscribe-topics)
>
> I have created a Topic named "emacs" for which I added a topic
> parameter via Gp:
>
> ((subscribe . "emacs"))
>
> If I am subscribing to a group matching this regexp say,
> fr.comp.applications.emacs, it is not put under the right topic.
> If I am doing:
>
> (gnus-subscribe-topics "fr.comp.applications.emacs")
>
> manually, it is filled under the right Topic.
>
> What's wrong ?

,----[ (info "(gnus)Subscription Methods") ]
| What Gnus does when it encounters a new group is determined by the
| `gnus-subscribe-newsgroup-method' variable.
`----

"when it encounters a new group" is not the case in your situation.
This variable is relevant only if a new newsgroup is created on the
server.

> P.S: please keep me in the Cc as I am not subscribed to this list yet.

Hint: Gnus honors Mail-Followup-To. :-)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: gnus-subscribe-topics

[Xavier Maillard]

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Sun, Jan 04 2009, Xavier Maillard wrote:
>
>> (setq gnus-subscribe-newsgroup-method 'gnus-subscribe-topics)
>>
>> I have created a Topic named "emacs" for which I added a topic
>> parameter via Gp:
>>
>> ((subscribe . "emacs"))
>>
>> If I am subscribing to a group matching this regexp say,
>> fr.comp.applications.emacs, it is not put under the right topic.
>> If I am doing:
>>
>> (gnus-subscribe-topics "fr.comp.applications.emacs")
>>
>> manually, it is filled under the right Topic.
>>
>> What's wrong ?
>
> ,----[ (info "(gnus)Subscription Methods") ]
> | What Gnus does when it encounters a new group is determined by the
> | `gnus-subscribe-newsgroup-method' variable.
> `----
>
> "when it encounters a new group" is not the case in your situation.
> This variable is relevant only if a new newsgroup is created on the
> server.

Can't this behaviour be changed for any group (new or existing
but never subscribed) ? What is the workaround ? Currently, I did
not subcribe to any nnimap groups (I have 4 dozens of them
pending) since I do not want to manually fill them under the
right topic.

>> P.S: please keep me in the Cc as I am not subscribed to this list yet.
>
> Hint: Gnus honors Mail-Followup-To. :-)

Done (hope it is correct).

Xavier

Re: gnus-subscribe-topics

[Andreas Seltenreich]

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

Xavier Maillard writes:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> ,----[ (info "(gnus)Subscription Methods") ]
>> | What Gnus does when it encounters a new group is determined by the
>> | `gnus-subscribe-newsgroup-method' variable.
>> `----
>>
>> "when it encounters a new group" is not the case in your situation.
>> This variable is relevant only if a new newsgroup is created on the
>> server.
>
> Can't this behaviour be changed for any group (new or existing
> but never subscribed) ? What is the workaround ? Currently, I did
> not subcribe to any nnimap groups (I have 4 dozens of them
> pending) since I do not want to manually fill them under the
> right topic.

I've modified my copy of Gnus to use gnus-subscribe-newsgroup-method
when subscribing from a Browse Server buffer a long time ago.  I didn't
propose to include this patch though because the default value of
g-s-n-m is rather inappropriate for explicitly subscribing groups.

Attached is a version that introduces a
gnus-browse-subscribe-newsgroup-method variable instead.  OK to commit
to No Gnus?  I vaguely remeber some discussion about a feature freeze
(Reiner?).

>>> P.S: please keep me in the Cc as I am not subscribed to this list yet.
>>
>> Hint: Gnus honors Mail-Followup-To. :-)
>
> Done (hope it is correct).

The comma looks like a typo to me.  You can avoid this by letting
Message Mode generate the header.  C-c C-f C-a runs the command
message-generate-unsubscribed-mail-followup-to.

regards,
andreas

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-srvr.diff --]
[-- Type: text/x-diff, Size: 3984 bytes --]

Index: gnus-srvr.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-srvr.el,v
retrieving revision 7.36
diff -c -r7.36 gnus-srvr.el
*** gnus-srvr.el	22 Jan 2009 07:02:16 -0000	7.36
--- gnus-srvr.el	23 Feb 2009 00:09:45 -0000
***************
*** 635,640 ****
--- 635,663 ----
  ;;; Browse Server Mode
  ;;;
  
+ (defcustom gnus-browse-subscribe-newsgroup-method
+   'gnus-subscribe-alphabetically
+   "Function(s) called when subscribing groups in the Browse Server Buffer
+ A few pre-made functions are supplied: `gnus-subscribe-randomly'
+ inserts new groups at the beginning of the list of groups;
+ `gnus-subscribe-alphabetically' inserts new groups in strict
+ alphabetic order; `gnus-subscribe-hierarchically' inserts new groups
+ in hierarchical newsgroup order; `gnus-subscribe-interactively' asks
+ for your decision; `gnus-subscribe-killed' kills all new groups;
+ `gnus-subscribe-zombies' will make all new groups into zombies;
+ `gnus-subscribe-topics' will enter groups into the topics that
+ claim them."
+   :group 'gnus-server
+   :type '(radio (function-item gnus-subscribe-randomly)
+ 		(function-item gnus-subscribe-alphabetically)
+ 		(function-item gnus-subscribe-hierarchically)
+ 		(function-item gnus-subscribe-interactively)
+ 		(function-item gnus-subscribe-killed)
+ 		(function-item gnus-subscribe-zombies)
+ 		(function-item gnus-subscribe-topics)
+ 		function
+ 		(repeat function)))
+ 
  (defvar gnus-browse-menu-hook nil
    "*Hook run after the creation of the browse mode menu.")
  
***************
*** 885,891 ****
    (gnus-browse-next-group (- n)))
  
  (defun gnus-browse-unsubscribe-current-group (arg)
!   "(Un)subscribe to the next ARG groups."
    (interactive "p")
    (when (eobp)
      (error "No group at current line"))
--- 908,916 ----
    (gnus-browse-next-group (- n)))
  
  (defun gnus-browse-unsubscribe-current-group (arg)
!   "(Un)subscribe to the next ARG groups.
! The variable `gnus-browse-subscribe-newsgroup-method' determines
! how new groups will be entered into the group buffer."
    (interactive "p")
    (when (eobp)
      (error "No group at current line"))
***************
*** 934,955 ****
  	    ;; subscribe to it.
   	    (if (gnus-ephemeral-group-p group)
  		(gnus-kill-ephemeral-group group))
! 	    ;; We need to discern between killed/zombie groups and
! 	    ;; just unsubscribed ones.
! 	    (gnus-group-change-level
! 	     (or (gnus-group-entry group)
! 		 (list t group gnus-level-default-subscribed
! 		       nil nil (if (gnus-server-equal
! 				    gnus-browse-current-method "native")
! 				   nil
! 				 (gnus-method-simplify
! 				  gnus-browse-current-method))))
! 	     gnus-level-default-subscribed (gnus-group-level group)
! 	     (and (car (nth 1 gnus-newsrc-alist))
! 		  (gnus-group-entry (car (nth 1 gnus-newsrc-alist))))
! 	     (null (gnus-group-entry group)))
  	    (delete-char 1)
! 	    (insert ? ))
  	(gnus-group-change-level
  	 group gnus-level-unsubscribed gnus-level-default-subscribed)
  	(delete-char 1)
--- 959,982 ----
  	    ;; subscribe to it.
   	    (if (gnus-ephemeral-group-p group)
  		(gnus-kill-ephemeral-group group))
! 	    (let ((entry (gnus-group-entry group)))
! 	      (if entry
! 		  ;; Just change the subscription level if it is an
! 		  ;; unsubscribed group.
! 		  (gnus-group-change-level entry
! 					   gnus-level-default-subscribed)
! 		;; If it is a killed group or a zombie, feed it to the
! 		;; mechanism for new group subscription.
! 		(gnus-call-subscribe-functions
! 		 gnus-browse-subscribe-newsgroup-method
! 		 group)))
  	    (delete-char 1)
! 	    (insert (let ((lvl (gnus-group-level group)))
! 		      (cond
! 		       ((< lvl gnus-level-unsubscribed) ? )
! 		       ((< lvl gnus-level-zombie) ?U)
! 		       ((< lvl gnus-level-killed) ?Z)
! 		       (t ?K)))))
  	(gnus-group-change-level
  	 group gnus-level-unsubscribed gnus-level-default-subscribed)
  	(delete-char 1)

Re: gnus-subscribe-topics

[Andreas Seltenreich]

I wrote:

> Xavier Maillard writes:
>
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>
>>> ,----[ (info "(gnus)Subscription Methods") ]
>>> | What Gnus does when it encounters a new group is determined by the
>>> | `gnus-subscribe-newsgroup-method' variable.
>>> `----
>>>
>>> "when it encounters a new group" is not the case in your situation.
>>> This variable is relevant only if a new newsgroup is created on the
>>> server.
>>
>> Can't this behaviour be changed for any group (new or existing
>> but never subscribed) ? What is the workaround ? Currently, I did
>> not subcribe to any nnimap groups (I have 4 dozens of them
>> pending) since I do not want to manually fill them under the
>> right topic.
>
> I've modified my copy of Gnus to use gnus-subscribe-newsgroup-method
> when subscribing from a Browse Server buffer a long time ago.  I didn't
> propose to include this patch though because the default value of
> g-s-n-m is rather inappropriate for explicitly subscribing groups.
>
> Attached is a version that introduces a
> gnus-browse-subscribe-newsgroup-method variable instead.  OK to commit
> to No Gnus?  I vaguely remeber some discussion about a feature freeze
> (Reiner?).

It looks more like thawing period at the moment, so I pushed this in.

regards,
andreas