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: Delete multiple repositories programmatically from elisp by supplying `y' as the answer to an interactively called function.
Date: Wed, 08 Dec 2021 11:47:31 +0100 [thread overview]
Message-ID: <87pmq7xtj0.fsf@zoho.eu> (raw)
In-Reply-To: 875yrzqvq1.fsf@gmail.com
Robert Pluim wrote:
>>> (let ((current-prefix-arg '(4)))
>>> (call-interactively #'straight-remove-unused-repos))
>>
>> Why does it have to be used interactively?
>> That's often not a good sign ...
>
> In this case it doesn't. Other commands inspect the value of
> current-prefix-arg, not just the value produced by their
> `interactive' spec, and then you have to use this
> particular hammer.
In the function body, in my experience it is best to refer to
the formal parameter, if one desires a default value one can
examine if it is unset and set it in a `let', then use the
let binding. Do this before anything else happens ...
Like below [last], it it works from Lisp without an argument,
from Lisp with an argument, interactively without an argument,
and interactively with a (prefix) argument.
It is often less complicated tho ... like this
(defun some-fun (&optional n)
(interactive "P")
(let ((num (or n 12)))
(message "move it! %d" num) ))
(some-fun) ; 12, the default
(some-fun 10) ; 10
;; C-u 7 M-x some-fun RET ; 7
;; M-x some-fun RET ; 12, again
Anyway ...
;;; -*- lexical-binding: t -*-
;;;
;;; this file:
;;; http://user.it.uu.se/~embe8573/emacs-init/string.el
;;; https://dataswamp.org/~incal/emacs-init/string.el
(defun hline (&optional char)
(interactive "P")
(let ((len (- (window-width) (or (current-column) 0) 1))
(c (or (and (listp char) (car char))
(and (numberp char) char)
?-) ))
(insert (make-string len c)) ))
(defalias 'hl #'hline)
(when nil
(hline)----------------------------------------------------------------------
(hline 42)*******************************************************************
(hline ?+)+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
M-x hline RET----------------------------------------------------------------
C-u C-u C-u M-x hline RET@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
C-u 59 M-x hline RET;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
)
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-12-08 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 13:16 Delete multiple repositories programmatically from elisp by supplying `y' as the answer to an interactively called function Hongyi Zhao
2021-12-07 17:05 ` Robert Pluim
2021-12-07 19:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-08 9:41 ` Robert Pluim
2021-12-08 10:47 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-12-07 23:35 ` Hongyi Zhao
2021-12-08 2:56 ` Hongyi Zhao
2021-12-08 3:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-08 3:45 ` Hongyi Zhao
2021-12-08 9:07 ` Robert Pluim
2021-12-08 9:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-07 22:20 ` Michael Heerdegen
2021-12-07 23:49 ` Hongyi Zhao
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=87pmq7xtj0.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).