From: Eli Zaretskii <eliz@gnu.org>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: 28922-done@debbugs.gnu.org
Subject: bug#28922: Pixel scrolling by frame-char-height
Date: Fri, 27 Oct 2017 17:24:17 +0300 [thread overview]
Message-ID: <838tfw7jou.fsf@gnu.org> (raw)
In-Reply-To: <20171021.131114.437162303416323549.tkk@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Sat, 21 Oct 2017 13:11:14 +0900 (JST))
> Date: Sat, 21 Oct 2017 13:11:14 +0900 (JST)
> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
> Cc: tkk@misasa.okayama-u.ac.jp
>
> I'm sending a patch for lisp/pixel-scroll.el.
Thanks, I pushed it to the emacs-26 branch.
Please in the future make sure the 1st line of the doc string is not
longer than 79 characters, and is a full sentence.
Also, please fill the lines in the log entry to be shorter than 75
characters, not including the leading whitespace. And include the bug
number in the log message.
(I modified your patch to fix all those issues.)
> diff --git a/etc/NEWS b/etc/NEWS
> old mode 100644
> new mode 100755
> index 74d6e8bf1c..d9eb4f9462
> --- a/cygdrive/c/Users/dream/Downloads/emacs/etc/NEWS
> +++ b/cygdrive/c/Users/dream/Dropbox/Downloads@TK/NEWS
> @@ -76,6 +76,12 @@ globally or for individual definitions.
> the XTerm window title. This feature is experimental and is disabled
> by default.
>
> +** Pixel-Scroll
> +
> +---
> +*** Now scroll vertically by number of pixels returned by
> +'frame-char-height' when 'pixel-resolution-fine-flag' is set to t.
I didn't install this part, because pixel-scroll-mode is a new mode
and is mentioned as such in NEWS. So everything about it is "new",
and there's no need to mention individual changes.
prev parent reply other threads:[~2017-10-27 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 4:11 bug#28922: Pixel scrolling by frame-char-height Tak Kunihiro
2017-10-27 14:24 ` 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=838tfw7jou.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28922-done@debbugs.gnu.org \
--cc=tkk@misasa.okayama-u.ac.jp \
/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).