From: Andreas Schwab <schwab@suse.de>
To: rms@gnu.org
Cc: cyd@stupidchicken.com, Reiner Steib <Reiner.Steib@gmx.de>,
emacs-devel@gnu.org
Subject: Re: 22.1.92; Tutorial: references to non-existing info nodes
Date: Wed, 12 Mar 2008 16:34:49 +0100 [thread overview]
Message-ID: <jeve3sarc6.fsf@sykes.suse.de> (raw)
In-Reply-To: <E1JZScd-0000ef-8O@fencepost.gnu.org> (Richard Stallman's message of "Wed\, 12 Mar 2008 11\:12\:03 -0400")
Richard Stallman <rms@gnu.org> writes:
> | Another explanation of the problem I found is that under the console
> | C-s disables input and C-q reenables it - which indeed is the case,
> | but doesn't make much sense under a xterminal, does it?
>
> Does this qualify as flow control problem?
>
> I don't think so. It looks like he has encountered the fact that C-s
> and C-q _typed by the user_ operate as commands that turn output off
> and on.
This is the same XON/XOFF (software) flow control, whether typed by the
user or generated by a terminal is not relevant.
> The solution is simply to turn off their effect (and I think
> Emacs does that in sysdep.c, so why isn't it working?).
The OP in the cited thread had that explicitly enabled due to a
misunderstanding.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-03-12 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 20:32 22.1.92; Tutorial: references to non-existing info nodes Reiner Steib
2008-03-10 22:09 ` Andreas Schwab
2008-03-11 21:00 ` Reiner Steib
2008-03-12 15:12 ` Richard Stallman
2008-03-12 23:10 ` Reiner Steib
2008-03-11 1:09 ` Chong Yidong
2008-03-11 20:57 ` Reiner Steib
2008-03-12 15:12 ` Richard Stallman
2008-03-12 15:34 ` Andreas Schwab [this message]
2008-03-12 20:03 ` Richard Stallman
2008-03-12 20:52 ` Andreas Schwab
2008-03-13 1:06 ` Richard Stallman
2008-03-12 13:41 ` Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeve3sarc6.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Reiner.Steib@gmx.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).