From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Ehud Karni" Newsgroups: gmane.emacs.devel Subject: Re: M-x compile for different file extensions Date: Tue, 22 Oct 2002 20:23:06 +0200 Organization: Mivtach-Simon Insurance agencies Sender: emacs-devel-admin@gnu.org Message-ID: <200210221823.g9MIN6v0026498@beta.mvs.co.il> References: <200210200000.g9K00B5d021923@beta.mvs.co.il> <200210201807.g9KI7H02011888@beta.mvs.co.il> Reply-To: ehud@unix.mvs.co.il NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035310975 15425 80.91.224.249 (22 Oct 2002 18:22:55 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 22 Oct 2002 18:22:55 +0000 (UTC) Cc: henrik+news@enberg.org, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1843g6-00040W-00 for ; Tue, 22 Oct 2002 20:22:54 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 1843hQ-0007R7-00 for ; Tue, 22 Oct 2002 20:24:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 1843fS-0000Un-00; Tue, 22 Oct 2002 14:22:14 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 1843f2-0000M8-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 14:21:48 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 1843f0-0000LX-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 14:21:48 -0400 Original-Received: from unix.sw.co.il ([192.114.178.12] helo=unix.mvs.co.il) by monty-python.gnu.org with esmtp (Exim 4.10) id 1843ez-0000IB-00; Tue, 22 Oct 2002 14:21:45 -0400 Original-Received: from beta.mvs.co.il (beta [10.253.0.3]) by unix.mvs.co.il (8.11.6/8.11.6) with ESMTP id g9MILbh10323; Tue, 22 Oct 2002 20:21:37 +0200 Original-Received: from beta.mvs.co.il (localhost [127.0.0.1]) by beta.mvs.co.il (8.12.5/8.12.5) with ESMTP id g9MIN8ed026504; Tue, 22 Oct 2002 20:23:09 +0200 Original-Received: (from ehud@localhost) by beta.mvs.co.il (8.12.5/8.12.5/Submit) id g9MIN6v0026498; Tue, 22 Oct 2002 20:23:06 +0200 X-Authentication-Warning: beta.mvs.co.il: ehud set sender to ehud@unix.mvs.co.il using -f Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Mon, 21 Oct 2002 23:12:29 -0400) X-Mailer: Emacs 21.2.91.3 rmail (send-msg 1.106) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:8661 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8661 On Mon, 21 Oct 2002 23:12:29 -0400, Richard Stallman 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