From: Guido Van Hoecke <guivho@gmail.com> To: Emacs <help-gnu-emacs@gnu.org> , orgmode <emacs-orgmode@gnu.org> Subject: flycheck orgmode on windows invalid output file name Date: Sun, 05 Jun 2016 12:45:45 +0200 [thread overview] Message-ID: <86shwrkj6u.fsf@gmail.com> (raw) Hi, Environment: Windows 10 (Insider preview 14352) GNU Emacs 25.0.92.1 (x86_64-w64-mingw32) of 2016-03-03 I just installed flycheck-20160604.154/ I read that it does not officially support windows 'although it should mostly work fine on Windows' And indeed flycheck works fine when editing .el, .js, .php et al. files. However, my emacs.el file is generated from an emacs-guivho.org file. When I issue C-' to edit an elisp code block, flycheck barks at me: 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. I hope there is a known or suggested workaround... TIA, -- Guido If you try to please everyone, somebody is not going to like it.
WARNING: multiple messages have this Message-ID (diff)
From: Guido Van Hoecke <guivho@gmail.com> To: Emacs <help-gnu-emacs@gnu.org>, orgmode <emacs-orgmode@gnu.org> Subject: flycheck orgmode on windows invalid output file name Date: Sun, 05 Jun 2016 12:45:45 +0200 [thread overview] Message-ID: <86shwrkj6u.fsf@gmail.com> (raw) Hi, Environment: Windows 10 (Insider preview 14352) GNU Emacs 25.0.92.1 (x86_64-w64-mingw32) of 2016-03-03 I just installed flycheck-20160604.154/ I read that it does not officially support windows 'although it should mostly work fine on Windows' And indeed flycheck works fine when editing .el, .js, .php et al. files. However, my emacs.el file is generated from an emacs-guivho.org file. When I issue C-' to edit an elisp code block, flycheck barks at me: 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. I hope there is a known or suggested workaround... TIA, -- Guido If you try to please everyone, somebody is not going to like it.
next reply other threads:[~2016-06-05 10:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-05 10:45 Guido Van Hoecke [this message] 2016-06-05 10:45 ` flycheck orgmode on windows invalid output file name Guido Van Hoecke 2016-06-05 15:25 ` Eli Zaretskii 2016-06-05 19:41 ` Guido Van Hoecke 2016-06-06 2:29 ` Eli Zaretskii 2016-06-06 6:43 ` Guido Van Hoecke 2016-06-06 14:51 ` [O] " Eli Zaretskii 2016-06-06 14:51 ` Eli Zaretskii
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=86shwrkj6u.fsf@gmail.com \ --to=guivho@gmail.com \ --cc=emacs-orgmode@gnu.org \ --cc=help-gnu-emacs@gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index https://git.savannah.gnu.org/cgit/emacs.git https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.