all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: invisible text and point
Date: Mon, 26 May 2003 22:07:27 -0500 (CDT)	[thread overview]
Message-ID: <200305270307.h4R37RM15873@eel.dms.auburn.edu> (raw)
In-Reply-To: <200305270213.h4R2DpP15774@eel.dms.auburn.edu> (message from Luc Teirlinck on Mon, 26 May 2003 21:13:51 -0500 (CDT))

Maybe extremely naive question, but what would be the harm in actually
showing all that invisible and visible-but-you-just-can-not-see-it
text to the user to begin with?  It would take care of all these
problems.  (Except for the infinite loops which are a different
problem and need to be addressed regardless.)  Another confusing thing
about the display property is that the involved string of text remains
impossible to see (to avoid the term invisible) when yanked inside
emacs, but all of a sudden appears out of nowhere when yanked into,
say, an xterm?  On the other hand the "really invisible" text becomes
also visible (by default) when yanked inside emacs, adding to the
confusion.

Some of the hidden text is actually informative.

Sincerely,

Luc.

  reply	other threads:[~2003-05-27  3:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26  4:37 invisible text and point Luc Teirlinck
2003-05-26  4:53 ` Luc Teirlinck
2003-05-26  5:03 ` Luc Teirlinck
2003-05-26  5:16   ` Luc Teirlinck
2003-05-26 13:07     ` Luc Teirlinck
2003-05-26 14:51 ` Stefan Monnier
     [not found] ` <200305261721.h4QHLigb001231@rum.cs.yale.edu>
2003-05-26 18:13   ` Luc Teirlinck
2003-05-26 18:26     ` Stefan Monnier
2003-05-27  2:13       ` Luc Teirlinck
2003-05-27  3:07         ` Luc Teirlinck [this message]
2003-05-27  7:26         ` David Kastrup
2003-05-27 22:41 ` 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=200305270307.h4R37RM15873@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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.