Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
flycheck-temp-file-system problem in windows editing code from orgmode #983
This is a Windows only problem, though I hope that the fix is harmless to non-windows environments.
Flymake works like a charm (thank you guys) a.o. to check .el, .js, .php et al. files.
However, my emacs.el file is generated from an emacs-guivho.org file. When I issue
The problem seems to be the asterisks. I am told that this can easily be fixed by calling convert-standard-filename on the generated tempfile name.
For testing i went to change flycheck-temp-file-system in flycheck.el so that it reads
rather than the original
I than edebugged the
Still, when editing elisp blocks from my elisp.org files, I keep hitting the '*' problem...
Would it be possible that such a change could be incorporated into flycheck? The description of convert-standard-filename states that it just returns the given filename in non-windows environments. It would solve the problem for us windows users though.
@guivho Thanks for reporting this issue. While we normally don't try and fix Windows issues the fix you proposed looks simple enough, and I've applied it to
I can't test it, obviously; please tell me whether the fix works.
Another thing: In future please use Github's Markdown markup to format your posts and comments on Github. Adding markup to code and error messages preserves formatting and indentation—which is particularly important for source code and backtraces—and makes posts easier to read overall.