[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#727: compilation-disable-input
From: |
Perry Smith |
Subject: |
bug#727: compilation-disable-input |
Date: |
Thu, 14 Aug 2008 16:17:26 -0500 |
I'm not sure what this is intended to do. Sending just one EOF
character to a process creates one EOF if many conditions are met.
But a second read from the same pty will continue to look for input.
The following code:
(when compilation-disable-input
(condition-case nil
(process-send-eof proc)
;; The process may have exited already.
(error nil)))
Causes my grep buffer to start with a ^D (the EOF character that
process-send-eof sends). This goofs up the parsing of the lines.
If you really do not want input, you need to close stdin. This could
be done in various ways but this is not the way to do it.
Perry Smith
pedzan@austin.ibm.com
- bug#727: compilation-disable-input,
Perry Smith <=