all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs/pretest@rum.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
	emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: info invisible changes
Date: Tue, 05 Nov 2002 13:49:33 -0500	[thread overview]
Message-ID: <200211051849.gA5InXc29965@rum.cs.yale.edu> (raw)
In-Reply-To: buowunsirq5.fsf@mcspd15.ucom.lsi.nec.co.jp

> When I do `Memacs' from the top-level dir (with point at the beginning
> of the buffer), I get the following error:
> 
>    Debugger entered--Lisp error: (error "No such anchor in tag table or node in tag table or file: The extensible self-documenting text editor")
>      signal(error ("No such anchor in tag table or node in tag table or file: The extensible self-documenting text editor"))
>      error("No such anchor in tag table or node in tag table or file: %s" "The extensible self-documenting text editor")
>      byte-code(...)
>      Info-find-node-2(nil "The extensible self-documenting text editor" nil)
>      Info-find-node(nil "The extensible self-documenting text editor")
>      Info-goto-node("The extensible self-documenting text editor" nil)
>      Info-menu("Emacs" nil)
>      call-interactively(Info-menu)
> 
> [Note that the "The extensible ..." is the descriptive text for the
>  `Emacs' menu line, so apparently the `M' command is getting confused
>  about how things are formatted.]

Can you try again ?  There's been changes w.r.t. intangibility
which might explain the bug and which should be fixed now.
This also applies to the cursor motion.  It's definitely not
perfect now but it's probably slightly different.

> There are some other, more minor problems with this:
> 
>   (1) The dir file (and presumably other info menus) I have was
>       formatted assuming that no text would be hidden, so in some cases,
>       the invisible text results in a very wierd looking display.
> 
>       Here's an example display from my *info* dir node (these are all
>       debian entries):
> 
> --- begin quote ---
> * CVS		        Concurrent Versions
> 						     System
> * CVS client/server     Describes the
> 						     client/server protocol
> 						     used by CVS.
> * gcc-295		The GNU Compiler
> 						     Collection (Version
> 						     2.95.x).
> * Gdb			The GNU debugger.
> * Gdb-Internals		The GNU debugger's
> 						     internals.
> ---  end quote  ---

We should probably refill the text.  After all, I think this problem only
happens for the `dir' file, not in other menus.


	Stefan

  reply	other threads:[~2002-11-05 18:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  8:04 info invisible changes Miles Bader
     [not found] ` <200211011623.gA1GNAL03601@rum.cs.yale.edu>
2002-11-05  4:08   ` Miles Bader
2002-11-05 18:49     ` Stefan Monnier [this message]
2002-11-07  4:49       ` Richard Stallman
2002-11-05 23:57     ` Kim F. Storm
2002-11-06  9:51       ` Miles Bader
2002-11-06 12:46         ` Kim F. Storm
2002-11-06 12:30           ` Miles Bader
2002-11-06 15:11         ` Stefan Monnier
2002-11-06 16:32           ` Miles Bader
2002-11-07 15:08           ` Richard Stallman
2002-11-12 10:11             ` Kim F. Storm
2002-11-12  9:22               ` Miles Bader
2002-11-12 10:59                 ` Kim F. Storm
2002-11-12 17:28                   ` Robert J. Chassell
2002-11-13 14:37                     ` Kim F. Storm
2002-11-13 18:20                       ` Robert J. Chassell
2002-11-14 12:17                         ` Richard Stallman
2002-11-14 21:38                           ` Kim F. Storm
2002-11-12 18:49               ` Stefan Monnier
2002-11-13 23:31                 ` Kim F. Storm
2002-11-14  0:39                 ` Kim F. Storm
2002-11-14  4:09               ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14 13:57 Karl Berry

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=200211051849.gA5InXc29965@rum.cs.yale.edu \
    --to=monnier+gnu/emacs/pretest@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.