RE: 21.4.13: ^c in shell now works, but now shell output only shows up when cursor moves

-----Original Message----- From: Ben Wing [mailto:ben＠xemacs.org] Karr, David wrote: >I have 21.4.13 set up on one box, and I'm setting up 21.4.13 on another >box, and copying over elements of the "init.el" from the first box. > >One annoyance I've had for a long time in shell mode is that ^c while >running an app in shell mode does not kill the app. I've tried to find >a solution to this for a long time, to no avail. I've just gotten used >to it. > >When I set up 21.4.13 on this new box, I got to a point where I >realized that ^c was killing the app. This was nice to see. > >However, now I see that apps that produce somewhat long-running output >are only producing blocks of output, only when I move the cursor. On >the old laptop (where ^c doesn't work), the output comes out normally. > >Are these two issues related? > maybe. there's lots of black magic out there you need to do when working with tty's and ^c, and it varies from system to system. if your two boxes have different os's or different linux installations or maybe even different versions of the same installation, they might have different config flags. are you compiling yourself? if so, check the config.h files that were produced; do a diff on the files from your two boxes and see if there's anything different, esp. in the following settings: /* Many flavors of PTY support */ #undef HAVE_GETPT /* glibc's easy pty allocation function */ #undef HAVE__GETPTY /* SGI's easy pty allocation function */ #undef HAVE_OPENPTY /* BSD's easy pty allocation function */ #undef HAVE_GRANTPT /* Unix98 */ #undef HAVE_UNLOCKPT /* Unix98 */ #undef HAVE_PTSNAME /* Unix98 */ #undef HAVE_KILLPG /* BSD */ #undef HAVE_TCGETPGRP /* Posix 1 */ #undef HAVE_ISASTREAM /* SysV streams */ #undef HAVE_SYS_PTY_H /* AIX */ #undef HAVE_SYS_PTYIO_H /* HP-UX */ #undef HAVE_PTY_H /* Linux, Tru64 */ #undef HAVE_LIBUTIL_H /* BSD openpty */ #undef HAVE_UTIL_H /* NetBSD openpty */ #undef HAVE_STROPTS_H /* SysV streams */ #undef HAVE_STRTIO_H /* SysV streams TIOCSIGNAL */ #undef HAVE_TERMIOS #undef HAVE_TERMIO #undef NO_TERMIO #undef SIGNALS_VIA_CHARACTERS > I'm not sure which problem is more >annoying. Is there something I can do to fix the "blocky output" >problem? > it might be a misconfiguration of one of the above values (or maybe some other value). does it happen on 21.4.18 too?