unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juanma Barranquero <lekktu@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r99831: Scrolling commands which does not signal errors at top/bottom.
Date: Fri, 16 Apr 2010 02:56:33 +0300	[thread overview]
Message-ID: <87ljcoe0cu.fsf@mail.jurta.org> (raw)
In-Reply-To: <jwvtyrds524.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 15 Apr 2010 00:41:24 -0400")

>> Wouldn't it better to define scrolling commands for
>> scroll-preserve-screen-position the same way with symbol properties?
>
> Fine by me.

Done with the `scroll-command' property.

> Especially if we can reduce the number of symbol properties
> by merging them into just one `scroll-command' property
> which isearch and scroll-preserve-screen-position can share.

Unfortunately, the definition of a scroll command used
by `isearch-allow-scroll' is too broad: it can be a command
that scrolls the window, acts on the other window or changes
the window layout.  I'm not sure if it would be good for
`scroll-preserve-screen-position' to put the `scroll-command' property
on all these commands that currently have the `isearch-scroll' property,
or whether some users might want to remove the `isearch-scroll' property
from some real scroll commands.

-- 
Juri Linkov
http://www.jurta.org/emacs/




  reply	other threads:[~2010-04-15 23:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NywTs-00007U-Lf@internal.in.savannah.gnu.org>
2010-04-06  0:51 ` [Emacs-diffs] /srv/bzr/emacs/trunk r99831: Scrolling commands which does not signal errors at top/bottom Juanma Barranquero
2010-04-06  0:59   ` Juri Linkov
2010-04-06  1:58     ` Juanma Barranquero
2010-04-06 16:12       ` Juri Linkov
2010-04-06 18:26         ` Juanma Barranquero
2010-04-06 20:19           ` Juri Linkov
2010-04-06 20:49             ` Juanma Barranquero
2010-04-06 21:06               ` Juri Linkov
2010-04-06 21:39                 ` Juanma Barranquero
2010-04-06 21:47                   ` Juanma Barranquero
2010-04-07 20:17                     ` Juri Linkov
2010-04-07 22:16                       ` Juanma Barranquero
2010-04-07 23:19                         ` Juri Linkov
2010-04-07 23:35                           ` Juanma Barranquero
2010-04-09 15:29                       ` Stefan Monnier
2010-04-09 22:46                         ` Juri Linkov
2010-04-10 14:51                           ` Stefan Monnier
2010-04-14 16:49                             ` Juri Linkov
2010-04-15  4:41                               ` Stefan Monnier
2010-04-15 23:56                                 ` Juri Linkov [this message]
2010-04-16  0:41                                   ` Stefan Monnier
2010-04-16  1:27                                     ` Juri Linkov

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=87ljcoe0cu.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).