From: "Ehud Karni" <ehud@unix.mvs.co.il>
Cc: henrik+news@enberg.org, emacs-devel@gnu.org
Subject: Re: M-x compile for different file extensions
Date: Tue, 22 Oct 2002 20:23:06 +0200 [thread overview]
Message-ID: <200210221823.g9MIN6v0026498@beta.mvs.co.il> (raw)
In-Reply-To: <E183pT3-0000MX-00@fencepost.gnu.org> (message from Richard Stallman on Mon, 21 Oct 2002 23:12:29 -0400)
On Mon, 21 Oct 2002 23:12:29 -0400, Richard Stallman <rms@gnu.org> wrote:
>
> 2. We use the compile command on many type of files which are not
> real "programs" - shell scripts (run with arguments), sql queries,
> reports (printed by the `compile') and many, many others.
>
> Ok, but if you do that, is it really the case that the command you want
> to run follows from the current visited file?
Yes, because we have our "standard" extensions for this kind of files.
> > 5. Run some commands with interactive input to them (when needed) in a
> > compilation window, with an option to kill the compilation buffer.
> > (`compile-commands', read the help carefully).
> >
> > Why is this better than using a single shell command string, with `;'
> > and `sleep N' used as needed between the individual shell commands?
>
> This is really used for programs that use /dev/tty (and not standard
> input), for security (programs that need pass words) or dynamic
> answers. It also has the added advantage of running multiple processes,
> each with its own buffer and different name automatically.
>
> I don't see the connection--would you please explain?
> These programs would relate to the other feature, having a way to send
> input to the compilation process, but I don't see how they relate
> to this feature.
An example may clarify it:
(compile-commands '(("cd\n" 0) ;; work in home dir
(". Xoper\n" 3) ;; run this script (wait 3 seconds)
("oper-pw\n" 3)) ;; send oper password (must read from /dev/tty)
"Oper Xterm" 1)) ;; name of compilation buffer,
;; kill the compilation buffer after the process ends
The sending of the pass word uses the fact that the compilation buffer
make a pseudo terminal that connects with the sub shell.
Ehud.
--
Ehud Karni Tel: +972-3-7966-561 /"\
Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign
Insurance agencies (USA) voice mail and X Against HTML Mail
http://www.mvs.co.il FAX: 1-815-5509341 / \
mailto:ehud@unix.mvs.co.il Better Safe Than Sorry
next prev parent reply other threads:[~2002-10-22 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iPgs9.26259$wU3.2299106@news0.telusplanet.net>
[not found] ` <200210200000.g9K00B5d021923@beta.mvs.co.il>
2002-10-20 16:59 ` M-x compile for different file extensions Richard Stallman
2002-10-20 18:07 ` Ehud Karni
2002-10-20 19:51 ` Stefan Monnier
2002-10-22 3:12 ` Richard Stallman
2002-10-22 6:46 ` Kai Großjohann
2002-10-22 17:17 ` Kevin Rodgers
2002-10-22 19:03 ` Ehud Karni
2002-10-23 7:11 ` Richard Stallman
2002-10-22 18:23 ` Ehud Karni [this message]
2002-10-23 7:10 ` Richard Stallman
2002-10-20 19:52 ` Stefan Monnier
2002-10-20 22:05 ` Ehud Karni
2002-10-22 3:12 ` Richard Stallman
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=200210221823.g9MIN6v0026498@beta.mvs.co.il \
--to=ehud@unix.mvs.co.il \
--cc=emacs-devel@gnu.org \
--cc=henrik+news@enberg.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).