unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: flycheck orgmode on windows invalid output file name
Date: Mon, 06 Jun 2016 05:29:29 +0300	[thread overview]
Message-ID: <83porvt5h2.fsf@gnu.org> (raw)
In-Reply-To: <CAEySM9EmUY2ZcX3RxP60HHYHmCo59cDmfN4nuSqeQUYHNqmyHA@mail.gmail.com> (message from Guido Van Hoecke on Sun, 5 Jun 2016 21:41:18 +0200)

> From: Guido Van Hoecke <guivho@gmail.com>
> Date: Sun, 5 Jun 2016 21:41:18 +0200
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>, orgmode <emacs-orgmode@gnu.org>
> 
> For testing i went to change flycheck-temp-file-system in flycheck.el
> so that it reads
> 
> (setq tempfile (convert-standard-filename (expand-file-name
> (file-name-nondirectory filename)
>            directory)))
> 
> rather than the original
> 
> (setq tempfile (expand-file-name (file-name-nondirectory filename)
>            directory))
> 
> I than edebugged the flycheck-temp-file-system with the
> "c:/Users/guivh/emacs-guivho/.flycheck_emacs-guivho.org[*Org Src
> emacs-guivho.org[ emacs-lisp ]*]") filename, and it nicely produced a
> tempfile where the '*'s are replaced by '!'s.
> 
> Still, when editing elisp blocks from my elisp.org files, I keep
> hitting the '*' problem...

What is "the '*' problem", exactly?



  reply	other threads:[~2016-06-06  2:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-06-06  6:43       ` Guido Van Hoecke
2016-06-06 14:51         ` [O] " 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83porvt5h2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).