unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: juri@jurta.org, emacs-devel@gnu.org, karl@freefriends.org
Subject: Re: 3 dots vanish at end of filled line
Date: Tue, 11 Oct 2005 08:57:05 -0400 (EDT)	[thread overview]
Message-ID: <m1EPJgn-0004SIC@rattlesnake.com> (raw)
In-Reply-To: <E1EP7Mr-0003C2-N0@fencepost.gnu.org> (rms@gnu.org)

   One idea that occurs to me is that you should write `@enddots{.}',
   with a period in the argument.  

Using Texinfo 4.8, that looks fine in *info*, but not in DVI as viewed
with xpdf.

In DVI, there is less space between the last two dots (dots two and
three of the ellipsis) than the period and the first dot of the
ellipsis and between dots one and two of the ellipsis.  (I did not
expect this!  It looks to me to be a side effect of the \hfil in the
@dots{} command from which @enddots{} is derived.)

In Texinfo. 

    Without space, but with a period between braces, @@enddots@{.@}, and
    some more words to push everything over@enddots{.}  And then more
    words.

In Info:

    Without space, but with a period between braces, @enddots{.}, and
    some more words to push everything over.....  And then more words.

In DVI (except the width difference is less than shown here):

    Without space, but with a period between braces, @enddots{.}, and
    some more words to push everything over. . . ..  And then more words.

As is, M-e and M-a work successfully both with Texinfo and with Info.

Unless the bug with TeX output is fixed, the suggestion cannot be used.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  reply	other threads:[~2005-10-11 12:57 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
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 [this message]
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=m1EPJgn-0004SIC@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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).