From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
38187@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#38187: 27.0.50; No mouse-wheel scaling on images
Date: Tue, 19 Nov 2019 17:54:09 +0100 [thread overview]
Message-ID: <CADwFkmm=0PtV56b-C36JzLb6zej+bgbqPPfH1FjS6AC=O1T5uQ@mail.gmail.com> (raw)
In-Reply-To: <83tv6z25h6.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> If you think there could be a problem with discoverability, we could
> add some index entries to the manual, and maybe mention "font" in the
> doc string of the command.
>
> Other than that, I really don't see how this could be hard to
> discover: we have just added a binding of C-wheel-up and C-wheel-down,
> something that every application out there supports, haven't we? So
> what kind of discoverability problems we envision with that binding in
> place?
That's a very good point. I might be living in the past when we
didn't have these key bindings.
Since we also can't seem to be able to find a much better command
name, I'll retract my defalias proposal and look into your suggestion
to add an entry to the index instead.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-11-19 16:54 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 20:38 bug#38187: 27.0.50; No mouse-wheel scaling on images Juri Linkov
2019-11-14 12:48 ` Eli Zaretskii
2019-11-17 10:04 ` Lars Ingebrigtsen
2019-11-17 16:05 ` Eli Zaretskii
2019-11-17 16:07 ` Lars Ingebrigtsen
2019-11-17 21:20 ` Stefan Kangas
2019-11-17 22:42 ` Juri Linkov
2019-11-18 9:10 ` Lars Ingebrigtsen
2019-11-18 21:37 ` Juri Linkov
2019-11-19 3:31 ` Eli Zaretskii
2019-11-20 23:00 ` Juri Linkov
2019-11-21 3:35 ` Eli Zaretskii
2019-11-21 21:18 ` Alan Third
2019-11-21 22:51 ` Juri Linkov
2019-11-22 7:47 ` Eli Zaretskii
2019-11-21 21:26 ` Lars Ingebrigtsen
2019-11-21 22:57 ` Juri Linkov
2019-11-21 23:10 ` Lars Ingebrigtsen
2019-11-22 7:58 ` Eli Zaretskii
2019-11-22 7:51 ` Eli Zaretskii
2019-11-22 7:31 ` Eli Zaretskii
2019-11-22 12:41 ` Lars Ingebrigtsen
2019-11-22 9:50 ` Alan Third
2019-11-22 10:04 ` Eli Zaretskii
2019-11-22 10:33 ` Alan Third
2019-11-22 13:26 ` Eli Zaretskii
2019-11-19 8:09 ` Lars Ingebrigtsen
2019-11-20 23:12 ` Juri Linkov
2019-11-21 12:11 ` Lars Ingebrigtsen
2019-11-21 14:25 ` Eli Zaretskii
2019-11-21 22:45 ` Juri Linkov
2019-11-23 22:23 ` Juri Linkov
2019-11-27 11:58 ` Lars Ingebrigtsen
2019-11-17 23:01 ` Drew Adams
2019-11-18 9:08 ` Lars Ingebrigtsen
2019-11-19 14:49 ` Stefan Kangas
2019-11-19 15:27 ` Drew Adams
2019-11-19 16:07 ` Stefan Kangas
2019-11-19 16:12 ` Stefan Kangas
2019-11-19 16:27 ` Drew Adams
2019-11-21 0:01 ` Stefan Kangas
2019-11-21 0:41 ` Drew Adams
2019-11-19 16:31 ` Eli Zaretskii
2019-11-19 16:54 ` Stefan Kangas [this message]
2019-11-19 22:50 ` Juri Linkov
2019-11-19 17:27 ` 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='CADwFkmm=0PtV56b-C36JzLb6zej+bgbqPPfH1FjS6AC=O1T5uQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=38187@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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 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).