From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Making a function than can only be used interactively
Date: Fri, 08 Jul 2022 05:40:44 +0200 [thread overview]
Message-ID: <87wncoclvn.fsf@dataswamp.org> (raw)
In-Reply-To: N6PicvQ--3-2@tutanota.com
Here is an example of a more complicated interactive spec,
(interactive
`(,(read-string "search: [repeat] ")
,(or (equal current-prefix-arg '( 4))
(equal current-prefix-arg '(64)) )
,(or (equal current-prefix-arg '(16))
(equal current-prefix-arg '(64)) )
,@(if (use-region-p)
(list (region-beginning) (region-end))
(list (point-min) (point-max)) )))
Again, eval the `interactive'!
The signature is
(defun wrap-search (str &optional case rev beg end)
Especially because 'case' and 'rev' both depends on the
`prefix-arg' I wonder if it's impossible to do with just the
interactive string, even ...
Other than that it isn't so difficult, a string is "s",
a number is "n" and the region is "r".
Note the use of the backtick just to be able to
do ,@ ... that's pretty common.
Another situation is this
(let*((case-fold-search (not case))
(pos (point))
(data (if rev (list #'search-backward end beg)
(list #'search-forward beg end) ))
(search-f (car data))
(search-beg (cadr data))
(search-end (caddr data)) ) ...)
Here we see that instead of doing (if rev ... ) three times we
stash the configuration (here 3 vars) based on 'rev', then use
`car' and the "forbidden" `cadr' and `caddr' to get from that.
(Forbidden as you should it has been said only use vanilla `car'
and `cdr', with 2 or more elements instead of `car' one should
do `nth.'.
But I think the argument-free cars are interesting I
guess ....
Full source:
https://dataswamp.org/~incal/emacs-init/wrap-search.el
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-07-08 3:40 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 19:16 Making a function than can only be used interactively carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 19:28 ` Bruno Barbier
[not found] ` <N64WnlX--3-2@missing-mail-id>
2022-07-03 19:36 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 19:53 ` Tassilo Horn
2022-07-03 20:17 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 4:51 ` Tassilo Horn
2022-07-05 23:13 ` Emanuel Berg
2022-07-03 20:14 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-03 20:27 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 20:51 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 21:18 ` Stefan Monnier
2022-07-03 21:29 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 22:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-03 22:45 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 1:13 ` Stefan Monnier
[not found] ` <jwvczelllyq.fsf-monnier+emacs@gnu.org-N65lQ2m----2>
2022-07-04 10:36 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 10:55 ` Tassilo Horn
2022-07-04 11:43 ` Christopher Dimech
2022-07-04 13:21 ` Stefan Monnier
2022-07-04 14:08 ` Robert Pluim
2022-07-04 21:40 ` Christopher Dimech
2022-07-05 17:35 ` Jean Louis
2022-07-04 19:17 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 19:40 ` Stefan Monnier
2022-07-04 19:50 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 20:45 ` Stefan Monnier
2022-07-06 0:07 ` Jean Louis
2022-07-06 20:00 ` Christopher Dimech
2022-07-06 20:29 ` Jean Louis
2022-07-07 11:03 ` Christopher Dimech
2022-07-07 21:06 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-07 21:28 ` Emanuel Berg
2022-07-07 22:14 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 3:40 ` Emanuel Berg [this message]
2022-07-08 6:08 ` Yuri Khan
2022-07-08 6:30 ` Emanuel Berg
2022-07-08 6:55 ` Yuri Khan
2022-07-08 11:44 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-09 2:05 ` Emanuel Berg
2022-07-10 4:33 ` Emanuel Berg
2022-07-08 12:06 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 12:11 ` Christopher Dimech
[not found] ` <N6Sh4jm--3-2@tutanota.com-N6ShCt5----2>
2022-07-08 12:18 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 16:14 ` Christopher Dimech
2022-07-08 20:29 ` [External] : " Drew Adams
2022-07-08 21:09 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 22:17 ` Drew Adams
2022-07-08 22:34 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-09 14:53 ` Drew Adams
2022-08-09 2:24 ` Emanuel Berg
2022-07-09 2:06 ` Emanuel Berg
2022-07-08 23:19 ` Emanuel Berg
2022-07-04 20:53 ` Drew Adams
2022-07-05 23:30 ` no difference between interactive and "from Lisp" (was: Re: Making a function than can only be used interactively) Emanuel Berg
2022-07-06 2:28 ` no difference between interactive and "from Lisp" Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-06 3:42 ` Emanuel Berg
2022-07-04 1:06 ` Making a function than can only be used interactively Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-07-04 19:32 Christopher Dimech
2022-07-04 20:10 Christopher Dimech
2022-07-04 20:35 ` Stefan Monnier
2022-07-04 20:46 ` Christopher Dimech
2022-07-04 21:18 ` Stefan Monnier
2022-07-04 21:59 ` Christopher Dimech
2022-07-05 22:34 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 21:07 Christopher Dimech
2022-07-04 21:45 ` Stefan Monnier
2022-07-04 22:05 ` Christopher Dimech
2022-07-04 22:35 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-04 23:33 ` Christopher Dimech
2022-07-04 23:42 Christopher Dimech
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=87wncoclvn.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@gnu.org \
/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).