tty

This question already has an answer here: Trick an application into thinking its stdout is a terminal, not a pipe 8 answers Whenever I use grep , and I pipe it to an other program, the --color option is not respected. I know I could use --color=always , but It also comes up with some other commands that I would like to get the exact output of that command as the output I would get if I was in a tty. So my question is, is it possible to trick a command into thinking that the command is run inside a tty ? For example, running grep --color word file # Outputs some colors grep --color word file |

I'm looking for the Perl equivalent to this Python code: from sys import stdout if stdout.isatty(): print "yes" else: print "no" Use the -t filetest operator . print -t STDOUT ? "Yes\n" : "No\n" Note that in Perl, STDOUT can be tied (essentially an overcomplicated overloaded object) so output to STDOUT may still reach a TTY even if its not directly attached to one. Use IO::interactive if you require STDOUT to actually be connected to the terminal, and not just being redirected to /dev/null/ or whatever. 来源： https://stackoverflow.com/questions/3517250/how-do-i-detect-if-stdout-is-connected-to-a

Problem: vagrant up fails with the error below. I am running vagrant on Windows 7 and the base box is Ubuntu )( files.vagrantup.com/precise32.box ). how can it be fixed? vagrant.bat up Bringing machine 'default' up with 'virtualbox' provider... [default] Clearing any previously set forwarded ports... [default] Clearing any previously set network interfaces... [default] Available bridged network interfaces: 1) Intel(R) PRO/1000 EB Network Connection with I/O Acceleration 2) Intel(R) PRO/1000 PL Network Connection Vagrant is attempting to interface with the UI in a way that requires a TTY. Most

When issuing grunt shell:test , I'm getting warning "the input device is not a TTY" & don't want to have to use -f : $ grunt shell:test Running "shell:test" (shell) task the input device is not a TTY Warning: Command failed: /bin/sh -c ./run.sh npm test the input device is not a TTY Use --force to continue. Aborted due to warnings. Here's the Gruntfile.js command: shell: { test: { command: './run.sh npm test' } Here's run.sh : #!/bin/sh # should use the latest available image to validate, but not LATEST if [ -f .env ]; then RUN_ENV_FILE='--env-file .env' fi docker run $RUN_ENV_FILE -it --rm -

Abstract: How to run an interactive task in background? Details: I am trying to run this simple script under ash shell (Busybox) as a background task. myscript.sh& However the script stops immediately... [1]+ Stopped (tty input) myscript.sh The myscript.sh contents... (only the relvant part, other then that I trap SIGINT, SIGHUP etc) #!/bin/sh catpid=0 START_COPY() { cat /dev/charfile > /path/outfile & catpid = $! } STOP_COPY() { kill catpid } netcat SOME_IP PORT | while read EVENT do case $EVENT in start) START_COPY;; stop) STOP_COPY;; esac done From simple command line tests I found that bot

I am reading bytes from a serial port in C++ using a file descriptor and the posix/unix read() function. In this example, I am reading 1 byte from the serial port (baud rate settings and similiar are omitted for clarity): #include <termios.h> #include <fcntl.h> #include <unistd.h> int main(void) { int fd = open("/dev/ttyS0", O_RDWR | O_NOCTTY); char buf[1]; int bytesRead = read(fd, buf, 1); close(fd); return 0; } If the device connected to /dev/ttyS0 does not send any information, the program will hang. How can I set a timeout? I have tried setting a time out like this: struct termios options;

I would like to write a simple C program that will perform different actions based on both "key down" and "key up" events. This program will be run from inside rxvt . What library or mechanism should I use to access both key presses and releases? Is it true that reading /dev/tty will only provide key releases? Is this also true for termcap, terminfo, ncurses, and slang? Is there a way to achieve this from within a terminal application? The following links may be of some assistance in using the keyboard raw mode which will give you access to the keyboard events rather than just key releases.