From: Juri Linkov <juri@linkov.net>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] scratch/follow e8937de: Replace GROUP argument in six window primitives by new functions.
Date: Fri, 18 Dec 2015 01:52:39 +0200 [thread overview]
Message-ID: <87zix863aw.fsf@mail.linkov.net> (raw)
In-Reply-To: <20151217221445.GD1888@acm.fritz.box> (Alan Mackenzie's message of "Thu, 17 Dec 2015 22:14:45 +0000")
> I think it would have to be `recenter-window-group', but is
> `recenter-group' really that ambiguous? People have no problem with
> `recenter', which, if anything, is even more ambiguous.
I don't know why `recenter' is not `recenter-window'
like other existing functions e.g. `reposition-window'.
Maybe for historical reasons. But `recenter-group'
will add more ambiguity: recenter what? what group?
> So, I think it would be possible to move some of the code from follow.el
> to window.el, but the interface between them would necessarily be
> thicker than just `follow-all-followers'. It would have to include the
> "cache-invalid" flag (probably encapsulated in a function call), and the
> `follow-redisplay' function. I'm not convinced that there would be any
> great gain in abstraction.
This abstraction is not needed as long as window groups are used
only in one package follow.el.
next prev parent reply other threads:[~2015-12-17 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151214165252.26784.43201@vcs.savannah.gnu.org>
[not found] ` <E1a8WMm-0006yi-Di@vcs.savannah.gnu.org>
2015-12-15 1:30 ` [Emacs-diffs] scratch/follow e8937de: Replace GROUP argument in six window primitives by new functions John Wiegley
2015-12-15 13:15 ` Alan Mackenzie
2015-12-15 15:22 ` [Emacs-diffs] scratch/follow e8937ed: " John Wiegley
2015-12-16 0:39 ` [Emacs-diffs] scratch/follow e8937de: " Juri Linkov
2015-12-17 22:14 ` Alan Mackenzie
2015-12-17 23:52 ` Juri Linkov [this message]
2015-12-18 0:43 ` [Emacs-diffs] scratch/follow e8937ed: " John Wiegley
2015-12-18 10:57 ` Alan Mackenzie
2015-12-20 13:05 ` Alan Mackenzie
2015-12-22 19:19 ` John Wiegley
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=87zix863aw.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=acm@muc.de \
--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.