From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: calling interactive functions programmatically
Date: Fri, 25 Apr 2003 09:38:59 -0600 [thread overview]
Message-ID: <3EA95693.2090808@yahoo.com> (raw)
In-Reply-To: vfist2pv0d.fsf@rpc71.cs.man.ac.uk
Phillip Lord wrote:
> Now I want to wrap this call inside another, where I already know the
> directory in question, but do not know the arguments.
>
> So I guess I can do...
>
>
> (defun my-find-dired(args)
> (interactive (read-string "Run find (with args): " find-args
> '(find-args-history . 1)))
> (find-dired (get-the-directory-name-from-somewhere-else)
> args))
>
> But ideally I would like to not do the "read-string" form, as this
> duplicates everything in find-dired.
>
> Is there a way to do this?
Does this work:
;; M-x gross-hack
(let ((unread-command-events
(listify-key-sequence
(concat (get-the-directory-name-from-somewhere-else)
"\r"))))
(call-interactively 'find-dired))
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
prev parent reply other threads:[~2003-04-25 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 13:27 calling interactive functions programmatically Phillip Lord
2003-04-25 15:38 ` Kevin Rodgers [this message]
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=3EA95693.2090808@yahoo.com \
--to=ihs_4664@yahoo.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.
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).