From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 64993@debbugs.gnu.org
Subject: bug#64993: 29.1; scroll-other-window breaks global-hl-line-sticky-flag
Date: Tue, 01 Aug 2023 21:04:49 +0300 [thread overview]
Message-ID: <837cqe1vwe.fsf@gnu.org> (raw)
In-Reply-To: <ierh6piac5p.fsf@janestreet.com> (message from Spencer Baugh on Tue, 01 Aug 2023 13:46:26 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: 64993@debbugs.gnu.org
> Date: Tue, 01 Aug 2023 13:46:26 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Spencer Baugh <sbaugh@janestreet.com>
> >> Cc: 64993@debbugs.gnu.org
> >> Date: Tue, 01 Aug 2023 13:32:55 -0400
> >>
> >> Arguing about this is rather pointless since I assume you would accept a
> >> patch which fixes the behavior to work even if point moves in a
> >> non-current buffer.
> >
> > I'm not sure I will, because I'm not sure I agree that the current
> > behavior is incorrect. I understand that you don't like it, but
> > that's all.
>
> Fine, can we ask an actual user of this feature whether they think this
> is a bug or not? Would that convince you that there's a bug here? Or
> what else would convince you?
I don't need to be convinced. You want a new behavior, so please
implement it as new behavior, not a change in the old one. For
example, a new, non-nil and non-t value of the sticky flag, which will
cause the mode to behave however you like it to behave. Then all this
argument is completely unnecessary (as it was from the get-go).
prev parent reply other threads:[~2023-08-01 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 14:59 bug#64993: 29.1; scroll-other-window breaks global-hl-line-sticky-flag Spencer Baugh
2023-08-01 15:54 ` Eli Zaretskii
2023-08-01 16:28 ` Spencer Baugh
2023-08-01 16:57 ` Eli Zaretskii
2023-08-01 17:13 ` Spencer Baugh
2023-08-01 17:20 ` Eli Zaretskii
2023-08-01 17:32 ` Spencer Baugh
2023-08-01 17:39 ` Eli Zaretskii
2023-08-01 17:46 ` Spencer Baugh
2023-08-01 18:04 ` Eli Zaretskii [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=837cqe1vwe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64993@debbugs.gnu.org \
--cc=sbaugh@janestreet.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).