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
