all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: dick.r.chiang@gmail.com
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Ihor Radchenko <yantar92@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Really noninteractive
Date: Fri, 21 Feb 2020 08:20:48 -0500	[thread overview]
Message-ID: <CAM-tV--E-_NaoWZkx7+ZqxynZJzXTPRHPJ7UbhvrhCK8KNc=cw@mail.gmail.com> (raw)
In-Reply-To: <87a75dgjl4.fsf@dick>

On Thu, 20 Feb 2020 at 14:11, <dick.r.chiang@gmail.com> wrote:
>
> LI> Yes, but that's not what I want.  :-) I want to say "this function call,
> LI> in this otherwise totally normal Emacs, should not prompt".
>
> Okay, so you've established that `noninteractive` only diverts "normal emacs"
> to call `read_minibuf_noninteractive()` which in turn attempts to get input
> from stdin

See, I assumed this as well after reading the prior messages of this
thread. But I just tried it out now, and it actually does not do any
diversion. I'm actually not entirely sure why, I guess changes to the
`noninteractive' variable from lisp don't reach the C level?

So the redirection of stdin only helps in the --batch case.



  reply	other threads:[~2020-02-21 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 14:39 Really noninteractive Lars Ingebrigtsen
2020-02-20 15:23 ` Andreas Schwab
2020-02-20 17:42   ` Lars Ingebrigtsen
2020-02-24  9:16     ` Andreas Schwab
2020-02-24 12:55       ` Noam Postavsky
2020-02-24 13:03         ` Lars Ingebrigtsen
2020-02-20 19:05   ` Clément Pit-Claudel
2020-02-20 15:32 ` Ihor Radchenko
2020-02-20 17:42   ` Lars Ingebrigtsen
2020-02-20 17:56     ` Noam Postavsky
2020-02-20 18:36       ` Lars Ingebrigtsen
2020-02-20 19:11         ` dick.r.chiang
2020-02-21 13:20           ` Noam Postavsky [this message]
2020-02-21 14:11             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM-tV--E-_NaoWZkx7+ZqxynZJzXTPRHPJ7UbhvrhCK8KNc=cw@mail.gmail.com' \
    --to=npostavs@gmail.com \
    --cc=dick.r.chiang@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=yantar92@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.