unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Better way to make sure external command exists in the system?
Date: Tue, 23 Mar 2021 10:56:38 +0100	[thread overview]
Message-ID: <87o8faxkfd.fsf@zoho.eu> (raw)
In-Reply-To: YFmgmMt3A738/3tB@protected.localdomain

Jean Louis wrote:

OK, let's see, straight X-Mas Eve this...

> (defvar *image-default-resize-size* 1536)
> (defvar *image-resize-sizes* '("1536" "1024" "800" "1200" "640"))

The *common-lisp-convention* for global variables is
disencourage in Elisp.

Also, why the strings?

> Argument FILE is image to be resized."
>   (if (rcd-which-list '("mogrify"))

Not known to be defined: rcd-which-list (indeed I don't have it)
Same with rcd-warning-message.

>       (let ((extension (file-name-extension file)))
> 	(when (or (equal (downcase extension) "jpg")
> 		  (equal (downcase extension) "png"))

Same thing twice, instead do let*.

> (defun image-resize-dired ()
>   "Resizes images."
>   (interactive)
>   (let ((files (dired-get-marked-files))
> 	(size (read-number "Size: " *image-default-resize-size* '(*image-resize-sizes*))))

HIST isn't used like that what I can see, read the
`read-from-minibuffer' docstring. Does it even work?

Also, why `read-number' and not in interactive?

And, no need for globals if they are only used here. Use let*
for that as well.

Keep it on...

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




  reply	other threads:[~2021-03-23  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 12:13 Better way to make sure external command exists in the system? Jean Louis
2021-03-19 13:57 ` Daniel Martín
2021-03-19 14:16   ` 2QdxY4RzWzUUiLuE
2021-03-21 14:10     ` Jean Louis
2021-03-21 17:17       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-21 14:07   ` Jean Louis
2021-03-21 17:16     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-23  8:02       ` Jean Louis
2021-03-23  9:56         ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-03-23 10:13           ` Jean Louis
2021-03-25 15:01             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 15:17               ` Jean Louis
2021-03-25 20:47                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 20:56                   ` Jean Louis
2021-03-25 21:10                     ` Emanuel Berg via Users list for the GNU Emacs text editor

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=87o8faxkfd.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.
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).