Gnus development mailing list
 help / color / mirror / Atom feed
From: Frank Haun <pille3003@fhaun.de>
Subject: Problems when subscribing nntp groups from Server Buffer
Date: Sun, 18 May 2003 16:23:33 +0200	[thread overview]
Message-ID: <86fznc9vve.fsf@pille.fhaun.de> (raw)

NNTP Groups which are subscribed via Server Buffer are not updated after `g',
nor when I set `gnus-activate-foreign-newsgroups' to `3' and  `b' (b runs
the command gnus-group-check-bogus-groups) make those groups vanish.

Just `M-g' on those groups works.

With ognus-0.18 everything works fine, the problems appeared with
ognus-0.19.

`G E' in the Group Buffer says:

Oort Gnus v0.18
;;; Editing the select method for `gmane.emacs.psgml.user'.

Gnus v5.10.3
;;; Editing the select method for `nntp+localhost:gmane.emacs.psgml.user'.

Hitting `A A' in Gnus v5.10.3 and subscribing groups works fine too, but
thats not the recommended method for subscribing.

Using the _old_ `gnus-browse-group-name' from Oort Gnus v0.18 works
fine.

    (defun gnus-browse-group-name ()
      (save-excursion
        (beginning-of-line)
        (let ((name (get-text-property (point) 'gnus-group)))
          (when (re-search-forward ": \\(.*\\)$" (gnus-point-at-eol) t)
            (gnus-group-prefixed-name
             (or name
                 (match-string-no-properties 1))
             gnus-browse-current-method)))))

Hm, I've done some edebug on the _current_ `gnus-browse-group-name'.

(defun gnus-browse-group-name ()
...
    gnus-browse-current-method
    => (nntp "localhost")

    (gnus-method-to-server-name gnus-browse-current-method)
    => "nntp+localhost"

    name
    => "gmane.emacs.psgml.devel"

    (concat (gnus-method-to-server-name gnus-browse-current-method) ":" 
            (or name
                (match-string-no-properties 1)))
    => "nntp+localhost:gmane.emacs.psgml.devel"

And there is

    `(defsubst gnus-method-to-server-name (method)'
    => "nntp+localhost"

What can I do? Do you need more info. :-)

\f

Ok, here some more from "gnus.gnus-bug".

Some edebugging on `gnus-get-unread-articles':

> [Lars] They should be activated by the code that starts with
>
> [Lars]  ;; These groups are foreign.  Check the level.
> [Lars]  (when (and (<= (gnus-info-level info) foreign-level)

This will never reached, cause

          (and (setq method (gnus-info-method info))
               (not (inline
                      (gnus-server-equal
                       gnus-select-method
                       (setq method (gnus-server-get-method nil method)))))
               (not (gnus-secondary-method-p method)))

returns `nil'.

Here some variables and code I've evaluated:

    group
     => "nntp+localhost:gmane.emacs.psgml.user"

    info
    => ("nntp+localhost:gmane.emacs.psgml.user" 3 nil ((seen 1)))

    gnus-select-method
    => (nntp "localhost")

    (setq method (gnus-info-method info))
    => nil

    (not (inline
           (gnus-server-equal
            gnus-select-method
            (setq method (gnus-server-get-method nil method)))))
    => nil

    (not (gnus-secondary-method-p method))
    => t

Frank



             reply	other threads:[~2003-05-18 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 14:23 Frank Haun [this message]
2003-10-18 13:34 ` Lars Magne Ingebrigtsen
2003-10-18 14:38   ` Frank Haun

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=86fznc9vve.fsf@pille.fhaun.de \
    --to=pille3003@fhaun.de \
    /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).