unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: bob@rattlesnake.com
Subject: 3 dots vanish at end of filled line
Date: Fri, 7 Oct 2005 15:32:41 -0500	[thread overview]
Message-ID: <200510072032.j97KWfc08666@f7.net> (raw)

Bob sent me this bug report for the current CVS version of Emacs about
three dots disappearing in the Info display (they are present in the
actual .info file).  It doesn't happen in 21.3.

Can someone look at it, please?

Thanks,
Karl


Date: Fri, 7 Oct 2005 19:28:29 +0000 (UTC)
From: "Robert J. Chassell" <bob@rattlesnake.com>
To: karl@freefriends.org
Subject: 3 dots vanish at end of filled line

Today's GNU Emacs CVS snapshot, Fri, 2005 Oct  7  13:53 UTC
GNU Emacs 22.0.50.103 (i686-pc-linux-gnu, GTK+ Version 2.6.10) 
started with

     /usr/local/src/emacs/src/emacs -Q -D

and using   texinfo-4.8

The bug:  in *info* the three dots of the @dots{} comand, when the
@dots{} comand just happens to fall on a line of its own when the
previous line is filled, does not show the three dots.  


Thus, in *info*

    Here are three dots ...

    Here are three dots with the @dots{} on a filled line xxxxxxxxxxxxx

    Contents of chapter 1.


but the three dots appear when the line is copied from the *info* file
...

(on a line of its own, as shown).

The DVI, as seen by xdvi, is OK. 


Here is a test file:


\input /usr/local/src/texinfo-4.8/doc/texinfo.tex  @c -*-texinfo-*-
@comment %**start of header
@setfilename foo.info
@settitle Texinfo Test
@smallbook
@comment %**end of header

@ignore

 ## Summary of shell commands to create various output formats:

    pushd /u/texinfo/

    ## Info output
    makeinfo --force --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose foo.texi

    ## ;; (kill-buffer "*info*")
    ## ;; (info "/u/texinfo/foo.info" nil)

    ## DVI output
    texi2dvi foo.texi

    ## View DVI output
    ##     xdvi foo.dvi &

    ## HTML output
    makeinfo --no-split --html foo.texi

    ## Plain text output
    makeinfo --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose --no-headers --output=foo.txt  \
    foo.texi

    ## DocBook output
    makeinfo --docbook --no-split --paragraph-indent=0 \
    --verbose foo.texi

    ## XML output
    makeinfo --xml --no-split --paragraph-indent=0 \
    --verbose foo.texi

    popd 

@end ignore

@titlepage
@sp 6
@center @titlefont{Test document}
@sp 4
@center by Robert J. Chassell

@page
@vskip 0pt plus 1filll
@end titlepage

@contents

@ifnottex
@node Top, Chapter One, (dir), (dir)
@top Test Top
@end ifnottex

@menu
* Chapter One::                 
@end menu

@node Chapter One
@chapter Chapter One

Jared Diamond@footnote{@cite{Collapse:@* How Societies Choose to Fail or
Succeed},@*
Jared Diamond,@*
2005, Viking,@*
ISBN 0-670-03337-5} has written a book, @cite{Collapse: How Societies
Choose to Fail or Succeed}, on this theme.  Before publishing his
book, in March 2003, he asked why societies can make disastrous
decisions?  (See
@url{http://www.edge.org/@/documents/@/archive/@/edge114.html}.)

Here are three dots @dots{}

Here are three dots with the @@dots@{@} on a filled line xxxxxxxxxxxxx
@dots{}

More contents of chapter 1.

@bye

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

             reply	other threads:[~2005-10-07 20:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 20:32 Karl Berry [this message]
2005-10-07 21:12 ` 3 dots vanish at end of filled line 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
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=200510072032.j97KWfc08666@f7.net \
    --to=karl@freefriends.org \
    --cc=bob@rattlesnake.com \
    /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).