unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: run emacs in batch mode without a tty
Date: Fri, 3 Jul 2015 03:28:11 -0700 (PDT)	[thread overview]
Message-ID: <7caedaf5-4461-4de4-9f3f-e911453c60f3@googlegroups.com> (raw)
In-Reply-To: <mailman.6225.1435919180.904.help-gnu-emacs@gnu.org>

Hi, you're right... it's not possible to ssh in and check this stuff but it is possible to run a script in the environment to check that there are no pseudo terminals either (/dev/pty*)

On Friday, 3 July 2015 11:26:22 UTC+1, to...@tuxteam.de  wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Fri, Jul 03, 2015 at 02:14:58AM -0700, Sam Halliday wrote:
> > Hi all,
> > 
> > I would like to run my elisp unit tests in a docker container, but my CI doesn't let me enable a tty when I'm doing this.
> > 
> > Given that the tests would only be using a dumb terminal anyway, it really just needs to be mocked out, but I don't have anything under `/dev/tty*`
> 
> Bah. Those young'uns re-inventing all wheels at once. No /dev/tty* ;-)
> 
> Do you see a /dev/pty* or /dev/ptmx?
> 
> Note that if there are no ptys probably other things won't work
> (ssh comes to mind).
> 
> regards
> - -- tomás
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iEYEARECAAYFAlWWY0AACgkQBcgs9XrR2kb1MgCfVkFfsR6naDKG3OSm0+xP3lgg
> TikAoIFkfsLqkkvnNHYpN9Uny1/UgMUZ
> =/AiX
> -----END PGP SIGNATURE-----



  parent reply	other threads:[~2015-07-03 10:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  9:14 run emacs in batch mode without a tty Sam Halliday
2015-07-03 10:26 ` tomas
     [not found] ` <mailman.6225.1435919180.904.help-gnu-emacs@gnu.org>
2015-07-03 10:28   ` Sam Halliday [this message]
2015-07-03 10:45     ` tomas
     [not found]     ` <mailman.6226.1435920329.904.help-gnu-emacs@gnu.org>
2015-07-03 13:27       ` Sam Halliday
2015-07-04  8:30         ` tomas
2015-07-03 12:00 ` Eli Zaretskii
     [not found] ` <mailman.6230.1435924859.904.help-gnu-emacs@gnu.org>
2015-07-03 13:26   ` Sam Halliday
2015-07-03 13:51     ` Eli Zaretskii
2015-07-04  6:56       ` Steinar Bang
2015-07-04  7:32         ` Eli Zaretskii
     [not found]     ` <mailman.6240.1435931463.904.help-gnu-emacs@gnu.org>
2015-07-03 15:07       ` Barry Margolin
2015-07-03 17:48         ` Eli Zaretskii
2015-07-03 20:13         ` Emanuel Berg
2015-07-03 15:42       ` Sam Halliday
2015-07-03 16:29         ` Sam Halliday
2015-07-03 17:51         ` Eli Zaretskii
2015-07-03 17:07       ` Sam Halliday
2015-07-03 20:14         ` Eli Zaretskii
     [not found]         ` <mailman.6254.1435954474.904.help-gnu-emacs@gnu.org>
2015-07-03 20:43           ` Sam Halliday
2015-07-03 21:25             ` Sam Halliday
2015-07-03 21:52               ` Sam Halliday
2015-07-03 22:01                 ` Sam Halliday
2015-07-04  7:42                   ` Eli Zaretskii
2015-07-03 22:55               ` Barry Margolin
2015-07-03 23:56                 ` Sam Halliday
2015-07-04  7:37                 ` Eli Zaretskii
2015-07-04  7:44               ` Eli Zaretskii
2015-07-04  7:45             ` 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=7caedaf5-4461-4de4-9f3f-e911453c60f3@googlegroups.com \
    --to=sam.halliday@gmail.com \
    --cc=help-gnu-emacs@gnu.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.
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).