Gnus development mailing list
 help / color / mirror / Atom feed
* Re: 23.0.60; GNUS manual, `T' - bad nodes
       [not found] ` <873anjocc8.fsf@jurta.org>
@ 2008-06-12  6:23   ` Reiner Steib
  2008-06-15 22:19     ` Reiner Steib
  0 siblings, 1 reply; 3+ messages in thread
From: Reiner Steib @ 2008-06-12  6:23 UTC (permalink / raw)
  To: Juri Linkov; +Cc: ding, Drew Adams, emacs-devel

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/




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 23.0.60; GNUS manual, `T' - bad nodes
  2008-06-12  6:23   ` 23.0.60; GNUS manual, `T' - bad nodes Reiner Steib
@ 2008-06-15 22:19     ` Reiner Steib
  2008-06-16 17:31       ` Drew Adams
  0 siblings, 1 reply; 3+ messages in thread
From: Reiner Steib @ 2008-06-15 22:19 UTC (permalink / raw)
  To: Juri Linkov; +Cc: Drew Adams, emacs-devel, ding

On Thu, Jun 12 2008, Reiner Steib wrote:

> On Thu, Jun 12 2008, Juri Linkov wrote:
>> This doesn't work because Gnus uses invalid characters in node
>> names.  See (info "(texinfo) Node Line Requirements") that says:
[...]
> 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.)

Fixed in v5-10.  It will propagate to Emacs_22 and to the trunk (Emacs
and Gnus) eventually.

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: 23.0.60; GNUS manual, `T' - bad nodes
  2008-06-15 22:19     ` Reiner Steib
@ 2008-06-16 17:31       ` Drew Adams
  0 siblings, 0 replies; 3+ messages in thread
From: Drew Adams @ 2008-06-16 17:31 UTC (permalink / raw)
  To: 'Reiner Steib', 'Juri Linkov'; +Cc: ding, emacs-devel

FWIW, I expected to receive this from bug-gnu-emacs, or perhaps
emacs-pretest-bug (where I submitted the bug), not from emacs-devel.

I admit it. I'm lost in the bug mails labyrinth.
I have no idea what to expect anymore.

> From: Reiner Steib Sent: Sunday, June 15, 2008 3:19 PM
> To: Juri Linkov Cc: Drew Adams; emacs-devel@gnu.org; ding@gnus.org
> Subject: Re: 23.0.60; GNUS manual, `T' - bad nodes
> On Thu, Jun 12 2008, Reiner Steib wrote:
> > On Thu, Jun 12 2008, Juri Linkov wrote:
> >> This doesn't work because Gnus uses invalid characters in node
> >> names.  See (info "(texinfo) Node Line Requirements") that says:
> [...]
> > 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.)
> 
> Fixed in v5-10.  It will propagate to Emacs_22 and to the trunk (Emacs
> and Gnus) eventually.





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-06-16 17:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <00c101c8cb88$ddf48700$0200a8c0@us.oracle.com>
     [not found] ` <873anjocc8.fsf@jurta.org>
2008-06-12  6:23   ` 23.0.60; GNUS manual, `T' - bad nodes Reiner Steib
2008-06-15 22:19     ` Reiner Steib
2008-06-16 17:31       ` Drew Adams

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).