From: "Lennart Borgman" <lennart.borgman@gmail.com>
To: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Editing of invisible text
Date: Sun, 26 Oct 2008 14:32:10 +0100 [thread overview]
Message-ID: <e01d8a50810260632k73eaab70re364362b3f62845d@mail.gmail.com> (raw)
Emacs lets you edit invisible text. That is perhaps not bad, but it is
bad that you can't see what you are doing when you are editing
invisible text. Here is a suggestion on how to make this better:
- Implement a minor mode that make all invisible text visible but with
a special face (or background color) that tells the user this is
really invisible text.
- Ask the user if she/he want to turn on this minor mode for the
buffer when invisible text is going to be changed.
- Of course add a variable to override this behaviour when needed ;-)
next reply other threads:[~2008-10-26 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 13:32 Lennart Borgman [this message]
2008-10-27 2:22 ` Editing of invisible text Stefan Monnier
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=e01d8a50810260632k73eaab70re364362b3f62845d@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.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).