github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-12-19 13:33:38 +08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
5c8b6adc2c
fish-shell/tests/pexpects/isatty.py

67 lines
1.2 KiB
Python
Raw Normal View History

builtin test: Let `-t` work for the standard streams Since builtins don't actually have the streams connected, but instead read input via the io_streams_t objects, this would just always say what *fish's* fds were. Instead, pass along some of the stream data to check those specifically - nobody cares that `test`s fd 0 *technically* is stdin. What they want to know is that, if they used another program in that place, it would connect to the TTY. This is pretty hacky - I abused static variables for this, but since it's two bools and an int it's probably okay. See #1228. Fixes #4766.
2020-09-17 00:22:12 +08:00
#!/usr/bin/env python3
from pexpect_helper import SpawnedProc
sp = SpawnedProc()
send, sendline, sleep, expect_prompt, expect_re, expect_str = (
sp.send,
sp.sendline,
sp.sleep,
sp.expect_prompt,
sp.expect_re,
sp.expect_str,
)
expect_prompt()
sendline("test -t 0; echo $status")
expect_prompt("0")
Reformat
2020-11-22 21:39:48 +08:00
sendline(
"""function t
builtin test: Let `-t` work for the standard streams Since builtins don't actually have the streams connected, but instead read input via the io_streams_t objects, this would just always say what *fish's* fds were. Instead, pass along some of the stream data to check those specifically - nobody cares that `test`s fd 0 *technically* is stdin. What they want to know is that, if they used another program in that place, it would connect to the TTY. This is pretty hacky - I abused static variables for this, but since it's two bools and an int it's probably okay. See #1228. Fixes #4766.
2020-09-17 00:22:12 +08:00
test -t 0 && echo stdin
test -t 1 && echo stdout
test -t 2 && echo stderr
Reformat
2020-11-22 21:39:48 +08:00
end"""
)
builtin test: Let `-t` work for the standard streams Since builtins don't actually have the streams connected, but instead read input via the io_streams_t objects, this would just always say what *fish's* fds were. Instead, pass along some of the stream data to check those specifically - nobody cares that `test`s fd 0 *technically* is stdin. What they want to know is that, if they used another program in that place, it would connect to the TTY. This is pretty hacky - I abused static variables for this, but since it's two bools and an int it's probably okay. See #1228. Fixes #4766.
2020-09-17 00:22:12 +08:00
expect_prompt()
sendline("t")
expect_str("stdin")
expect_str("stdout")
expect_str("stderr")
expect_prompt()
sendline("cat </dev/null | t")
expect_str("stdout")
expect_str("stderr")
expect_prompt()
sendline("t | cat")
expect_str("stdin")
expect_str("stderr")
expect_prompt()
sendline("t 2>| cat")
expect_str("stdin")
expect_str("stdout")
expect_prompt()
sendline("cat </dev/null | t | cat")
expect_str("stderr")
expect_prompt()
sendline("cat </dev/null | t 2>| cat")
expect_str("stdout")
expect_prompt()
sendline("t </dev/null")
expect_str("stdout")
expect_str("stderr")
expect_prompt()
Use the newly fixed `test -t` in isatty Removes a weird dependency on the test command.
2020-09-17 02:58:07 +08:00
sendline("isatty stdin && echo yes")
expect_str("yes")
expect_prompt()
sendline("cat </dev/null | isatty stdin || echo no")
expect_str("no")
expect_prompt()
Reference in New Issue Copy Permalink