From: David.Kastrup@t-online.de (David Kastrup)
Cc: emacs-devel@gnu.org
Subject: Re: Proposed new minor mode
Date: 07 Jun 2003 12:47:51 +0200 [thread overview]
Message-ID: <x5smqmjh9k.fsf@lola.goethe.zz> (raw)
In-Reply-To: <200306071030.h57AUwl29375@eel.dms.auburn.edu>
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Eli Zaretskii wrote:
>
> Let the users who need this type "M-x vis-mode-disable RET" or
> some such.
>
> Whether we need a binding for this or not is a different matter.
> But it would seem (given the current implementation) that every
> user, even, or I would say especially, a novice user, would need to
> use the command at least once (actually twice, because it needs to
> be disabled again), because otherwise the confusion when killing and
> yanking, printing part of the buffer, using commands like M-x man
> and the like, is going to be too big.
The surprise is not ameliorated by the availability of a command
toggling some visibility. The novice user caught by surprise will not
think "Oh, I should have called vis-mode-disable in order not get
this".
> The user needs to be aware the text is there, because sooner or
> later he is going to be confronted with it.
And then he will get aware of it.
> If the text were erased, instead of being made invisible, that would
> be a different matter, but that is not how it is currently
> implemented. I do not know of any plans to implement it that way.
Strange. I think I read the contention several times that it would
be a good idea to edit the buffer, making the text better match the
appearance.
> Killing and yanking are not just commands for advanced users and
> there are plenty of reasons to kill and yank text from info buffers.
Sure, but if we have an inconsistency there, the solution is to fix it
instead of providing a command nobody would ever think of using,
because it only uglifies the current buffer and does not cause
anything different to be yanked to the destination buffer.
It won't do a harm to have such a mode for debugging info files and
their display, and other invisibility matters, but it would be an
illusion to think that it would be of major interest to novices, or
help them much.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-06-07 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 1:51 Proposed new minor mode Luc Teirlinck
2003-06-07 1:57 ` Luc Teirlinck
2003-06-07 6:55 ` David Kastrup
2003-06-07 9:13 ` Eli Zaretskii
2003-06-07 10:30 ` Luc Teirlinck
2003-06-07 10:47 ` David Kastrup [this message]
2003-06-07 11:59 ` Luc Teirlinck
2003-06-07 13:52 ` { SPAM 2 }::Re: " Luc Teirlinck
2003-06-07 9:52 ` Luc Teirlinck
2003-06-07 12:20 ` Miles Bader
2003-06-07 9:11 ` Eli Zaretskii
2003-06-07 9:45 ` Luc Teirlinck
2003-06-08 1:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5smqmjh9k.fsf@lola.goethe.zz \
--to=david.kastrup@t-online.de \
--cc=dak@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.