unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Avoiding moving point into minibuffer prompt area
Date: Tue, 16 Aug 2005 20:05:04 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICOEMICLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200508161912.j7GJCGS01998@raven.dms.auburn.edu>

On a related subject, and being a bit nit-picky - does anyone else think
that these things should be harmonized & better documented?

 - Neither the Emacs manual nor the Emacs-Lisp manual contains the word
"inviolable".

 - Both manuals refer to the "intangible" property.

 - Is "intangible" not the same property as what Customize refers to as
"inviolable"? More precisely, isn't the "intangible" property what makes the
minibuffer-prompt area "inviolable"?

 - If so, wouldn't it be better to stick to the same term, whichever we
choose? Especially since "inviolable" conveys no more meaning to the
uninitiated than "intangible" - nothing is gained by using it, except
another layer of obfuscation.

Of the two terms, "intangible" is more accurate, IMO.

Someone will perhaps reply that "inviolable" applies to the
minibuffer-prompt area, indicating that it cannot be entered ("violated"),
while "intangible" is the corresponding text property of that area. Even so,
I think more would be gained by using the same term ("intangible") in
Customize. That would help users make the link with all of the doc that
describes the characteristics of the "intangible" property.

  parent reply	other threads:[~2005-08-17  3:05 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  1:29 Avoiding moving point into minibuffer prompt area Lennart Borgman
2005-08-16  1:53 ` Luc Teirlinck
2005-08-16  4:07   ` Drew Adams
2005-08-16  5:10     ` Luc Teirlinck
2005-08-16 14:23       ` Drew Adams
2005-08-16 14:49         ` Luc Teirlinck
2005-08-16  5:15     ` Luc Teirlinck
2005-08-16  4:13 ` Luc Teirlinck
2005-08-16  4:51   ` Drew Adams
2005-08-16 16:34     ` David Reitter
2005-08-16 17:57       ` Luc Teirlinck
2005-08-16 18:27         ` Lennart Borgman
2005-08-16 19:12           ` Luc Teirlinck
2005-08-16 21:54             ` Lennart Borgman
2005-08-16 22:09               ` Luc Teirlinck
2005-08-16 22:29                 ` Lennart Borgman
2005-08-17  3:05             ` Drew Adams [this message]
2005-08-17  3:53               ` Luc Teirlinck
2005-08-17  3:59               ` Luc Teirlinck
2005-08-17 15:52               ` Richard M. Stallman
2005-08-18  5:44                 ` Drew Adams
2005-08-16 21:34         ` David Reitter
2005-08-16 19:52     ` Randal L. Schwartz
2005-08-17  3:07       ` Drew Adams
2005-08-17  3:13         ` Randal L. Schwartz
2005-08-17  3:17           ` Drew Adams
2005-08-16 20:43     ` Richard M. Stallman
2005-08-16  9:04   ` Lennart Borgman
2005-08-16  9:59     ` Juri Linkov
2005-08-16 10:49       ` Lennart Borgman
2005-08-16 11:27         ` Juri Linkov
2005-08-16 11:46           ` Lennart Borgman
2005-08-16 20:43         ` Richard M. Stallman
2005-08-16 22:15           ` Lennart Borgman
2005-08-17 15:51             ` Richard M. Stallman
2005-08-17 16:12               ` Lennart Borgman
2005-08-18 21:15                 ` Richard M. Stallman
2005-08-18 22:46                   ` Lennart Borgman
2005-08-19 23:07                     ` Richard M. Stallman
2005-08-19 23:55                       ` Lennart Borgman
2005-08-22  5:01                         ` Richard M. Stallman
2005-08-22  5:02                         ` Richard M. Stallman
2005-08-16 20:43       ` Richard M. Stallman
2005-08-16 13:57     ` Luc Teirlinck
2005-08-16 14:15       ` Lennart Borgman
2005-08-16 18:29 ` Richard M. Stallman
2005-08-17  9:01   ` Emilio Lopes
2005-08-17 11:14     ` Lennart Borgman

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=DNEMKBNJBGPAOPIJOOICOEMICLAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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 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).