unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 14881@debbugs.gnu.org
Subject: bug#14881: 24.3.50; Odd cursor movement with images (or lines with different heights?)
Date: Tue, 16 Jul 2013 22:36:28 +0300	[thread overview]
Message-ID: <83a9lm2t6r.fsf@gnu.org> (raw)
In-Reply-To: <m3ip0amjr5.fsf@stories.gnus.org>

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: 14881@debbugs.gnu.org
> Date: Tue, 16 Jul 2013 20:39:58 +0200
> 
> Defaulting to the current cursor (non-)movement seems kinda un-obvious.
> Why would anybody want `C-n' to scroll the window instead of er moving
> the cursor down?

Because you don't want the images to jump.  If they do, you won't see
some of their parts, especially if the window height is small.

> I rather like the way Emacs keeps the entire image in the buffer.

??? You mean in the window, right?

> Scrolling so that an image is cut off (at the top) is not very pleasant.

Then I think you are in the minority here.  Most people want to see
the images they scroll across in their entirety, not just some parts
of them.





  reply	other threads:[~2013-07-16 19:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 17:57 bug#14881: 24.3.50; Odd cursor movement with images (or lines with different heights?) Lars Magne Ingebrigtsen
2013-07-16 18:29 ` Eli Zaretskii
2013-07-16 18:39   ` Lars Magne Ingebrigtsen
2013-07-16 19:36     ` Eli Zaretskii [this message]
2013-07-16 19:41       ` Lars Magne Ingebrigtsen
2013-07-17 10:50       ` Lars Magne Ingebrigtsen
2013-07-17 16:54         ` Eli Zaretskii
2013-07-18 13:57           ` Lars Magne Ingebrigtsen
2013-07-18 16:52             ` Eli Zaretskii
2013-07-19 11:07               ` Lars Magne Ingebrigtsen
2013-07-19 14:04                 ` Eli Zaretskii
2013-07-19 14:13                   ` Lars Magne Ingebrigtsen
2013-07-19 14:31                     ` 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

  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=83a9lm2t6r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14881@debbugs.gnu.org \
    --cc=larsi@gnus.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).