From: Miles Bader <miles@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: David Hansen <david.hansen@gmx.net>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [david.hansen@gmx.net: Re: comint's directory tracking doesn't understand \( or \)]
Date: Wed, 07 Mar 2007 09:48:51 +0900 [thread overview]
Message-ID: <87irddev4c.fsf@catnip.gol.com> (raw)
In-Reply-To: <jwvd53naz5g.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon\, 05 Mar 2007 21\:23\:32 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Wouldn't it be better to move it to shell.el?
> I.e. create a new function shell-argument?
I think it would be a nicer interface if it were split into two
functions: one which which would just parse the arguments and return a
lisp list of them (e.g. `shell-split') and one which would call
shell-split and do the choose-N-through-M-and-apply-mapconcat stuff to
return a string (e.g., `shell-arguments-string').
E.g.:
(shell-split "this is \"a test\"") => ("this" "is" "a test")
(shell-arguments-string "this is \"a test\"" 1 2) => "is \"a test\""
Simple uses might use the latter but the former seems a generally
cleaner interface and building block for other uses.
-Miles
--
The automobile has not merely taken over the street, it has dissolved the
living tissue of the city. Its appetite for space is absolutely insatiable;
moving and parked, it devours urban land, leaving the buildings as mere islands
of habitable space in a sea of dangerous and ugly traffic.
[James Marston Fitch, New York Times, 1 May 1960]
next prev parent reply other threads:[~2007-03-07 0:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 17:44 [david.hansen@gmx.net: Re: comint's directory tracking doesn't understand \( or \)] Richard Stallman
2007-03-04 13:13 ` David Hansen
2007-03-04 15:45 ` Chong Yidong
2007-03-04 15:51 ` David Kastrup
2007-03-04 19:26 ` Chong Yidong
2007-03-04 19:32 ` David Kastrup
2007-03-04 19:39 ` Lennart Borgman (gmail)
2007-03-04 20:16 ` David Kastrup
2007-03-04 20:25 ` Lennart Borgman (gmail)
2007-03-04 19:47 ` Miles Bader
2007-03-04 21:45 ` Stefan Monnier
2007-03-04 22:06 ` Andreas Seltenreich
2007-03-04 23:42 ` Stefan Monnier
2007-03-04 23:13 ` David Hansen
2007-03-04 23:30 ` David Kastrup
2007-03-05 2:09 ` David Hansen
2007-03-04 19:40 ` Robert J. Chassell
2007-03-04 20:17 ` David Kastrup
2007-03-04 23:22 ` Chris Moore
2007-03-04 23:23 ` Tom Tromey
2007-03-05 2:55 ` Richard Stallman
2007-03-05 6:23 ` David Hansen
2007-03-05 21:50 ` Richard Stallman
2007-03-06 2:23 ` Stefan Monnier
2007-03-06 3:10 ` David Hansen
2007-03-06 22:36 ` Richard Stallman
2007-03-07 0:48 ` Miles Bader [this message]
2007-03-07 14:49 ` David Hansen
2007-03-08 3:16 ` Richard Stallman
2007-03-09 19:55 ` Chong Yidong
2007-03-09 20:28 ` Glenn Morris
2007-03-09 20:45 ` David Hansen
2007-03-09 21:08 ` David Kastrup
2007-03-10 0:04 ` Chong Yidong
2007-03-10 8:06 ` David Hansen
2007-03-10 20:18 ` Chong Yidong
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=87irddev4c.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=david.hansen@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).