From: "Drew Adams" <drew.adams@oracle.com>
Cc: Juri Linkov <juri@jurta.org>,
bob@rattlesnake.com, Eli Zaretskii <eliz@gnu.org>,
Alex Schroeder <alex@emacswiki.org>
Subject: RE: [Emacs-trunk-diffs] Changes to emacs/lisp/faces.el
Date: Thu, 30 Dec 2004 08:33:34 -0800 [thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBGELJCKAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87vfajamtq.fsf@confusibombus.emacswiki.org>
>> By contrast, people do not want ^L to stand out like comments do.
> Do people want ^L highlighted at all?
I would like there to be something telling me the difference between
the two ASCII characters ^L and the corresponding control character.
In some text buffers, it might be appropriate to have ^L displayed as, say,
a horizontal line (dotted or otherwise) to indicate a page boundary - as in
some word processors. Such a disply option should be just that: an option,
in any case.
In other kinds of buffers, where ^L does not signify a page boundary, such a
display option would not be appropriate.
next prev parent reply other threads:[~2004-12-30 16:33 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CZoXW-0007hE-UW@lists.gnu.org>
[not found] ` <E1Ca4Kt-00067g-EH@fencepost.gnu.org>
2004-12-03 9:18 ` [Emacs-trunk-diffs] Changes to emacs/lisp/faces.el Kim F. Storm
2004-12-04 2:48 ` Richard Stallman
2004-12-05 17:52 ` Juri Linkov
2004-12-05 18:32 ` Daniel Pfeiffer
2004-12-06 1:40 ` Richard Stallman
2004-12-07 22:40 ` Daniel Pfeiffer
2004-12-07 23:48 ` Stefan Monnier
2004-12-08 8:47 ` Daniel Pfeiffer
2004-12-08 15:16 ` Stefan Monnier
2004-12-08 22:15 ` Richard Stallman
2004-12-08 22:15 ` Richard Stallman
2004-12-12 9:19 ` Daniel Pfeiffer
2004-12-13 9:03 ` Juri Linkov
2004-12-13 14:51 ` Stefan Monnier
2004-12-13 19:51 ` Richard Stallman
2004-12-13 23:41 ` Daniel Pfeiffer
2004-12-14 23:22 ` Richard Stallman
2004-12-17 0:54 ` Richard Stallman
2004-12-19 9:41 ` Daniel Pfeiffer
2004-12-21 11:21 ` Richard Stallman
2004-12-23 20:39 ` Daniel Pfeiffer
2004-12-14 12:32 ` Kim F. Storm
2004-12-15 10:56 ` Juri Linkov
2004-12-15 11:21 ` Kim F. Storm
2004-12-15 12:01 ` Robert J. Chassell
2004-12-15 14:58 ` Richard Stallman
2004-12-15 16:14 ` Kim F. Storm
2004-12-15 20:35 ` Daniel Pfeiffer
2004-12-24 2:28 ` Juri Linkov
2004-12-24 13:26 ` Robert J. Chassell
2004-12-26 19:42 ` Juri Linkov
2004-12-27 8:00 ` Eli Zaretskii
2004-12-27 19:53 ` Juri Linkov
2004-12-27 22:01 ` Eli Zaretskii
2004-12-27 22:56 ` Stefan Monnier
2004-12-28 17:25 ` Richard Stallman
2004-12-28 2:38 ` Juri Linkov
2004-12-28 4:47 ` Eli Zaretskii
2004-12-28 7:52 ` Juri Linkov
2004-12-28 20:36 ` Eli Zaretskii
2004-12-29 0:22 ` Juri Linkov
2004-12-29 4:45 ` Eli Zaretskii
2004-12-30 7:33 ` Juri Linkov
2004-12-30 14:21 ` Alex Schroeder
2004-12-30 16:33 ` Drew Adams [this message]
2004-12-30 20:59 ` Richard Stallman
2004-12-28 4:57 ` Richard Stallman
2004-12-25 15:12 ` 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=FDELKNEBLPKKDCEBEJCBGELJCKAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=alex@emacswiki.org \
--cc=bob@rattlesnake.com \
--cc=eliz@gnu.org \
--cc=juri@jurta.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).