> I don't believe the problem as you've described it is even possible. Which > does not mean I > believe you're not seeing a problem. Only that the problem statement is > incomplete or inaccurate.
I'm not sure what you mean. I think I do had a problem, 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 On Tue, Dec 15, 2015, at 04:23 AM, Kurtis Rader wrote: > On Mon, Dec 14, 2015 at 12:35 AM, ben yakawp <ben.li...@yakawp.com> > wrote: > > > > I'd like to report a strange behaviour with fish shell in tmux. > > > > In Tmux you can define a default shell that is used in every new window. > > My default shell is fish which runs without any problems so far. The > > default shell fish is used only interactively, all scripts are ran by > > bash. > > > > Where the problem begins: > > - with tmux I split the current window > > - with the split I also run a command which in this case is a bash > > script which reads user input, like > > ~~~~~~~~~~~ > > #!/bin/bash > > read input > > echo $input > > ~~~~~~~~~~~ > > > > - the user input is not echoed and more importantly, Carriage return is > > not processed. > > > > I can't reproduce this problem on Mac OS X or Ubuntu server 14.04. > Furthermore, as someone who has recently carefully read the relevant fish > code and modified it (to allow binding \n separate from \r) I don't > believe > the problem as you've described it is even possible. Which does not mean > I > believe you're not seeing a problem. Only that the problem statement is > incomplete or inaccurate. > > > > - if I put 'stty echo' at the first line Carriage Return is echoed as > > '^M' but still not processed > > > > What do you see if you run "stty -a" from a fish prompt? I'm betting it > shows that the "echo" option is enabled. > > Are you by any chance using the "exec" command to execute that bash > script? > That shouldn't cause any problems unless you're running a custom built > fish > shell with my very recent change that disables ICRNL mode. And even if > you > were it would not affect the echoing of the characters you typed as you > ran > that bash script. > > -- > 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
