Date: Tue, 26 Aug 2008 14:45:24 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: swell.k@gmail.com Cc: freebsd-current@freebsd.org, Ed Schouten <ed@freebsd.org> Subject: Re: Inserting flow-control chars with an mpsafetty kernel Message-ID: <878wuk3sq3.fsf@kobe.laptop> In-Reply-To: <86abf0xazp.fsf@gmail.com> (swell k.'s message of "Tue, 26 Aug 2008 15:38:02 %2B0400") References: <87fxot5hoi.fsf@kobe.laptop> <86myj0xdou.fsf@gmail.com> <8763po58y9.fsf@kobe.laptop> <86abf0xazp.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Aug 2008 15:38:02 +0400, swell.k@gmail.com wrote: >Giorgos Keramidas <keramida@freebsd.org> writes: >> Yes. I was using screen when I tried this. Now that I tried outside >> of screen, C-s and C-q work in Emacs and ^V^S or ^V^Q works in >> /usr/bin/vi. >> >> Is this a known bug of screen? Are there already patches floating >> around to fix it? > > I don't know. What I know that it was way before mpsafetty was merged > in -current. It didn't really bother me to verify and report it since > I don't use non-windowed Emacs often enough. But from my observation > ^S/^Q do work in copy mode and it still present in screen.git too and > didn't fixed in mpsafetty-20080824.diff.gz. > > So it's just `me too', sorry. Fair enough, thanks for the tip about screen. At least now I know where to look for more details :D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?878wuk3sq3.fsf>