all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The future of Follow Mode - a proposal.
Date: Thu, 25 Feb 2016 11:46:58 -0500	[thread overview]
Message-ID: <jwvmvqog32u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83lh68g3fh.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 Feb 2016 18:28:18 +0200")

> Actually, vertical-motion completely breaks in that case.  I don't
> even see a way that will allow to solve that situation in principle,
> except in some very specific and restricted use cases.

Exactly.  E.g. the behavior of vertical-motion could be "made to work" in
the case where the motion is within the existing glyph matrices of the
relevant windows, tho even in that case there could be several possible
desirable behaviors depending on the intention behind the use of
vertical-motion.

> Which is why I strongly suggest to change Follow Mode so that it
> forces all of its windows be of the same width.

And in that case my Elisp hook approach should be usable (assuming it's
implementable ;-).

> With the current pixelwise control of window dimensions, this is easy.

Not sure about "easy" but yes.

> I think this will magically remove many of the problems that currently
> plague Follow Mode, and leave us with something we can reasonably easy
> to solve and maintain.

Sounds fine (and doable in Elisp).

> However, Alan disagrees, and insists on supporting windows of unequal
> width.

I think it might makes sense to allow the user to disable the "make all
follow-mode windows same-width" and just live with the corresponding
quirks, but I suspect that the amount of work needed to make follow-mode
work "100% correctly" for the mixed-width case is really large (it will
involve defining new primitives to replace vertical-motion, then
changing all users accordingly).  What's the expected use-case that
would justify such an effort?


        Stefan



  reply	other threads:[~2016-02-25 16:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 19:56 The future of Follow Mode - a proposal Alan Mackenzie
2016-02-18 20:24 ` Eli Zaretskii
2016-02-19 14:25   ` Alan Mackenzie
2016-02-19 14:34     ` martin rudalics
2016-02-19 16:12       ` Eli Zaretskii
2016-02-19 16:08     ` Eli Zaretskii
2016-02-19 18:18       ` Alan Mackenzie
2016-02-19 18:45         ` Eli Zaretskii
2016-02-20 12:44           ` Alan Mackenzie
2016-02-20 13:05             ` Eli Zaretskii
2016-02-23 23:11               ` Alan Mackenzie
2016-02-24  3:57                 ` Stefan Monnier
2016-02-24 17:14                   ` Eli Zaretskii
2016-02-24 18:57                     ` Stefan Monnier
2016-02-24 19:19                       ` Eli Zaretskii
2016-02-24 20:10                         ` Stefan Monnier
2016-02-24 20:21                           ` Eli Zaretskii
2016-02-25  0:30                             ` Stefan Monnier
2016-02-25 16:28                               ` Eli Zaretskii
2016-02-25 16:46                                 ` Stefan Monnier [this message]
2016-02-25 17:29                                   ` Eli Zaretskii
2016-02-25 20:30                                 ` Alan Mackenzie
2016-02-25 20:57                       ` Alan Mackenzie
2016-02-25 21:10                         ` Stefan Monnier
2016-02-25 22:17                           ` Alan Mackenzie
2016-02-28 16:40                             ` Stefan Monnier
2016-02-24 18:34                 ` Eli Zaretskii
2016-02-25 20:18                   ` Alan Mackenzie
2016-02-19 14:56   ` Anders Lindgren
2016-02-19 16:30     ` Eli Zaretskii
2016-02-19 18:45       ` Alan Mackenzie
2016-02-18 20:41 ` John Yates
2016-02-19 16:21   ` Alan Mackenzie
2016-02-19 16:32     ` Eli Zaretskii
2016-02-19 19:25     ` John Yates
2016-02-19 20:27       ` Eli Zaretskii

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=jwvmvqog32u.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@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.