Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:131004
Precedence: list
MIME-Version: 1.0
Date: Sun, 24 May 2026 22:49:43 +0545
Message-ID: <CA+9BsNdJoYLiS8Td5PQiDcxkipobk6s6m4Gixex96k-i7zERxQ@mail.gmail.com>
Subject: [PHP-DEV] [Discussion] Native terminal helpers for PHP CLI
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000dd9f3c0652934200"
From: prateekbhujelpb@gmail.com (Pratik Bhujel)

--000000000000dd9f3c0652934200
Content-Type: text/plain; charset="UTF-8"

Hi internals,

I have been experimenting with a small PHP extension for native terminal
helpers:

https://github.com/prateekbhujel/php-terminal

The goal is to expose a small cross-platform CLI terminal layer for the
pieces that are currently awkward to normalize in userland, especially on
Windows:

- checking whether stdin/stdout/stderr are TTYs
- reading terminal size
- enabling/restoring raw mode safely
- reading a single key with normalized names
- writing directly to stdout/stderr

This started from a practical issue with prompt-style PHP CLIs. Laravel
Prompts, for example, currently cannot use its normal interactive prompt
flow on Windows because the backend depends on Unix-style terminal
behavior. I opened a proof-of-concept integration here:

https://github.com/laravel/prompts/pull/242

The extension is still alpha, and I am not proposing it for core right
now. I mainly want feedback on whether this API shape makes sense from a
PHP CLI/runtime point of view, and whether this is better kept as
PECL/ecosystem work first.

Initial release with Windows builds:

https://github.com/prateekbhujel/php-terminal/releases/tag/v0.1.0

If this would be better discussed on internals-win first, I am happy to
move it there. I am mainly looking for feedback on API shape, naming,
Windows behavior, and missing primitives before taking it further.

Thanks,
Pratik

--000000000000dd9f3c0652934200
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi internals,<br><br>I have been experimenting with a smal=
l PHP extension for native terminal<br>helpers:<br><br><a href=3D"https://g=
ithub.com/prateekbhujel/php-terminal">https://github.com/prateekbhujel/php-=
terminal</a><br><br>The goal is to expose a small cross-platform CLI termin=
al layer for the<br>pieces that are currently awkward to normalize in userl=
and, especially on<br>Windows:<br><br>- checking whether stdin/stdout/stder=
r are TTYs<br>- reading terminal size<br>- enabling/restoring raw mode safe=
ly<br>- reading a single key with normalized names<br>- writing directly to=
 stdout/stderr<br><br>This started from a practical issue with prompt-style=
 PHP CLIs. Laravel<br>Prompts, for example, currently cannot use its normal=
 interactive prompt<br>flow on Windows because the backend depends on Unix-=
style terminal<br>behavior. I opened a proof-of-concept integration here:<b=
r><br><a href=3D"https://github.com/laravel/prompts/pull/242">https://githu=
b.com/laravel/prompts/pull/242</a><br><br>The extension is still alpha, and=
 I am not proposing it for core right<br>now. I mainly want feedback on whe=
ther this API shape makes sense from a<br>PHP CLI/runtime point of view, an=
d whether this is better kept as<br>PECL/ecosystem work first.<br><br>Initi=
al release with Windows builds:<br><br><a href=3D"https://github.com/pratee=
kbhujel/php-terminal/releases/tag/v0.1.0">https://github.com/prateekbhujel/=
php-terminal/releases/tag/v0.1.0</a><br><br>If this would be better discuss=
ed on internals-win first, I am happy to<br>move it there. I am mainly look=
ing for feedback on API shape, naming,<br>Windows behavior, and missing pri=
mitives before taking it further.<br><br>Thanks,<br>Pratik<br></div>

--000000000000dd9f3c0652934200--