From: storm@cua.dk (Kim F. Storm)
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: 06 Nov 2002 00:57:50 +0100 [thread overview]
Message-ID: <5xznsnvabl.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <buowunsirq5.fsf@mcspd15.ucom.lsi.nec.co.jp>
Miles Bader <miles@lsi.nec.co.jp> writes:
> It does look nicer (cleaner), but there are some problems:
Thanks for reporting those problems; I have tried to fix some of them
as described below.
>
> When I do `Memacs' from the top-level dir (with point at the beginning
> of the buffer), I get the following error:
I cannot reproduce this with the lastest CVS. I think Stefan fixed it.
>
> 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.
> * CVS client/server Describes the
> client/server protocol
> used by CVS.
I have added code to properly align (+2 spaces) the following description
lines. Please try it out.
>
> (2) Cursor movement is `wierd' around the invisible text region. For
> instance, taking one of the menu lines from above:
Indeed. However, I'm definitely not going to hack on the display
engine to improve this [minor] issue.
BTW, try turning on M-x line-number-mode and M-x column-number-mode
and what what happens as you move through invisible text with embedded
newlines :-(
>
> (3) In the gcc-2.95 info doc, there's a node (`(gcc-295)G++ and GCC')
> that contains the following text:
>
> and C++: (gdb.info)C.).
> and C++.info)C.).
I've fixed that.
> (4) The wrapping problem happens with *note tags too; often it's fairly
> benign (a line that's unusually short because of invisible'd text),
Yes, but as you'd see by turning on column-number-mode, there is no
easy way to decide what column a given character is displayed at [of
if there is, please enlighten me]. So it is really difficult to try
to improve this "locally".
As Stefan suggested we could refill the text, but then we start
modifying the text in the info buffer - and I'm not sure what the
implications of doing that are.
Also, how do we know what part of the text is safe to refill.
So for the moment, I don't see how we can easily get rid of those
short lines.
> but sometimes it gets a bit uglier; e.g. the original:
> target's thread library if you want thread support. *Note
> Cross-Compilers and Header Files: Cross Headers, for discussion
> target's thread library if you want thread support. See Cross-Compilers and Header Files, for discussion
I've fixed that (inserting a newline if the hidden text contains one),
but unfortunately this means that you'll see more short lines in some
places.
> (5) Cursor movement around the `See' is wierd, but I guess that's
> something you can do much about.
No, I don't think so...
> (6) Ah, I just saw another misformatted menu entry; the original:
>
> * gcc-3.2: (gcc-3.2). The GNU Compiler
> * gcc-3.2 2). The GNU Compiler
I've fixed that too.
> Anyway, I basically like it, it's noticably easier to read than the old
> style.
Thanks! I think so too, but not everyone was pleased with the
change, so I had to make it customizable...
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-11-05 23:57 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
2002-11-07 4:49 ` Richard Stallman
2002-11-05 23:57 ` Kim F. Storm [this message]
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=5xznsnvabl.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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 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).