From: Ben North <ben@redfrontdoor.org>
Subject: Doc fix: display.texi: "truncation" vs "continuation"
Date: Mon, 15 Nov 2004 17:28:22 +0000 [thread overview]
Message-ID: <1100539702.4198e736743e2@imp.hosting365.ie> (raw)
Hi,
Should the following tiny fix be applied to lispref/display.texi
(diff'ed wrt the HEAD revision 1.132)?
--- display.texi 2004-11-15 17:21:17.265004000 +0000
+++ NEW--display.texi 2004-11-15 17:22:13.795002000 +0000
@@ -4460,7 +4460,7 @@
@item 1
The glyph for the end of a continued line (the default is @samp{\}).
Newer Emacs versions, on some platforms, display curved arrows to
-indicate truncation---the display table has no effect in these
+indicate continuation---the display table has no effect in these
situations.
@item 2
The glyph for indicating a character displayed as an octal character
next reply other threads:[~2004-11-15 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 17:28 Ben North [this message]
2004-11-17 5:03 ` Doc fix: display.texi: "truncation" vs "continuation" Richard 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=1100539702.4198e736743e2@imp.hosting365.ie \
--to=ben@redfrontdoor.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).