unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: "Андрей Парамонов" <cmr.pent@gmail.com>
Cc: 28166@debbugs.gnu.org
Subject: bug#28166: 25.2; Batch mode not perfectly noninteractive
Date: Sun, 20 Aug 2017 23:28:21 -0400	[thread overview]
Message-ID: <87y3qdbnvu.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAC4Co6Oaz3VGWhe0dmNt9O1FFx-G_Qd5nCsWHvan577+vk4HNA@mail.gmail.com> ("Андрей Парамонов"'s message of "Mon, 21 Aug 2017 05:42:39 +0300")

Андрей Парамонов <cmr.pent@gmail.com> writes:

> I thought that "noninteractive" means precisely:
> do not read from keyboard.
>
> However I'm not sure now. How do other (e.g Lisp) interpreters behave
> in similar circumstances?

sbcl has a --non-interactive option, it doesn't disable reading from
stdin.  It basically just prevents the REPL from starting.  I think this
is analogous to Emacs' --batch/--script option preventing the command
loop from starting.

    ~/tmp$ cat read-line.lisp 
    (read-line)
    ~/tmp$ sbcl --script read-line.lisp --non-interactive
    [waiting for input here...]
    ~/tmp$ sbcl --help
    Usage: sbcl [runtime-options] [toplevel-options] [user-options]
      [...]
      --disable-debugger         Invoke sb-ext:disable-debugger.
      --noprint                  Run a Read-Eval Loop without printing results.
      --script [<filename>]      Skip #! line, disable debugger, avoid verbosity.
      --quit                     Exit with code 0 after option processing.
      --non-interactive          Sets both --quit and --disable-debugger.
      [...]





  reply	other threads:[~2017-08-21  3:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20 19:52 bug#28166: 25.2; Batch mode not perfectly noninteractive Андрей Парамонов
2017-08-20 20:13 ` npostavs
2017-08-21  1:15   ` Андрей Парамонов
2017-08-21  2:30     ` Eli Zaretskii
2017-08-21  2:42       ` Андрей Парамонов
2017-08-21  3:28         ` npostavs [this message]
2017-08-21  7:49         ` Andreas Schwab
2017-08-21  7:52           ` Андрей Парамонов
2017-08-21 14:16             ` Eli Zaretskii

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=87y3qdbnvu.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=28166@debbugs.gnu.org \
    --cc=cmr.pent@gmail.com \
    /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).