all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10105@debbugs.gnu.org
Subject: bug#10105: 24.0.91; Possible bug in `scroll-conservatively'
Date: Mon, 28 Nov 2011 13:12:48 +0100	[thread overview]
Message-ID: <CAH8Pv0ggFESUAGJitCJGUC905tY1dXKyhhXrpQ6seouq3vBaEQ@mail.gmail.com> (raw)
In-Reply-To: <E1RUztd-0004xY-8M@fencepost.gnu.org>

>> 1. Eval: "(setq scroll-conservatively 101)".
>> 2. Eval: "(custom-set-faces '(mode-line ((t (:box (:line-width 1))))))".
>> 3. Visit the attached file.
>> 4. Type "C-s p C-s C-s C-s".
>> --> At this point, the Isearch has moved point to line "p1", but it's
>> positioned at the top of the window.  It should be at the bottom.
>
> I'm quite sure this is by design: the last C-s scrolls _up_, which
> under scroll-conservatively means Emacs should put point at the
> topmost line.  If you'd get to that line by C-p, that would be where
> point should be displayed, right?
>
> Why did you expect it to be at the bottom?

Because, after the "failing" C-s, the Isearch begins again from the
top of the buffer, so that the search direction is always (at least
conceptually) from top to bottom, i.e. _fordward_.  See info node
"(emacs)Repeat Isearch".

> And does the custom-set-faces even make a difference (I cannot test
> that where I'm typing this)?

Oh no, you're right.  Thus step #2 in the above recipe is unnecessary (sorry).


-- 
Dani Moncayo





  reply	other threads:[~2011-11-28 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  9:51 bug#10105: 24.0.91; Possible bug in `scroll-conservatively' Dani Moncayo
2011-11-25 11:33 ` Eli Zaretskii
2011-11-25 15:43   ` Eli Zaretskii
2011-11-25 16:38     ` Dani Moncayo
2011-11-28 10:38     ` Dani Moncayo
2011-11-28 12:01       ` Eli Zaretskii
2011-11-28 12:12         ` Dani Moncayo [this message]
2011-11-28 13:08           ` Eli Zaretskii
2011-11-28 17:37             ` Stefan Monnier
2011-11-28 18:11               ` Eli Zaretskii
2011-11-29  7:05       ` Juri Linkov
2011-11-29 16:55         ` 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=CAH8Pv0ggFESUAGJitCJGUC905tY1dXKyhhXrpQ6seouq3vBaEQ@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=10105@debbugs.gnu.org \
    --cc=eliz@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.