From: C K Kashyap <ckkashyap@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: A question about interactive
Date: Thu, 21 Mar 2013 12:16:56 +0530 [thread overview]
Message-ID: <CAGdT1gopLeA=bVbtXYhQX1iqjOhMv4VPNUsByp5gtjE4P5Ti8w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
Here's what I want to do - I'd like to write utility functions in
different el files and store them in a particular directory. then write a
function in .emacs - say - my-script-load ... What I'd like it to do is
this
(defun my-script-load (script-name)
(interactive "fEnter script name: ")
(load script-name)
)
Now, the problem is that the ineractive "f" seems to use the current
buffer location as the starting point. How can I change that?
Regards,
Kashyap
[-- Attachment #2: Type: text/html, Size: 718 bytes --]
next reply other threads:[~2013-03-21 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 6:46 C K Kashyap [this message]
2013-03-21 13:24 ` A question about interactive Drew Adams
2013-03-22 6:59 ` C K Kashyap
2013-03-22 7:18 ` Drew Adams
2013-03-22 11:24 ` C K Kashyap
2013-03-22 14:45 ` Drew Adams
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='CAGdT1gopLeA=bVbtXYhQX1iqjOhMv4VPNUsByp5gtjE4P5Ti8w@mail.gmail.com' \
--to=ckkashyap@gmail.com \
--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).