2011/1/10 Jason Rumney <jas...@gnu.org>:
> On 10/01/2011 05:43, Lennart Borgman wrote:
>
>> We have discussed this before on the Emacs Devel list. My conclusion
>> was that the windows version (i.e. emacsclientw.exe) should not wait -
>> because if it does that gives problems for some programs starting it
>> since you can not give the switch --no-wait in all such cases. (Not
>> for cmd.exe though.)
>>
>
> Which programs are these? I am not aware of any programs that have a
> problem if the external editor which they launch does not terminate
> until the user is finished editing. I do know that not waiting causes
> problems for many programs which use termination of the editor they
> spawned to mean the file they requested to be edited is ready.

Hm, forgotten at the moment. I think I have seen this in either "it's
all text" for firefox or the corresponding support for google chrome.
Or was it the downloaded page (C-j) in google chrome that did not
permit adding a parameter. I think at leas the last one.

>> Unfortunately I have not time to check such things over and over again
>> and fix them so I would be glad if this was changed in Emacs sources
>> instead of my Emacs+EmacsW32 distribution. The patch is needed, at
>> least in some cases.
>>
>
> It is wrong, at least in some cases.

I think we agree on this, or? ;-)

Reply via email to