unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: polymath@uwyo.edu, emacs-devel@gnu.org
Subject: Re: Sesquicolon -- Note: Not a Bug
Date: Mon, 26 Aug 2002 15:51:56 -0600 (MDT)	[thread overview]
Message-ID: <200208262151.g7QLpuX12815@wijiji.santafe.edu> (raw)
In-Reply-To: <buo8z2ul71p.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 26 Aug 2002 10:53:22 +0900)

    > Would that do the job?  I don't know the precise rules of what #! can
    > do.  If that would do the job, it is a fine solution.  We could call
    > it --script.

    To the best of my knowledge, you're allowed exactly one option (which
    will go before the filename).

Are you saying that Emacs would be called with two arguments,
the option and a file name?

If so, we should not use -batch for this.  To special-case the
combination of --batch and a file name is a double-level kludge,
because each of those arguments normally has a different and
incompatible meaning.  For the combination of the two to do something
special is too inconsistent.

Let's make a new option --script for this purpose.

  reply	other threads:[~2002-08-26 21:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.10.10208230008380.5847-100000@asuwlink.uwyo.edu>
2002-08-25  5:26 ` Sesquicolon -- Note: Not a Bug Richard Stallman
2002-08-25  5:37   ` Miles Bader
2002-08-25 10:01     ` Marius Vollmer
2002-08-26 12:53       ` Richard Stallman
2002-08-26 21:19         ` Marius Vollmer
2002-08-26 22:08           ` Stefan Monnier
2002-08-26  0:36     ` Richard Stallman
2002-08-26  1:53       ` Miles Bader
2002-08-26 21:51         ` Richard Stallman [this message]
2002-08-26 22:15           ` Stefan Monnier
2002-08-27  9:28             ` Kim F. Storm
2002-08-31 12:17           ` Pavel Janík
2002-09-01 13:15             ` Richard Stallman
2002-09-04 17:33               ` Pavel Janík
2002-08-25 18:52   ` Stefan Monnier

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=200208262151.g7QLpuX12815@wijiji.santafe.edu \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=polymath@uwyo.edu \
    /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).