From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: compare-windows - synchronize points
Date: 14 Aug 2003 17:43:18 +0300 [thread overview]
Message-ID: <87r83oz4e1.fsf@mail.jurta.org> (raw)
In-Reply-To: <87he4k4iz9.fsf@emacswiki.org>
Alex Schroeder <alex@emacswiki.org> writes:
> One good solution to this problem is to write interactive functions
> for the most useful cases so that you can call them directly. There
> need not be many of them:
>
> compare-windows-sync-word
> compare-windows-sync-sentence
> compare-windows-sync-defun
> compare-windows-sync-regexp -- this one would query for a regexp
Adding the interactive function for syncing seems to be a good thing.
But what troubles me the most is the namespace wasting.
Instead of creating n number of compare-windows-sync-* functions
it's better to create one interactive function
(e.g. compare-windows-sync-windows) which when called with argument C-u
will ask the user for a function name (e.g. forward-word,
forward-sentence) or a regexp (anyhow, one of your proposed functions
asks for a regexp) and will set the buffer-local compare-windows-sync
variable to this function or regexp. If the compare-windows-sync-windows
is called without C-u, it could use the previously saved value of
compare-windows-sync.
--
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2003-08-14 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 19:59 compare-windows - synchronize points Juri Linkov
2003-08-12 23:22 ` Richard Stallman
2003-08-13 2:57 ` Juri Linkov
2003-08-14 3:07 ` Richard Stallman
2003-08-14 5:33 ` Juri Linkov
2003-08-16 16:19 ` Richard Stallman
2003-08-18 21:35 ` Juri Linkov
2003-08-20 2:43 ` Richard Stallman
2003-08-20 5:56 ` Juri Linkov
2003-08-26 1:38 ` Richard Stallman
2003-08-26 5:28 ` Juri Linkov
2003-08-27 16:42 ` Richard Stallman
2003-08-14 10:43 ` Alex Schroeder
2003-08-14 14:43 ` Juri Linkov [this message]
2003-08-14 23:59 ` Alex Schroeder
2003-08-15 4:21 ` 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=87r83oz4e1.fsf@mail.jurta.org \
--to=juri@jurta.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 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).