(defun python-preoutput-filter (s)
`comint-preoutput-filter-functions' function: ignore prompts not at
bol.
(cond ((and (string-match (rx (and string-start (repeat 3 (any .))
I see you've reverted to the basic code and thus removed the while loop
I had added.
I guess it's OK so
On Mar 27, 2005, at 9:50 AM, Stefan Monnier wrote:
I couldn't get your patch to work. However, I did see what was going
on
and I managed to write my own patch. I don't know if this could break
anything else, but it does fix my OS X completion problems.
Thanks, I'll install it later.
From my
On Mar 26, 2005, at 12:51 PM, Steven Huwig wrote:
That had no effect on the behavior. I guess it must actually be
an issue with the size of the incoming data vs. some buffer size
in the C code ... does this sound plausible? I will write up some
scripts to incrementally generate and test Python
On Mar 26, 2005, at 5:10 PM, Stefan Monnier wrote:
Maybe you could add a `message' at the beginning of
python-preoutput-filter,
to see what the process filter actually receives. Or maybe even at the
beginning of comint-output-filter.
Stefan
Curiouser and curiouser. I put a message in
Curiouser and curiouser. I put a message in
python-preoutput-filter that echoes its parameter as you
suggest. Looking at the contents of my messages buffer after
attempting the completion for os., the Can't find completion
message from the python completion routine happens after
precisely
On Mar 26, 2005, at 8:05 PM, Stefan Monnier wrote:
Curiouser and curiouser. I put a message in
python-preoutput-filter that echoes its parameter as you
suggest. Looking at the contents of my messages buffer after
attempting the completion for os., the Can't find completion
message from the python
