I don't know why, but when I run ls alone on a line (in my daudin directory) a TAB is in the output. The ls runs in a pseudo-tty and it seems that a TAB really does come back from the master pty desciptor. So I must be doing something wrong somewhere. This doesn't apply when ls is piped into another command because in that case a pseudo-tty isn't used. The ls output prints just fine with the embedded TAB, but how did it get there? It's hard to figure out what's going on because you can't just pipe into something (like od -a) from the shell because then ls changes its behavior. Can it be that there really is a TAB in the ls output in a pseudotty?
I don't know why, but when I run
ls
alone on a line (in my daudin directory) a TAB is in the output. Thels
runs in a pseudo-tty and it seems that a TAB really does come back from the master pty desciptor. So I must be doing something wrong somewhere. This doesn't apply whenls
is piped into another command because in that case a pseudo-tty isn't used. The ls output prints just fine with the embedded TAB, but how did it get there? It's hard to figure out what's going on because you can't just pipe into something (likeod -a
) from the shell because thenls
changes its behavior. Can it be that there really is a TAB in thels
output in a pseudotty?