|
From: | gojjoe |
Subject: | bug#22615: 11.89.1; File Not found error... |
Date: | Thu, 11 Feb 2016 00:03:57 +0100 |
User-agent: | Thunderbird/666 |
Hi Mosè,Thank you very much for your interest in this. Unfortunately I've never managed to pinpoint where the spaces are creating the problem; as you say, paths with spaces don't cause problems in other settings handled by 'start-process'... That's also why I've never submitted this bug. Could it be the function that retrieves the GS path? I'll take a look once more and let you know (it'll take a couple of days).
Cheers! J On 20160210 23:39, Mosè Giordano wrote:
2016-02-10 17:52 GMT+01:00 <address@hidden>:Hi Shawn, Together with the problem you describe, do you also find that a shell buffer has been opened? In my case the problem was the 'preview-gs-command' variable: I set it using short-path notation: "c:\\PROGRA~1\\GS\\BIN\\GSWIN32C.EXE", and I got rid of that problem. Possibly it's because spaces in the standard string set up by AUCTeX aren't escaped properly...Thanks for this information. Do you know exactly where the error is triggered? The only possible place I found was `preview-gs-restart', but `start-process' should be smart enough to properly handle arguments with spaces in them. Bye, Mosè
[Prev in Thread] | Current Thread | [Next in Thread] |