unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: Should invisible imply intangible?
Date: Thu, 28 Feb 2002 20:30:13 -0500	[thread overview]
Message-ID: <200203010130.g211UDG05790@rum.cs.yale.edu> (raw)
In-Reply-To: 200202262013.g1QKDef16683@aztec.santafe.edu

>     > Is there any practical use for text which is invisible but not
>     > intangible?
> 
>     Yes.  Check out lisp/reveal.el (aka reveal-mode) 
> 
> Ok, I am convinced.  But what do you think of the view that invisible
> should imply intangible unless something like reveal.el is used?
> We could have a flag which says whether invisible implies intangible.
> It could default to t, and reveal-mode could set it to nil.

But reveal.el does not apply to all invisible text in a buffer.
Only to the text that's made invisible by an overlay and only if
the invisibility spec says that it should be replaced by an ellipsis.

Also, as David Kastrup has mentioned repeatedly, intangible text tends
to break lots of things, so we probably want to use something else.
For example: automatically move point to a visible area after each command
(and after post-command-hook, of course) or during redisplay (I believe
there is already such a feature for text with a `display' property).

The current intangibility which moves point to a tangible area for
each and every point motion tends to be too intrusive.

I think that a "move to visible, after post-command-hook" or something
like that might be appropriate.  And it wouldn't conflict with reveal.el
(although it could still conflict if reveal.el was changed to use an idle
timer rather than post-command-hook).


	Stefan


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-01  1:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23 20:19 Should invisible imply intangible? Richard Stallman
2002-02-23 21:24 ` Paul Michael Reilly
2002-02-25  0:09   ` Richard Stallman
2002-02-25  5:10 ` Stefan Monnier
2002-02-26 20:13   ` Richard Stallman
2002-03-01  1:30     ` Stefan Monnier [this message]
2002-03-03 14:40       ` Richard Stallman
2002-03-03 17:11         ` Stefan Monnier
2002-03-04 23:41           ` Richard Stallman
2002-03-04 23:46             ` Stefan Monnier
2002-03-05  1:40             ` Stefan Monnier
2002-03-07  2:30               ` Richard Stallman
2002-03-04 23:41           ` Richard Stallman
2002-03-05 21:58             ` Richard Stallman
2002-03-05 23:04               ` Stefan Monnier
2002-03-05 23:34                 ` Stefan Monnier
2002-03-09 20:03                 ` Richard Stallman
2002-03-09 22:37                   ` Stefan Monnier
2002-03-10 21:32                     ` Richard Stallman
     [not found]                       ` <200203102202.g2AM26q06798@rum.cs.yale.edu>
2002-03-11 19:06                         ` Richard Stallman
2002-03-12 17:56                           ` Stefan Monnier
2002-03-13 10:58                             ` Richard Stallman
2002-03-13 11:19                               ` David Kastrup
2002-03-15  3:41                                 ` Richard Stallman
2002-03-15 11:47                                   ` David Kastrup
2002-03-16  6:39                                     ` Richard Stallman
2002-03-16 11:58                                       ` David Kastrup
2002-03-18  9:06                                         ` Richard Stallman
2002-03-18 23:36                                           ` David Kastrup
2002-03-19  7:24                                             ` Eli Zaretskii
2002-03-19 11:12                                               ` David Kastrup
2002-03-16  0:22                                   ` Stefan Monnier
2002-03-16  0:56                                     ` Miles Bader
2002-03-16  0:59                                       ` Stefan Monnier
2002-03-16  1:25                                         ` David Kastrup
2002-03-17 10:06                                         ` Richard Stallman
2002-03-16  1:18                                     ` David Kastrup
2002-03-16  1:28                                       ` Stefan Monnier
2002-03-16  2:16                                         ` David Kastrup
2002-03-16  3:29                                         ` Miles Bader
2002-03-16  4:05                                           ` David Kastrup
2002-03-23 23:37                                         ` David Kastrup
2002-03-13 13:06                               ` Stefan Monnier
2002-03-13 14:15                                 ` David Kastrup
2002-03-13 16:53                                   ` Stefan Monnier
2002-03-14 12:42                                   ` 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=200203010130.g211UDG05790@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --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).