unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Endless Story" <usable.thought@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Writing an interactive function to accept a string argument, then call a Python script?
Date: 13 Feb 2007 03:21:21 -0800	[thread overview]
Message-ID: <1171365681.355908.131220@k78g2000cwa.googlegroups.com> (raw)
In-Reply-To: <mailman.4406.1171347657.2155.help-gnu-emacs@gnu.org>

On Feb 13, 6:20 am, Kevin Rodgers <kevin.d.rodg...@gmail.com> wrote:
>
> Just curious: Is the `M' interactive code necessary in your experience?
> I've always just used `s'.

Well, since I was hacking it out blindly, I grabbed the first thing I
saw in the GNU Emacs Lisp Reference Manual that looked like it should
work. I guess M is fancier than s, but both will work in this instance
- from the manual:

     'M'
     Arbitrary text, read in the minibuffer using the current buffer's
input method,
     and returned as a string (see Input Methods). Prompt.

     's'
     Arbitrary text, read in the minibuffer and returned as a string
(see Text from
     Minibuffer). Terminate the input with either C-j or <RET>. (C-q
may be used
     to include either of these characters in the input.) Prompt.

Meanwhile, since you're into lisp, I have a question for you: Would
there be any real advantage to my learning it, aside from customizing
Emacs beyond the things that other people have done that I can find on
the Web? My impression is that the answer is no. I'm really just a
writer who stumbled into scripting by accident, during a few years
when I was documenting software as a technical writer. I enjoy
fiddling with code mostly to automate various things I do with text
processing. Python has been perfect for this purpose - easy to learn,
easy to put down and then pick up again every few months as needed. I
once thought about learning lisp - in fact I went so far as to buy
"The Little Schemer" - but in the end I decided I could no more afford
to take the time to learn it than I could continue to learn C, which I
once dabbled in briefly for fun.

  parent reply	other threads:[~2007-02-13 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 13:08 Writing an interactive function to accept a string argument, then call a Python script? Endless Story
2007-02-09 14:18 ` Stack
2007-02-10  8:49 ` Kevin Rodgers
     [not found] ` <mailman.4285.1171097378.2155.help-gnu-emacs@gnu.org>
2007-02-10 10:57   ` Endless Story
2007-02-13  6:20     ` Kevin Rodgers
     [not found]     ` <mailman.4406.1171347657.2155.help-gnu-emacs@gnu.org>
2007-02-13 11:21       ` Endless Story [this message]
2007-02-14 17:32         ` Edward Dodge

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=1171365681.355908.131220@k78g2000cwa.googlegroups.com \
    --to=usable.thought@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).