Info navigation is broken

Info navigation is broken

[David Ponce]

Hello,

Info navigation using [u]p, [n]ext, [p]rev commands is broken in
CVS version of Emacs 21.  Here is a backtrace:

Debugger entered--Lisp error: (error "Node has no Up")
  signal(error ("Node has no Up"))
  error("Node has no %s" "Up")
  Info-extract-pointer("up")
  Info-up()
* call-interactively(Info-up)

Also it seems that there are two header lines in the Info buffer, like
this:

File: dir, Node: Top This is the top of the INFO tree <== header line
 File: dir, Node: Top This is the top of the INFO tree <== buffer

After commenting out the following line in `Info-setup-header-line'
Info navigation worked fine again.

;;; It is useful to be able to copy the links line out of the buffer
;;; with M-w.
;;;    (narrow-to-region (1+ header-end) (point-max))

Sincerely,
David

In GNU Emacs 21.3.50.1 (i386-mingw-nt4.0.1381)
 of 2002-05-30 on EBAT311
configured using `configure --with-gcc (2.95)'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: t

Re: Info navigation is broken

[David Ponce]

> After commenting out the following line in `Info-setup-header-line'
> Info navigation worked fine again.
>
> ;;; It is useful to be able to copy the links line out of the buffer
> ;;; with M-w.
>   (narrow-to-region (1+ header-end) (point-max))


Oops!   You should have read :  After uncommenting the abobe line.

Sorry!

Re: Info navigation is broken

[Richard Stallman]

Thanks for the bug report.  Does this patch fix it?

*** info.el.~1.301.~	Wed May 29 12:45:59 2002
--- info.el	Sun Jun  2 20:20:56 2002
***************
*** 1247,1256 ****
      (save-excursion
        (save-restriction
  	(goto-char (point-min))
! 	(when Info-header-line
! 	  ;; expose the header line in the buffer
! 	  (widen)
! 	  (forward-line -1))
  	(let ((bound (point)))
  	  (forward-line 1)
  	  (cond ((re-search-backward (concat name ":") bound t)
--- 1247,1256 ----
      (save-excursion
        (save-restriction
  	(goto-char (point-min))
! ;;; 	(when Info-header-line
! ;;; 	  ;; expose the header line in the buffer
! ;;; 	  (widen)
! ;;; 	  (forward-line -1))
  	(let ((bound (point)))
  	  (forward-line 1)
  	  (cond ((re-search-backward (concat name ":") bound t)

Re: Info navigation is broken

[David Ponce]

Richard Stallman wrote:
> Thanks for the bug report.  Does this patch fix it?

Yes thanks!  Navigation works now.  But there are still two headers:

One in the header line like this (menu Help/Read the Emacs Manual):

Next: Distrib,  Prev: (dir),  Up: (dir)

Another in the buffer (the first line):

File: emacs,  Node: Top,  Next: Distrib,  Prev: (dir),  Up: (dir)

I just started Emacs with emacs -q --no-site-file.

David



__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

Re: Info navigation is broken

[Richard Stallman]

    Yes thanks!  Navigation works now.  But there are still two headers:

Yes, that is deliberate.

Re: Info navigation is broken

[Stefan Monnier]

>     Yes thanks!  Navigation works now.  But there are still two headers:
> Yes, that is deliberate.

Can we scroll the buffer so that the first line (the one that duplicates
the content of the header-line) is initially not displayed ?


	Stefan

Re: Info navigation is broken

[Eli Zaretskii]

> From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
> Date: Wed, 05 Jun 2002 11:16:40 -0400
> 
> Can we scroll the buffer so that the first line (the one that duplicates
> the content of the header-line) is initially not displayed ?

I'd second that.

Re: Info navigation is broken

[Miles Bader]

"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > Can we scroll the buffer so that the first line (the one that duplicates
> > the content of the header-line) is initially not displayed ?
> 
> I'd second that.

... or just make the feature optional.  It seems all the comments about
this feature so far are negative.

-Miles

-- 
`Life is a boundless sea of bitterness'

Re: Info navigation is broken

[Eli Zaretskii]

On 6 Jun 2002, Miles Bader wrote:

> "Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > > Can we scroll the buffer so that the first line (the one that duplicates
> > > the content of the header-line) is initially not displayed ?
> > 
> > I'd second that.
> 
> ... or just make the feature optional.

Even better.  (I think I already suggested that in the past.)

Re: Info navigation is broken

[Richard Stallman]

    Can we scroll the buffer so that the first line (the one that duplicates
    the content of the header-line) is initially not displayed ?

It is possible but I think the bad effects exceed the good.