From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Control of fan-speed on Lenovo Thinkpads
Date: Wed, 31 Mar 2021 23:02:46 +0300 [thread overview]
Message-ID: <YGTVZotTx6DKCtJY@protected.localdomain> (raw)
In-Reply-To: <jwvtuor9zdi.fsf-monnier+emacs@gnu.org>
* Stefan Monnier <monnier@iro.umontreal.ca> [2021-03-31 17:24]:
> > (let* ((sudo `(call-process "sudo" nil ,sudo-buffer t "su" "-c" "--" "root" "-c" ,command))
> > (status (eval sudo))
>
> Why? No kitten needs to suffer here:
>
> (let* ((status (call-process "sudo" nil sudo-buffer t "su" "-c" "--" "root" "-c" command))
In that specific case yes. It works, I changed it. But it defeats
itself in purpose, do you see? That COMMAND is parameter to `su' which
invokes default user's shell. I don't find it bad, it just defeats the
purpose of `call-process'.
On the other hand, something like this would not work:
(call-process "dmesg" nil (get-buffer-create "*out*") t "-l info") → 1 with message "dmesg: unknown level ' info'"
but this works:
(call-process "dmesg" nil (get-buffer-create "*out*") t "-l" "info") → 0
Maybe `call-process' is not that much safer than `shell-command',
as with some dangerous arguments it could execute wrongly. I find
it beneficial that one can forget about quoting.
(call-process "echo" nil (get-buffer-create "*out*") t "-n" "Hello
there") → 0 -- works well even with new line.
(call-process "echo" nil (get-buffer-create "*out*") t "-n" "Hello \"there\" 'Somebody here' and ''' more than that.") → 0 with message: Hello "there" 'Somebody here' and ''' more than that.
For me it brings main benefit that I can forget about problems of
quoting. I will be replacing `shell-command' in those functions
where quoting is possible problem.
Example would be here, where `figlet' accepts strings but then
with `shell-command' I would need to take care of proper quoting.
(defvar figlet-history nil)
(defvar figlet-font-history nil)
(defun figlet ()
(interactive)
(let* ((fonts '("banner" "big" "block" "bubble" "digital"
"ivrit" "lean" "mini" "mnemonic" "script"
"shadow" "slant" "small" "smscript" "smshadow"
"smslant" "standard" "term"))
(font (completing-read "Font: " fonts nil t (car figlet-font-history) 'figlet-font-history))
(text (read-from-minibuffer "Text: " (car figlet-history) nil nil 'figlet-history))
(command (format "figlet -f %s \"%s\"" font text))
(figlet (shell-command-to-string command)))
(if buffer-read-only
(message figlet)
(insert figlet))))
Then such can be improved so that programmer does not think of quoting:
(defun figlet ()
(interactive)
(let* ((fonts '("banner" "big" "block" "bubble" "digital"
"ivrit" "lean" "mini" "mnemonic" "script"
"shadow" "slant" "small" "smscript" "smshadow"
"smslant" "standard" "term"))
(font (completing-read "Font: " fonts nil t (car figlet-font-history) 'figlet-font-history))
(text (read-from-minibuffer "Text: " (car figlet-history) nil nil 'figlet-history)))
(call-process "figlet" nil t nil "-f" font text)))
Where one can insert any kind of quotes in the string:
+-+-+-+-+-+-+-+ +-+-+-+-+-+
|"|t|h|a|n|k|"| |"|y|o|u|"|
+-+-+-+-+-+-+-+ +-+-+-+-+-+
or
+-+-+-+-+-+-+ +-+-+ +-+-+-+-+-+-+-+-+ +-+-+ +-+-+ +-+-+-+-+-+ +-+-+-+ +-+
|'|'|T|h|i|s| |i|s| |'|'|F|u|n|n|y|'| |\|'| |i|t| |w|o|r|k|s| |a|l|l| |-|
+-+-+-+-+-+-+ +-+-+ +-+-+-+-+-+-+-+-+ +-+-+ +-+-+ +-+-+-+-+-+ +-+-+-+ +-+
+-+-+-+-+-+-+-+-+-+-+
|||@|\|"|n|i|c|e|\|"|
+-+-+-+-+-+-+-+-+-+-+
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-03-31 20:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 20:36 Control of fan-speed on Lenovo Thinkpads Jean Louis
2021-03-30 8:12 ` Michael Albinus
2021-03-30 9:42 ` Jean Louis
2021-03-30 9:44 ` Jean Louis
2021-03-30 10:13 ` Michael Albinus
2021-03-30 10:23 ` Finding simpler better sudo for Emacs Jean Louis
2021-03-30 10:34 ` Michael Albinus
2021-03-30 10:43 ` Jean Louis
2021-03-30 10:52 ` Michael Albinus
2021-03-30 11:05 ` Jean Louis
2021-03-30 11:13 ` Michael Albinus
2021-03-30 11:40 ` Jean Louis
2021-03-30 15:01 ` Control of fan-speed on Lenovo Thinkpads Stefan Monnier
2021-03-30 20:06 ` Jean Louis
2021-03-31 1:23 ` Stefan Monnier
2021-03-31 5:35 ` Jean Louis
2021-03-31 14:23 ` Stefan Monnier
2021-03-31 20:02 ` Jean Louis [this message]
2021-03-31 20:19 ` Stefan Monnier
2021-04-01 9:46 ` Jean Louis
[not found] <8735wcogti.fsf@gmail.com>
[not found] ` <YGNq8IGh12I+QL9I@protected.localdomain>
2021-03-31 5:49 ` Utkarsh Singh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YGTVZotTx6DKCtJY@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.