From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: stephen.berman@gmx.net, 13690@debbugs.gnu.org
Subject: bug#13690: 24.3.50; scroll-conservatively and Info-up
Date: Wed, 13 Feb 2013 23:48:02 +0200 [thread overview]
Message-ID: <83d2w351il.fsf@gnu.org> (raw)
In-Reply-To: <87pq04hway.fsf@yandex.ru>
> From: Dmitry Gutov <dgutov@yandex.ru>
> Cc: Stephen Berman <stephen.berman@gmx.net>, 13690@debbugs.gnu.org
> Date: Wed, 13 Feb 2013 23:02:13 +0400
>
> > . Since those changes were made, 2.5 years ago, I heard _zero_
> > complaints about this behavior; you are the first one. By
>
> I don't think that's true anymore. You should at least remember the bug
> I posted relatively recently:
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13133
OK, so he is the 2nd one since June 2010. How does that change the
picture?
> Like I explained in the bug above, the current behavior creates problems
> in edge cases. So a users can choose the values that "work almost right,
> but not exactly".
Every behavior can be problematic in some edge cases.
Anyway, I'm not part to this argument. I don't customize
scroll-conservatively (or any other of the scroll-* options). I just
coded it like users who complained wanted. Judging by the silence
since then, I'd say the change was mostly right. But if I'm wrong,
someone else can come up and code something different.
next prev parent reply other threads:[~2013-02-13 21:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 23:24 bug#13690: 24.3.50; scroll-conservatively and Info-up Stephen Berman
2013-02-12 16:14 ` Eli Zaretskii
2013-02-12 22:00 ` Stephen Berman
2013-02-13 4:02 ` Eli Zaretskii
2013-02-13 13:36 ` Stephen Berman
2013-02-13 17:41 ` Eli Zaretskii
2013-02-13 19:02 ` Dmitry Gutov
2013-02-13 21:48 ` Eli Zaretskii [this message]
2013-02-14 1:51 ` Dmitry Gutov
2013-02-14 5:16 ` Eli Zaretskii
2013-02-13 23:18 ` Stephen Berman
2013-02-14 5:12 ` Eli Zaretskii
2013-02-14 11:32 ` Stephen Berman
2020-08-25 11:31 ` Lars Ingebrigtsen
2020-08-25 18:02 ` Stephen Berman
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=83d2w351il.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13690@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=stephen.berman@gmx.net \
/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.