all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, "Michaël Cadilhac" <michael@cadilhac.name>,
	emacs-devel@gnu.org
Subject: Re: line-move-partial too costly ?
Date: Mon, 18 Sep 2006 22:42:02 +0200	[thread overview]
Message-ID: <m3ac4wc3fp.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87eju99npb.fsf@stupidchicken.com> (Chong Yidong's message of "Mon\, 18 Sep 2006 11\:52\:32 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> storm@cua.dk (Kim F. Storm) writes:
>
>>>>> Since the creation of line-move-partial, going to the next few lines
>>>>> has become a P*TA.
>>>>
>>>>> Is there any solution ?
>>>>
>>>> I installed a small optimization -- pls try again.
>>>>
>>> AFAICT, it doesn't fix my problem.
>>
>> I have installed an more elaborate change to line-move-partial
>> (involving a new primitive `window-line-visibility').
>
> Can we consider the FOR-RELEASE item fixed?
>
>   ** Michael Cadilhac's line-move-partial is slow.

Michaël still has to confirm that the changes I made in the last few
days fixes the problem.  If not, I have one more thing I can try....

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-09-18 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 14:11 line-move-partial too costly ? Michaël Cadilhac
2006-09-13 22:51 ` Kim F. Storm
2006-09-14 12:23   ` Michaël Cadilhac
2006-09-14 14:15     ` Kim F. Storm
2006-09-15 21:06     ` Kim F. Storm
2006-09-18 15:52       ` Chong Yidong
2006-09-18 20:42         ` Kim F. Storm [this message]
2006-09-19  8:19       ` Michaël Cadilhac
2006-09-19 12:07         ` Kim F. Storm
2006-09-19 22:57         ` Richard Stallman
2006-09-20 10:50           ` Kim F. Storm
2006-09-14 12:29 ` Miles Bader
2006-09-14 12:58   ` Michaël Cadilhac
2006-09-14 13:31     ` Miles Bader

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=m3ac4wc3fp.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=michael@cadilhac.name \
    --cc=rms@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.