On 2/2/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > Can't win them all, I guess. I've been thinking about what might be > causing this - and I have a theory. It might be that the code that > puts the child process into it's own process group is the culprit - > the child loops over sleep(0) until the parent gives it it's own > group. To test this theory, one simply has to turn of job control, > using 'status --job-control=none'. Could you test if this fixes your > problem?
That does seem to fix the prompt problem. But doing some more testing, I get all sorts of weird problems with this tarball. Things that worked fine connected to the machine over ssh now cause problems when running fish in Terminal. It turns out that fish_pager isn't fixed after all. I still get SIGBUS when I hit space in any fish_pager at 100%. And fish_pager goes nuts trying to list the contents of a directory - we're talking 65-80% CPU. This last problem seems to be new in this tarball - 1.20.1 has no such problem. The version of fish from this tarball also goes nuts when it's executed as the first process in an empty terminal (IE, as the shell). Again, fish 1.20.1 and 1.20.0 didn't do this. Not sure what's going on here. -- -Nick Pilon ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
