[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: called by a process filter?
From: |
Richard Stallman |
Subject: |
Re: called by a process filter? |
Date: |
Fri, 13 May 2005 20:25:34 -0400 |
> If something looks at this-command inside a process filter, it is
> probably broken already. In general it is unpredictable what command
> is running, or was just running, when the process filter is called.
> So such code would currently get unpredictable results.
True.
We should set this-command to nil while we a reading a key sequence at
the top level (and thus may run anync code).
That would be a clean approach.
As for this-process, it would be clean and safe, but at present there
is no clear need to add it.
- Re: called by a process filter?, (continued)
- Re: called by a process filter?, Richard Stallman, 2005/05/12
- Re: called by a process filter?, Kim F. Storm, 2005/05/12
- Re: called by a process filter?, Stefan Monnier, 2005/05/12
- Re: called by a process filter?, Kim F. Storm, 2005/05/12
- Re: called by a process filter?, Stefan Monnier, 2005/05/12
- Re: called by a process filter?, Kevin Rodgers, 2005/05/12
- Re: called by a process filter?, Kim F. Storm, 2005/05/13
- Re: called by a process filter?, Richard Stallman, 2005/05/12
- Re: called by a process filter?, Kim F. Storm, 2005/05/13
- Re: called by a process filter?,
Richard Stallman <=