unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dick <dick.r.chiang@gmail.com>
Cc: luangruo@yahoo.com, 52676@debbugs.gnu.org
Subject: bug#52676: 28.0.50; [PATCH] Rationalize window-text-pixel-size
Date: Tue, 21 Dec 2021 20:06:40 +0200	[thread overview]
Message-ID: <838rwdzvbj.fsf@gnu.org> (raw)
In-Reply-To: <87pmppg7up.fsf@dick> (message from dick on Tue, 21 Dec 2021 12:56:14 -0500)

> From: dick <dick.r.chiang@gmail.com>
> Date: Tue, 21 Dec 2021 12:56:14 -0500
> Cc: 52676@debbugs.gnu.org
> 
> Your transposition of "up" and "down" in pixel-scroll-precision
> contradicts the existing understanding of those two directions.

Which existing understanding is that? where does it exist?

And what do you presume is being scrolled "up": the text or the
window? should C-v be regarded as scrolling "up" or "down"? should
PageDown be bound to scroll-down-command or scroll-up-command?

> Minimally you could have kept pixel-scroll-precision in a separate
> module to avoid conflating the original `pixel-scroll.el`.  Even better,
> you might have quarantined it in ELPA.

Thank you for your valuable advice regarding file and package
organization in Emacs, but we have other ideas, so no, thanks.

> You remind me Chong Yidong, another spaghetti coder who was inexplicably
> given free reign over the code base, and proceeded to spray the master
> with indecipherable crudities still being unwound today.

Hogwash.





  parent reply	other threads:[~2021-12-21 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20  2:32 bug#52676: 28.0.50; [PATCH] Rationalize window-text-pixel-size dick
2021-12-20  3:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-20  5:20   ` dick
2021-12-20 17:11     ` Eli Zaretskii
2021-12-21  1:36       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-21  3:30         ` Eli Zaretskii
2021-12-21  3:38           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-21 12:12             ` Eli Zaretskii
2021-12-21 12:19               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-21 17:56                 ` dick
2021-12-21 18:05                   ` Robert Pluim
2021-12-22  0:59                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-21 18:06                   ` Eli Zaretskii [this message]
2021-12-22  0:58                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-21  1:34     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-20 15:19 ` 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=838rwdzvbj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52676@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=luangruo@yahoo.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).