unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mauro Aranda <maurooaranda@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>, 65852@debbugs.gnu.org
Subject: bug#65852: 30.0.50; image-auto-resize :type has choices in wrong order
Date: Sun, 10 Sep 2023 10:58:17 -0300	[thread overview]
Message-ID: <6fe31ce5-4be7-7f79-e310-52e04d869467@gmail.com> (raw)
In-Reply-To: <CADwFkm=wnwujCFswmk7VZK4fsEh3rhgi7pnL-ZD=H9w2zyT1Qg@mail.gmail.com>

On 10/9/23 10:49, Stefan Kangas wrote:
 > Mauro Aranda <maurooaranda@gmail.com> writes:
 >
 >> The :type for image-auto-resize looks like this:
 >>
 >> :type '(choice (const :tag "No resizing" nil)
 >>                 (const :tag "Fit to window" fit-window)
 >>                 (other :tag "Scale down to fit window" t)
 >>                 (number :tag "Scale factor" 1))
 >>
 >> The `other' choice should come last.  Otherwise Custom thinks that
 >> that's the selected option, even when the value of image-auto-resize is
 >> a number.
 >
 > ENOPATCH

I was waiting to get a bug number assigned, so I could add it in the
commit message.  I don't know if there's any other way to do it.

 > Thanks for working on this.  Is it possible to detect issues like these
 > statically?

I worked on something like that for elint.el, based on the wishlist on
Bug#2591: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=2591

But I know it might be better to make it so that the byte-compiler
warns, so I never posted it.






  reply	other threads:[~2023-09-10 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 13:40 bug#65852: 30.0.50; image-auto-resize :type has choices in wrong order Mauro Aranda
2023-09-10 13:48 ` Mauro Aranda
2023-09-10 13:49 ` Stefan Kangas
2023-09-10 13:58   ` Mauro Aranda [this message]
2023-09-10 14:24     ` Stefan Kangas
2023-09-10 14:47       ` Mauro Aranda
2023-09-10 15:38         ` Stefan Kangas
2023-09-10 15:38       ` Mattias Engdegård
2023-09-12 14:42         ` Mattias Engdegård
2023-09-17 15:20           ` Mattias Engdegård
2023-09-17 21:53             ` Mauro Aranda

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=6fe31ce5-4be7-7f79-e310-52e04d869467@gmail.com \
    --to=maurooaranda@gmail.com \
    --cc=65852@debbugs.gnu.org \
    --cc=stefankangas@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).