unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Subject: info invisible changes
Date: 01 Nov 2002 17:04:20 +0900	[thread overview]
Message-ID: <buoy98dhg1n.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)

Hi Kim,\r਀ഊI see you put in your info changes.\r਀ഊIt does look nicer (cleaner), but there are some problems:\r਀ഊWhen I do `Memacs' from the top-level dir (with point at the beginning\r਀漀昀 琀栀攀 戀甀昀昀攀爀⤀Ⰰ 䤀 最攀琀 琀栀攀 昀漀氀氀漀眀椀渀最 攀爀爀漀爀㨀ഊ\r਀   䐀攀戀甀最最攀爀 攀渀琀攀爀攀搀ⴀⴀ䰀椀猀瀀 攀爀爀漀爀㨀 ⠀攀爀爀漀爀 ∀一漀 猀甀挀栀 愀渀挀栀漀爀 椀渀 琀愀最 琀愀戀氀攀 漀爀 渀漀搀攀 椀渀 琀愀最 琀愀戀氀攀 漀爀 昀椀氀攀㨀 吀栀攀 攀砀琀攀渀猀椀戀氀攀 猀攀氀昀ⴀ搀漀挀甀洀攀渀琀椀渀最 琀攀砀琀 攀搀椀琀漀爀∀⤀ഊ     signal(error ("No such anchor in tag table or node in tag table or file: The extensible self-documenting text editor"))\r਀     攀爀爀漀爀⠀∀一漀 猀甀挀栀 愀渀挀栀漀爀 椀渀 琀愀最 琀愀戀氀攀 漀爀 渀漀搀攀 椀渀 琀愀最 琀愀戀氀攀 漀爀 昀椀氀攀㨀 ─猀∀ ∀吀栀攀 攀砀琀攀渀猀椀戀氀攀 猀攀氀昀ⴀ搀漀挀甀洀攀渀琀椀渀最 琀攀砀琀 攀搀椀琀漀爀∀⤀ഊ     byte-code("Æ\b!ƒ1\0\b\x19Ç	\n\"‰^[ƒ0\0\vA@\x14È\v8É=„!\0Ê\f!\x14\v@ƒ0\0\f‰\x15bˆËÌÍ\"ˆ*eÎ\f!ÏZ]bˆÐ\n!‰\x1e\x13ƒL\0\x0e\x13bˆËÌÍ\"ˆÑÒ\x0e\x14\"ˆ)Ƈ" [Info-tag-table-marker m regexp found guesspos anchorpos marker-position Info-find-in-tag-table 2 Info-mode Info-read-subfile throw foo t byte-to-position 1000 Info-find-node-in-buffer error "No such anchor in tag table or node in tag table or file: %s" pos nodename] 4)\r਀     䤀渀昀漀ⴀ昀椀渀搀ⴀ渀漀搀攀ⴀ㈀⠀渀椀氀 ∀吀栀攀 攀砀琀攀渀猀椀戀氀攀 猀攀氀昀ⴀ搀漀挀甀洀攀渀琀椀渀最 琀攀砀琀 攀搀椀琀漀爀∀ 渀椀氀⤀ഊ     Info-find-node(nil "The extensible self-documenting text editor")\r਀     䤀渀昀漀ⴀ最漀琀漀ⴀ渀漀搀攀⠀∀吀栀攀 攀砀琀攀渀猀椀戀氀攀 猀攀氀昀ⴀ搀漀挀甀洀攀渀琀椀渀最 琀攀砀琀 攀搀椀琀漀爀∀ 渀椀氀⤀ഊ     Info-menu("Emacs" nil)\r਀     挀愀氀氀ⴀ椀渀琀攀爀愀挀琀椀瘀攀氀礀⠀䤀渀昀漀ⴀ洀攀渀甀⤀ഊ\r਀嬀一漀琀攀 琀栀愀琀 琀栀攀 ∀吀栀攀 攀砀琀攀渀猀椀戀氀攀 ⸀⸀⸀∀ 椀猀 琀栀攀 搀攀猀挀爀椀瀀琀椀瘀攀 琀攀砀琀 昀漀爀 琀栀攀ഊ `Emacs' menu line, so apparently the `M' command is getting confused\r਀ 愀戀漀甀琀 栀漀眀 琀栀椀渀最猀 愀爀攀 昀漀爀洀愀琀琀攀搀⸀崀ഊ\r਀ഊThere are some other, more minor problems with this:\r਀ഊ  (1) The dir file (and presumably other info menus) I have was\r਀      昀漀爀洀愀琀琀攀搀 愀猀猀甀洀椀渀最 琀栀愀琀 渀漀 琀攀砀琀 眀漀甀氀搀 戀攀 栀椀搀搀攀渀Ⰰ 猀漀 椀渀 猀漀洀攀 挀愀猀攀猀Ⰰഊ      the invisible text results in a very wierd looking display.\r਀ഊ      Here's an example display from my *info* dir node (these are all\r਀      搀攀戀椀愀渀 攀渀琀爀椀攀猀⤀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊ* CVS		        Concurrent Versions\r਀ऀऀऀऀऀऀ     匀礀猀琀攀洀ഊ* CVS client/server     Describes the\r਀ऀऀऀऀऀऀ     挀氀椀攀渀琀⼀猀攀爀瘀攀爀 瀀爀漀琀漀挀漀氀ഊ						     used by CVS.\r਀⨀ 最挀挀ⴀ㈀㤀㔀ऀऀ吀栀攀 䜀一唀 䌀漀洀瀀椀氀攀爀ഊ						     Collection (Version\r਀ऀऀऀऀऀऀ     ㈀⸀㤀㔀⸀砀⤀⸀ഊ* Gdb			The GNU debugger.\r਀⨀ 䜀搀戀ⴀ䤀渀琀攀爀渀愀氀猀ऀऀ吀栀攀 䜀一唀 搀攀戀甀最最攀爀✀猀ഊ						     internals.\r਀ⴀⴀⴀ  攀渀搀 焀甀漀琀攀  ⴀⴀⴀഊ\r਀      䠀攀爀攀✀猀 琀栀攀 琀攀砀琀 愀猀 椀琀 愀瀀瀀攀愀爀猀 眀椀琀栀漀甀琀 椀渀瘀椀猀椀戀氀攀 爀攀最椀漀渀猀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊ* CVS: (cvs).					     Concurrent Versions\r਀ऀऀऀऀऀऀ     匀礀猀琀攀洀ഊ* CVS client/server: (cvsclient).		     Describes the\r਀ऀऀऀऀऀऀ     挀氀椀攀渀琀⼀猀攀爀瘀攀爀 瀀爀漀琀漀挀漀氀ഊ						     used by CVS.\r਀⨀ 最挀挀ⴀ㈀㤀㔀㨀 ⠀最挀挀ⴀ㈀㤀㔀⤀⸀ऀऀऀऀ     吀栀攀 䜀一唀 䌀漀洀瀀椀氀攀爀ഊ						     Collection (Version\r਀ऀऀऀऀऀऀ     ㈀⸀㤀㔀⸀砀⤀⸀ഊ* Gdb: (gdb).					     The GNU debugger.\r਀⨀ 䜀搀戀ⴀ䤀渀琀攀爀渀愀氀猀㨀 ⠀最搀戀椀渀琀⤀⸀ऀऀऀ     吀栀攀 䜀一唀 搀攀戀甀最最攀爀✀猀ഊ						     internals.\r਀ⴀⴀⴀ  攀渀搀 焀甀漀琀攀  ⴀⴀⴀഊ\r਀      䘀爀漀洀 琀栀攀 愀戀漀瘀攀Ⰰ 椀琀 猀攀攀洀猀 琀栀愀琀 礀漀甀爀 挀栀愀渀最攀 愀氀猀漀 爀攀洀漀瘀攀猀 猀漀洀攀ഊ      whitespace, because just difference can't be accounted for by just\r਀      洀愀欀椀渀最 琀栀攀 渀漀搀攀ⴀ渀愀洀攀 愀渀搀 瀀甀渀挀甀琀愀琀椀漀渀 椀渀瘀椀猀椀戀氀攀⸀ഊ\r਀ഊ  (2) Cursor movement is `wierd' around the invisible text region.  For\r਀      椀渀猀琀愀渀挀攀Ⰰ 琀愀欀椀渀最 漀渀攀 漀昀 琀栀攀 洀攀渀甀 氀椀渀攀猀 昀爀漀洀 愀戀漀瘀攀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊ* gcc-295		The GNU Compiler\r਀ⴀⴀⴀ  攀渀搀 焀甀漀琀攀  ⴀⴀⴀഊ\r਀      眀栀攀渀 䤀 甀猀攀 䌀ⴀ昀 琀漀 洀漀瘀攀 昀漀爀眀愀爀搀 昀爀漀洀 琀栀攀 戀攀最椀渀渀椀渀最 漀昀 琀栀攀 氀椀渀攀Ⰰഊ      everything's OK until point is before the `5'.  If I hit C-f\r਀      琀栀攀渀Ⰰ 瀀漀椀渀琀 樀甀洀瀀猀 琀漀 戀攀椀渀最 戀攀昀漀爀攀 琀栀攀 怀吀✀Ⰰ 眀栀攀渀 䤀 攀砀瀀攀挀琀攀搀 椀琀 琀漀ഊ      move to just after the `5'.  If I then hit C-f again, the cursor\r਀      搀漀攀猀渀✀琀 洀漀瘀攀Ⰰ 怀猀琀椀挀欀椀渀最✀ 愀琀 琀栀攀 瀀漀椀渀琀 戀攀昀漀爀攀 琀栀攀 怀吀✀㬀 愀渀漀琀栀攀爀 䌀ⴀ昀ഊ      then moves forward as expected.\r਀ഊ      I thought these sorts of problems were supposed to be generally\r਀      昀椀砀攀搀 琀栀攀猀攀 搀愀礀猀 ⠀眀攀氀氀Ⰰ 䌀ⴀ渀⼀䌀ⴀ瀀 愀爀攀 猀琀椀氀氀 昀甀挀欀攀搀 䤀 琀栀椀渀欀Ⰰ 戀甀琀ഊ      they're a separate case), so perhaps there's something odd with\r਀      琀栀攀 眀愀礀 礀漀甀✀爀攀 猀攀琀琀椀渀最 甀瀀 礀漀甀爀 椀渀瘀椀猀椀戀氀攀 琀攀砀琀⸀ഊ\r਀ഊ  (3) In the gcc-2.95 info doc, there's a node (`(gcc-295)G++ and GCC')\r਀      琀栀愀琀 挀漀渀琀愀椀渀猀 琀栀攀 昀漀氀氀漀眀椀渀最 琀攀砀琀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊthat you get better object code, and better debugging information.  The\r਀䜀一唀 搀攀戀甀最最攀爀Ⰰ 䜀䐀䈀Ⰰ 眀漀爀欀猀 眀椀琀栀 琀栀椀猀 椀渀昀漀爀洀愀琀椀漀渀 椀渀 琀栀攀 漀戀樀攀挀琀 挀漀搀攀 琀漀ഊgive you comprehensive C++ source-level editing capabilities (*note C\r਀愀渀搀 䌀⬀⬀㨀 ⠀最搀戀⸀椀渀昀漀⤀䌀⸀⤀⸀ഊ---  end quote  ---\r਀ഊ      your *note hack turns it into:\r਀ഊ--- begin quote ---\r਀琀栀愀琀 礀漀甀 最攀琀 戀攀琀琀攀爀 漀戀樀攀挀琀 挀漀搀攀Ⰰ 愀渀搀 戀攀琀琀攀爀 搀攀戀甀最最椀渀最 椀渀昀漀爀洀愀琀椀漀渀⸀  吀栀攀ഊGNU debugger, GDB, works with this information in the object code to\r਀最椀瘀攀 礀漀甀 挀漀洀瀀爀攀栀攀渀猀椀瘀攀 䌀⬀⬀ 猀漀甀爀挀攀ⴀ氀攀瘀攀氀 攀搀椀琀椀渀最 挀愀瀀愀戀椀氀椀琀椀攀猀 ⠀猀攀攀 䌀ഊand C++.info)C.).\r਀ⴀⴀⴀ  攀渀搀 焀甀漀琀攀  ⴀⴀⴀഊ\r਀  ⠀㐀⤀ 吀栀攀 眀爀愀瀀瀀椀渀最 瀀爀漀戀氀攀洀 栀愀瀀瀀攀渀猀 眀椀琀栀 ⨀渀漀琀攀 琀愀最猀 琀漀漀㬀 漀昀琀攀渀 椀琀✀猀 昀愀椀爀氀礀ഊ      benign (a line that's unusually short because of invisible'd text),\r਀      戀甀琀 猀漀洀攀琀椀洀攀猀 椀琀 最攀琀猀 愀 戀椀琀 甀最氀椀攀爀㬀 攀⸀最⸀ 琀栀攀 漀爀椀最椀渀愀氀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊ     order to be compiled,and also requires the header files for the\r਀     琀愀爀最攀琀✀猀 琀栀爀攀愀搀 氀椀戀爀愀爀礀 椀昀 礀漀甀 眀愀渀琀 琀栀爀攀愀搀 猀甀瀀瀀漀爀琀⸀  ⨀一漀琀攀ഊ     Cross-Compilers and Header Files: Cross Headers, for discussion\r਀     愀戀漀甀琀 栀攀愀搀攀爀 昀椀氀攀猀 椀猀猀甀攀猀 昀漀爀 挀爀漀猀猀ⴀ挀漀洀瀀椀氀愀琀椀漀渀⸀ഊ---  end quote  ---\r਀ഊ      turns into [note the wrapped line]:\r਀ഊ--- begin quote ---\r਀     漀爀搀攀爀 琀漀 戀攀 挀漀洀瀀椀氀攀搀Ⰰ愀渀搀 愀氀猀漀 爀攀焀甀椀爀攀猀 琀栀攀 栀攀愀搀攀爀 昀椀氀攀猀 昀漀爀 琀栀攀ഊ     target's thread library if you want thread support.  See Cross-Compilers and Header Files, for discussion\r਀     愀戀漀甀琀 栀攀愀搀攀爀 昀椀氀攀猀 椀猀猀甀攀猀 昀漀爀 挀爀漀猀猀ⴀ挀漀洀瀀椀氀愀琀椀漀渀⸀ഊ---  end quote  ---\r਀ഊ  (5) Cursor movement around the `See' is wierd, but I guess that's\r਀      猀漀洀攀琀栀椀渀最 礀漀甀 挀愀渀 搀漀 洀甀挀栀 愀戀漀甀琀⸀ഊ\r਀  ⠀㘀⤀ 䄀栀Ⰰ 䤀 樀甀猀琀 猀愀眀 愀渀漀琀栀攀爀 洀椀猀昀漀爀洀愀琀琀攀搀 洀攀渀甀 攀渀琀爀礀㬀 琀栀攀 漀爀椀最椀渀愀氀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊ* gcc-3.2: (gcc-3.2).				     The GNU Compiler\r਀ऀऀऀऀऀऀ     䌀漀氀氀攀挀琀椀漀渀 ⠀嘀攀爀猀椀漀渀 ㌀⸀㈀⤀⸀ഊ* gccint-3.2: (gccint-3.2).			     Internals of the GNU\r਀ऀऀऀऀऀऀ     䌀漀洀瀀椀氀攀爀 䌀漀氀氀攀挀琀椀漀渀ഊ						     (Version 3.2).\r਀ⴀⴀⴀ  攀渀搀 焀甀漀琀攀  ⴀⴀⴀഊ\r਀      琀甀爀渀猀 椀渀琀漀㨀ഊ\r਀ⴀⴀⴀ 戀攀最椀渀 焀甀漀琀攀 ⴀⴀⴀഊ* gcc-3.2		2).				     The GNU Compiler\r਀ऀऀऀऀऀऀ     䌀漀氀氀攀挀琀椀漀渀 ⠀嘀攀爀猀椀漀渀 ㌀⸀㈀⤀⸀ഊ* gccint-3.2		2).			     Internals of the GNU\r਀ऀऀऀऀऀऀ     䌀漀洀瀀椀氀攀爀 䌀漀氀氀攀挀琀椀漀渀ഊ						     (Version 3.2).\r਀ⴀⴀⴀ  攀渀搀 焀甀漀琀攀  ⴀⴀⴀഊ\r਀ഊAnyway, I basically like it, it's noticably easier to read than the old\r਀猀琀礀氀攀⸀ഊ\r਀ⴀ䴀椀氀攀猀ഊ-- \r਀嬀簀渀甀爀最氀攀簀崀  搀搀琀ⴀ 搀攀洀漀渀椀挀㼀 猀漀 焀甀愀欀攀 眀椀氀氀 栀愀瘀攀 愀渀 攀瘀椀氀 欀椀渀搀愀 猀攀琀琀椀渀最㼀 漀渀攀 琀栀愀琀 ഊ            will  make every christian in the world foamm at the mouth? \r਀嬀椀搀搀琀崀      渀甀爀最Ⰰ 琀栀愀琀✀猀 琀栀攀 最漀愀氀 ഊ

             reply	other threads:[~2002-11-01  8:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  8:04 Miles Bader [this message]
     [not found] ` <200211011623.gA1GNAL03601@rum.cs.yale.edu>
2002-11-05  4:08   ` info invisible changes Miles Bader
2002-11-05 18:49     ` Stefan Monnier
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=buoy98dhg1n.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=miles@gnu.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.
Code repositories for project(s) associated with this public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).