From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Cursor Moving on Image Broken?
Date: Thu, 14 Apr 2005 09:34:32 +0200 [thread overview]
Message-ID: <m3wtr5erqv.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <16989.36234.529000.771236@MJ.MCHANXP648L.MCHANXP648L> (MJ Chan's message of "Wed, 13 Apr 2005 17:22:18 -0400")
MJ Chan <bichonyoyo@gmail.com> writes:
> First of all, I apologize if this is not the right mailing list to post
> a possible problem with latest CVS Emacs. (I am not on the list).
You should use M-x report-emacs-bug to report bugs with CVS Emacs.
> However, today I checked out latest Emacs from CVS and I found that I
> have a problem with ^P (previous line) when the cursor is on the
> image. I can do ^N (next-line) without a problem, but ^P will not move
> to the previous line. That is, I can only go down and cannot go up.
>
> Another problem is that when I scroll a wide image to the right (with
> my multi-column image display), I no longer can scroll back to
> beginning of the line (an image strip actually) with ^P.
Can you post a specific test case (lisp code + image + step-by-step
instructions) that shows the bogus behaviour, or at least some more
specific instructions like "size of slices" etc...
>
> I looked through the mailing archive, and saw a similar post that
> talks about partial image scrolling in January, but I am not sure if
> it is related. I also learned that the new move-line lisp function is
> also trying to help solve the scrolling of tall image. Would that have
> something to do with the problem I reported?
It could very well be a problem... Line scrolling now tries
to scroll correctly in tall images -- but it may have broken
something else.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
prev parent reply other threads:[~2005-04-14 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 21:22 Cursor Moving on Image Broken? MJ Chan
2005-04-14 7:34 ` Kim F. Storm [this message]
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=m3wtr5erqv.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).