From: Subhan Michael Tindall <SubhanT@familycareinc.org>
To: 'Barry Margolin' <barmar@alum.mit.edu>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: How automatically/immediately run command in ansi-term *with* *arguments* ?
Date: Tue, 10 Feb 2015 18:20:26 +0000 [thread overview]
Message-ID: <4dba06efb16b466296d78e95323b6d51@fcmailsvr3.familycareinc.org> (raw)
In-Reply-To: <barmar-2A0342.10504809022015@88-209-239-213.giganet.hu>
Kind of a long shot, & I'm not set up to test it,
But maybe you could put program arg1 arg2... in back-ticks? `program arg1 arg2` to force the grouping into a single 'program'?
> -----Original Message-----
> From: help-gnu-emacs-bounces+subhant=familycareinc.org@gnu.org
> [mailto:help-gnu-emacs-bounces+subhant=familycareinc.org@gnu.org] On
> Behalf Of Barry Margolin
> Sent: Monday, February 09, 2015 7:51 AM
> To: help-gnu-emacs@gnu.org
> Subject: Re: How automatically/immediately run command in ansi-term
> *with* *arguments* ?
>
> In article <18d0a858-7d2b-42de-bc61-8e16ff376569@googlegroups.com>,
> Chris Seberino <cseberino@gmail.com> wrote:
>
> > I'm trying to set some shortcuts for shell commands. I want to use
> > ansi-term as it has colors and other niceties not found in shell if I
> > use shell-command....
> >
> > This works...
> >
> > (ansi-term 'some_command_here')
> >
> > This does *NOT*...
> >
> > (ansi-term 'some_command_here arg1 arg2')
> >
> > How get arguments to work? This would be quite a nice replacement for
> > shell-command if it could for people that like/need ansi-term.
>
> The argument to ansi-term is a program, not a command. There doesn't
> seem to be a way to provide arguments to the program. Write a script that
> does what you want, and put that as the program argument.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
next prev parent reply other threads:[~2015-02-10 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 4:16 How automatically/immediately run command in ansi-term *with* *arguments* ? Chris Seberino
2015-02-09 15:50 ` Barry Margolin
2015-02-10 18:20 ` Subhan Michael Tindall [this message]
[not found] ` <mailman.19677.1423592437.1147.help-gnu-emacs@gnu.org>
2015-02-10 20:49 ` Barry Margolin
2015-02-10 23:44 ` Michael Heerdegen
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=4dba06efb16b466296d78e95323b6d51@fcmailsvr3.familycareinc.org \
--to=subhant@familycareinc.org \
--cc=barmar@alum.mit.edu \
--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).