From: Eli Zaretskii <eliz@gnu.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: 14780@debbugs.gnu.org
Subject: bug#14780: Acknowledgement (Regression: C-n doesn't go to next line under simple circumstances)
Date: Fri, 19 Jul 2013 22:14:28 +0300 [thread overview]
Message-ID: <83fvvaz7jf.fsf@gnu.org> (raw)
In-Reply-To: <CAFM41H3p4jhh4=fGBDcC7PujEsH2ib0ijEnR67gs2ek0LkwjgQ@mail.gmail.com>
> Date: Fri, 19 Jul 2013 14:37:57 -0400
> From: Barry OReilly <gundaetiapo@gmail.com>
>
> Git bisected the repo at Savannah to:
>
> 15cdf9527f5a78a5ea9aa0ba3fee8d7b84c3acf9 is the first bad commit
> commit 15cdf9527f5a78a5ea9aa0ba3fee8d7b84c3acf9
> Author: Eli Zaretskii <eliz@gnu.org>
> Date: Mon Dec 3 22:48:12 2012 +0200
>
> Fix bug #13055 with cursor positioning inside scroll-margin.
>
> src/xdisp.c (redisplay_window): If the cursor is visible, but inside
> the scroll margin, move point outside the margin.
I cannot reproduce the bug on my system. Unless I don't understand
what you mean by "cannot reach the '-' character". I can reach every
line in the buffer by using C-n, using your recipe (or what I
understand of it).
next prev parent reply other threads:[~2013-07-19 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 16:03 bug#14780: Regression: C-n doesn't go to next line under simple circumstances Barry OReilly
[not found] ` <handler.14780.B.13728674128397.ack@debbugs.gnu.org>
2013-07-19 18:37 ` bug#14780: Acknowledgement (Regression: C-n doesn't go to next line under simple circumstances) Barry OReilly
2013-07-19 19:14 ` Eli Zaretskii [this message]
2013-07-19 19:53 ` Barry OReilly
2013-07-19 20:30 ` bug#14780: Regression: C-n doesn't go to next line under simple circumstances Eli Zaretskii
2013-07-19 20:37 ` Barry OReilly
2013-07-20 6:42 ` Eli Zaretskii
2013-07-20 8:33 ` Eli Zaretskii
2013-07-20 9:09 ` Eli Zaretskii
2013-07-22 20:37 ` Barry OReilly
2013-07-24 17:38 ` 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=83fvvaz7jf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14780@debbugs.gnu.org \
--cc=gundaetiapo@gmail.com \
/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).