From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: Re: flycheck orgmode on windows invalid output file name Date: Sun, 05 Jun 2016 18:25:31 +0300 Message-ID: <83ziqzu07o.fsf@gnu.org> References: <86shwrkj6u.fsf@gmail.com> Reply-To: Eli Zaretskii Return-path: In-reply-to: <86shwrkj6u.fsf@gmail.com> (message from Guido Van Hoecke on Sun, 05 Jun 2016 12:45:45 +0200) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sender: "help-gnu-emacs" To: help-gnu-emacs@gnu.org Cc: emacs-orgmode@gnu.org List-Id: emacs-orgmode.gnu.org > From: Guido Van Hoecke > Date: Sun, 05 Jun 2016 12:45:45 +0200 > > Error while checking syntax automatically: (file-error "Opening output file" "Invalid argument" "c:/Users/guivh/emacs-guivho/.flycheck_emacs-guivho.org[*Org Src emacs-guivho.org[ emacs-lisp ]*]") > > I checked the windows only issues but did not see something similar. > > Apparently flycheck has a problem with the fact that the buffer does not > correspond to a physical file. No, I think the problem is that flycheck assumes it can create a file whose name includes '*', which is false on Windows. > I hope there is a known or suggested workaround... If I'm right, the only solution is to modify flycheck so that it runs the file name through convert-standard-filename.