From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: invisible text and point
Date: Mon, 26 May 2003 14:26:33 -0400 [thread overview]
Message-ID: <200305261826.h4QIQX5S001474@rum.cs.yale.edu> (raw)
In-Reply-To: 200305261813.h4QIDN815240@eel.dms.auburn.edu
> I posted a follow-up to my original message from yesterday evening
> this morning. I no longer propose "reverting" to the emacs-21.3
> behavior (actually, I only did this because I misinterpreted it
> yesterday, as I noticed this morning), but "mimicking it better", by
> making sure that (point) returns the position of a visible character.
Semantic detail (relevant in this context): `point' is always between
two characters, which is why there is no (char-of POS) but there are
(char-before POS) and (char-after POS).
> Since my conjecture that the infinite loops were also related to the
> problem was apparently a premature conclusion based on the fact that
> the bugs did not occur in 21.3 and happened at similar places as the
> other bug, we are left with the m and RETURN bugs in info. Just
Yes, we need to address those. Making invisible front-sticky and
not rear-sticky (in the info buffer) is easy enough.
I guess the question now is: should we give preference to the desire
to ensure that "self-insert-command will insert a visible character"
or to "`char-after' is what the user sees (i.e. is visible)".
Stefan
next prev parent reply other threads:[~2003-05-26 18:26 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 [this message]
2003-05-27 2:13 ` Luc Teirlinck
2003-05-27 3:07 ` Luc Teirlinck
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
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=200305261826.h4QIQX5S001474@rum.cs.yale.edu \
--to=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 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).