From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org, karl@freefriends.org
Subject: Re: 3 dots vanish at end of filled line
Date: Fri, 7 Oct 2005 21:54:40 -0500 (CDT) [thread overview]
Message-ID: <200510080254.j982seR17582@raven.dms.auburn.edu> (raw)
In-Reply-To: <874q7tgdh9.fsf@jurta.org> (message from Juri Linkov on Sat, 08 Oct 2005 00:47:54 +0300)
>From my previous message:
If so, then I think it is safe to fix that in a way of
comparing their lengths before highlighting.
That is _still_ a very unreliable heuristic.
For instance, in Bob's example file foo.texi, after the:
Here are three dots with the @@dots@{@} on a filled line xxxxxxxxxxxxx
@dots{}
Paste in the extra text (separated by blank lines):
@verbatim
*****
*BOX*
*****
@end verbatim
run makeinfo on it and see how horribly badly this gets displayed in
`emacs -Q -nbc'
Not only is the ending ***** line not displayed, the *BOX* line in
displayed in a ridiculously large font. The displayed stuff does not
even remotely resemble the intended box. I do not believe that the
"fix" you proposed fixes this.
The standalone info gets this completely correct. I also get it
correct with my .emacs file, which solidly corrects these types of
bugs in info.el (both the bugs in font and invisibility).
Sincerely,
Luc.
next prev parent reply other threads:[~2005-10-08 2:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:32 3 dots vanish at end of filled line Karl Berry
2005-10-07 21:12 ` Juri Linkov
2005-10-07 21:21 ` Karl Berry
2005-10-07 21:47 ` Juri Linkov
2005-10-07 23:12 ` Karl Berry
2005-10-07 23:56 ` Luc Teirlinck
2005-10-08 2:54 ` Luc Teirlinck [this message]
2005-10-08 22:57 ` Richard M. Stallman
2005-10-09 0:14 ` Karl Berry
2005-10-09 0:57 ` Luc Teirlinck
2005-10-09 6:11 ` Juri Linkov
2005-10-09 17:17 ` Karl Berry
2005-10-09 19:16 ` Luc Teirlinck
2005-10-10 15:00 ` Stefan Monnier
2005-10-10 17:07 ` Karl Berry
2005-10-10 18:01 ` Stefan Monnier
2005-10-11 14:46 ` Richard M. Stallman
2005-10-11 17:06 ` Stefan Monnier
2005-10-10 23:48 ` Richard M. Stallman
2005-10-10 23:48 ` Richard M. Stallman
2005-10-11 2:18 ` Luc Teirlinck
2005-10-11 3:31 ` Luc Teirlinck
2005-10-11 22:42 ` Richard M. Stallman
2005-10-12 0:21 ` Luc Teirlinck
2005-10-12 19:47 ` Stefan Monnier
2005-10-13 20:10 ` Richard M. Stallman
2005-10-28 4:41 ` KOBAYASHI Yasuhiro
2005-10-10 6:18 ` Juri Linkov
2005-10-09 19:54 ` Luc Teirlinck
2005-10-10 4:14 ` Richard M. Stallman
2005-10-10 15:02 ` Stefan Monnier
2005-10-10 23:47 ` Richard M. Stallman
2005-10-09 11:09 ` Robert J. Chassell
2005-10-10 4:14 ` Richard M. Stallman
2005-10-10 12:21 ` Robert J. Chassell
2005-10-10 23:47 ` Richard M. Stallman
2005-10-11 12:57 ` Robert J. Chassell
2005-10-20 11:11 ` Juri Linkov
2005-10-20 23:38 ` Richard M. Stallman
2005-10-21 11:55 ` Juri Linkov
2005-10-21 22:19 ` Richard M. Stallman
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=200510080254.j982seR17582@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=karl@freefriends.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).