> I agree that you have a problem. But I think your diagnosis of the > problem is incorrect I'm not aware of any diagnosis in my original message, if so it wasn't my intention but rather a misunderstanding caused by my lacking English skills.
> What happens if you create a file with > that conten, make it executable with "chmod 755", t and execute it from a > fish prompt? Do you see the characters you type echoed? Is the [enter] > key You have to believe me I've tried every combination of tmux default shell vs. non interactive shell from the script. The only case where it didn't work with literally this script (I've tested excactly this content), ran with the 'tmux split-window "./t.sh" command. It worked when I called the script manually from a fish shell, but not in the tmux context. On Wed, Dec 16, 2015, at 04:53 AM, Kurtis Rader wrote: > On Tue, Dec 15, 2015 at 5:46 AM, ben yakawp <ben.li...@yakawp.com> wrote: > > > > I'm not sure what you mean. I think I do had a problem, > > > I agree that you have a problem. But I think your diagnosis of the > problem > is incorrect. > > > > but from what I > > understand now, it was not caused by an error or anything but was a > > consequence of a behaviour on how fish preserves tty modes between > > commands ( see the answer of Mike Meyer with the link to > > https://github.com/fish-shell/fish-shell/pull/2317 ). > > > > > What do you see if you run "stty -a" from a fish prompt? > > > > speed 38400 baud; rows 31; columns 113; line = 0; > > intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; > > eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt > > = ^R; > > werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; > > -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts > > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon > > -ixoff > > -iuclc -ixany -imaxbel iutf8 > > opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 > > vt0 ff0 > > isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop > > -echoprt > > echoctl echoke > > > > The "stty -a" you ran is an external command like the bash script you > mentioned. Both of them would have had the same terminal modes. You can > see > from your "stty -a" output that "echo" mode is enabled. So there is > something else going on that you haven't documented. You say > > > with the split I also run a command which in this case is a bash script > which reads user input, like > > When you say "reads input, like" I conclude your example script is meant > as > an approximation of the real script. What happens if you create a file > with > that conten, make it executable with "chmod 755", t and execute it from a > fish prompt? Do you see the characters you type echoed? Is the [enter] > key > (carriage-return) correctly handled? > > It also seems to me from your description of the problem like the bash > script that is failing is executed automatically based on a tmux or fish > config file rather than interactively entering the script name at a fish > prompt. Regardless of whether the answer is yes or no we need > clarification. Ideally you should be able to provide sufficient detail > that > someone else can reproduce the problem. > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank ------------------------------------------------------------------------------ _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
