Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Juri Linkov <juri@jurta.org>
Cc: ding@gnus.org, Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: 23.0.60; GNUS manual, `T' - bad nodes
Date: Thu, 12 Jun 2008 08:23:05 +0200	[thread overview]
Message-ID: <v97icvdvee.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <873anjocc8.fsf@jurta.org> (Juri Linkov's message of "Thu, 12 Jun 2008 01:34:03 +0300")

On Thu, Jun 12 2008, Juri Linkov wrote:

>> Open Info to the GNUS manual.
>> Use `T' to see the TOC.
>>
>> Try any of the FAQ links. You get an error message.
>> Plus, those links are not rendered (created) correctly.
>
> This doesn't work because Gnus uses invalid characters in node
> names.  See (info "(texinfo) Node Line Requirements") that says:
> "you cannot use periods, commas, colons or parentheses within
> a node name".  But there are periods in node names like "[1.1]".

I don't have time to deal with this now[1].  Could some assign this
(part of the) bug to Gnus in the bug tracker, please?  (It also
applies to Emacs 22.2 / Gnus 5.10.x.)

Bye, Reiner.

[1] We need to decide if we want to keep gnus-faq.xml or use
    gnus-faq.texi as the primary source and drop gnus-faq.xml.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




       reply	other threads:[~2008-06-12  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00c101c8cb88$ddf48700$0200a8c0@us.oracle.com>
     [not found] ` <873anjocc8.fsf@jurta.org>
2008-06-12  6:23   ` Reiner Steib [this message]
2008-06-15 22:19     ` Reiner Steib
2008-06-16 17:31       ` Drew Adams

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=v97icvdvee.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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).