Indeed. It appears that fish sets the terminal to something close to raw
mode, it still obeys ctrl-\, but not ctrl-d. There are more problems like
this when piping input or output to/from functions or block structures.
On Mon, Nov 21, 2011 at 14:59, DeathGorePain <
deathgorep...@users.sourceforge.net> wrote:
> Hello everybody,
>
> I have a slight problem, that this simple function can illustrate:
>
> *function writeIt
> set out /tmp/out.txt
> cat - > $out
> end*
>
> If the function is called in the shell, one cannot see the input, however
> *>cat /tmp/out.txt*
> outputs whatever one has input.
>
> If the function is added to *~/config/fish/config.fish *and called with
> *>fish -c "writeIt"*
> one can see their input, while typing.
>
> Could someone look into this please ?
>
> Regards,
> DeathGorePain
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Fish-users mailing list
> Fish-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fish-users
>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
