From: Juri Linkov <juri@linkov.net>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Auto-resizing of images in image-mode
Date: Tue, 21 Apr 2020 02:44:52 +0300 [thread overview]
Message-ID: <87eeshvi2l.fsf@mail.linkov.net> (raw)
In-Reply-To: <87ftcy4fe7.fsf@gmail.com> ("Štěpán Němec"'s message of "Mon, 20 Apr 2020 12:31:44 +0200")
> I don't use doc-view mode, but consistency seems important, esp. given
> that its keymap iherits from image-mode-map.
>
> OTOH I really like grouping similar functionality to a common prefix, as
> it helps both mnemonics and discoverability/documentation, so I think
> I'd prefer changing doc-view mode to follow image-mode's example here;
> possibly changing the s prefix to something else (in the parent, i.e.
> image-mode) so it doesn't conflict with the slice prefix. But changing
> UI defaults is always a delicate matter...
Some unfinished code in image-mode.el
;; ;; (define-key map "c f h" 'image-scale-fit-height)
;; ;; (define-key map "c ]" 'image-rotate-right)
uses the prefix "c", but I see no mnemonics in "c".
There is some mnemonics in the prefix "t" (transform):
t 0 image-transform-reset
t b image-transform-fit-both
t f image-mode-fit-frame
t h image-transform-fit-to-height
t r image-transform-set-rotation
t s image-transform-set-scale
t w image-transform-fit-to-width
but I'm still not sure if this is the best possible outcome.
next prev parent reply other threads:[~2020-04-20 23:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 18:13 Auto-resizing of images in image-mode Eli Zaretskii
2020-04-16 21:53 ` Juri Linkov
2020-04-17 6:45 ` Eli Zaretskii
2020-04-18 23:45 ` Juri Linkov
2020-04-19 6:58 ` Štěpán Němec
2020-04-19 23:17 ` Juri Linkov
2020-04-20 10:31 ` Štěpán Němec
2020-04-20 15:29 ` Eli Zaretskii
2020-04-20 23:44 ` Juri Linkov [this message]
2020-04-20 13:09 ` Stefan Monnier
2020-04-21 21:28 ` Juri Linkov
2020-04-22 5:34 ` Tassilo Horn
2020-04-19 12:34 ` Alan Third
2020-04-19 23:18 ` Juri Linkov
2020-04-19 14:06 ` Eli Zaretskii
2020-04-19 23:19 ` Juri Linkov
2020-04-19 23:58 ` Juri Linkov
2020-04-20 14:39 ` Eli Zaretskii
2020-04-20 23:43 ` Juri Linkov
2020-04-21 13:51 ` 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=87eeshvi2l.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stepnem@gmail.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).