all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: moving point and invisible text
Date: Tue, 21 Feb 2006 15:56:10 -0500	[thread overview]
Message-ID: <E1FBeYM-0001iO-Sk@fencepost.gnu.org> (raw)
In-Reply-To: <jwvmzgl6647.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 20 Feb 2006 17:07:52 -0500)

    > It looks like the your code to move point out of invisible text is not
    > behaving consistently.  The previous invisible/intangible code, which
    > your code replaced, worked consistently.

    AFAIK my code did not replace it.  Both codes are still with us.

I have a memory of deleting my invisible-intangible code, so that your
code would be the only one.  But I checked now, and that appears to be
a false memory; the code is still there.  Perhaps I just thought of
deleting it and did not actually do so.

Anyway, that code does not apply to the test cases we have been
looking at, since they are just invisible, not intangible.  We need to
clean up what is done with moving point outside invisible text at the
command loop level.

    This keep coming up and the answer is still the same: no, I won't work on
    it, because I'm deeply convinced it cannot be done without introducing
    worse problems.  Such consistency is actually pretty low in the list
    of priorities.  Much more important is e.g. to ensure that repeated movement
    commands do not get stuck.

We need to do both.  There is no conflict between them.  "Not getting
stuck" is a weaker criterion; "not appearing momentarily to be stuck"
is a stronger one which includes the other.  Satisfying the latter
will not interfere with the former.

This is a new feature and we should make it work properly now.  I will
make time to work on this myself, but I don't know how soon.  I hope
someone else can do it sooner.

I want to be able to get back to checking the Emacs Manual.  That also
needs to be done, and in two weeks around the beginning of this month
I checked 2/3 of it, but I've been bogged down by other work for the
past two weeks.  I hope to get back to it soon and finish it.

  reply	other threads:[~2006-02-21 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 18:42 moving point and invisible text Richard M. Stallman
2006-02-20 22:07 ` Stefan Monnier
2006-02-21 20:56   ` Richard M. Stallman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-08  9:23 martin rudalics
2006-02-08 12:56 ` Stefan Monnier
2006-02-14  0:40 ` Richard M. Stallman
2006-02-14  7:25   ` martin rudalics
2006-02-14 22:18     ` Richard M. Stallman
2006-02-15 10:13       ` martin rudalics

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=E1FBeYM-0001iO-Sk@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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 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.