From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: jas@extundo.com
Subject: Re: Problems with info (emacs version)
Date: Tue, 3 Jun 2003 11:24:16 -0500 (CDT) [thread overview]
Message-ID: <200306031624.h53GOG424960@eel.dms.auburn.edu> (raw)
In-Reply-To: <x5adcz43cl.fsf@lola.goethe.zz> (David.Kastrup@t-online.de)
I believe this discussion has gotten too much into the nitty-gritty
details of the problems involved and not focused enough on the
underlying common cause for all these problems and the general
solution, which I believe is not that difficult.
I believe that there are appropriate and inappropriate uses for the
invisibility and display properties. If you use them in an
inappropriate way all the reported problems, as well as countless
others, appear. If you use them appropriately they do not, or at
least only in a way less severe fashion.
The following represents my personal opinion:
Invisibility property:
Appropriate:
In a long text, sometimes you want to focus on the details and
sometimes you want to get an overview. Give the details the
invisibility property (or various invisibility properties
corresponding to various level of detail) and provide user commands to
toggle invisibility.
Inappropriate:
Using the invisibility properties for internal Emacs purposes. As the
various problems I reported show, there is nothing "internal" about
the invisibility property.
Conclusion:
Always use the invisibility property as a user feature, never as an
internal feature. Always make sure that the user knows about
invisible text. Always provide convenient commands to toggle
invisibility.
Display property:
Appropriate:
>From the Elisp manual:
`display' This property activates various features that change the way
text is displayed. For example, it can make text appear taller
or shorter, higher or lower, wider or narrow, or replaced with an
image.
Inappropriate:
As a way to make text impossible to see, without making it invisible,
by displaying it as whitespace (as info does extensively), or, more
generally, as a way to display regular text as some other regular text
with unrelated content, as an alternative for such lowly tools,
typically used by the unsophisticated masses, as deletion and
insertion.
The solution I propose for info is not that difficult:
1. Replace the pseudo-invisible text with text having the
invisibility property (see Stefan's proposal earlier in this
thread for more details).
2. Provide a command in info, say `v' that toggles visibility.
make sure the user knows about it.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-06-03 16:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 3:33 Problems with info (emacs version) Luc Teirlinck
2003-06-02 4:29 ` Eli Zaretskii
2003-06-02 6:51 ` Kenichi Handa
2003-06-03 4:06 ` Richard Stallman
2003-06-03 4:18 ` Luc Teirlinck
2003-06-02 17:17 ` Stefan Monnier
2003-06-02 18:23 ` Luc Teirlinck
2003-06-03 4:06 ` Richard Stallman
2003-06-03 4:45 ` Luc Teirlinck
2003-06-03 18:03 ` Robert J. Chassell
2003-06-03 18:38 ` Luc Teirlinck
2003-06-03 5:22 ` Luc Teirlinck
2003-06-03 5:58 ` Simon Josefsson
2003-06-03 6:07 ` Miles Bader
2003-06-03 6:35 ` Simon Josefsson
2003-06-03 6:46 ` Miles Bader
2003-06-03 19:15 ` Simon Josefsson
2003-06-03 19:25 ` Miles Bader
2003-06-03 19:46 ` Simon Josefsson
2003-06-03 19:58 ` Luc Teirlinck
2003-06-03 20:05 ` Simon Josefsson
2003-06-03 23:26 ` Miles Bader
2003-06-03 13:49 ` Luc Teirlinck
2003-06-03 14:56 ` David Kastrup
2003-06-03 16:23 ` Stefan Monnier
2003-06-03 16:24 ` Luc Teirlinck [this message]
2003-06-05 0:08 ` Richard Stallman
2003-06-03 16:45 ` Luc Teirlinck
2003-06-03 19:23 ` Simon Josefsson
2003-06-03 19:40 ` Luc Teirlinck
2003-06-05 0:07 ` Richard Stallman
2003-06-03 14:07 ` Luc Teirlinck
2003-06-03 18:11 ` Robert J. Chassell
2003-06-04 8:53 ` Richard Stallman
2003-06-04 18:05 ` Luc Teirlinck
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=200306031624.h53GOG424960@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=jas@extundo.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 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.