emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Martin Beck <Elwood151@web.de>
Cc: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Problems with Hyperlinks containing backslashes
Date: Thu, 09 Apr 2015 19:46:40 +0200	[thread overview]
Message-ID: <87zj6hnqin.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <trinity-a507e204-3971-4524-a43f-5520519b8399-1428495097833@3capp-webde-bs22> (Martin Beck's message of "Wed, 8 Apr 2015 14:11:37 +0200")

"Martin Beck" <Elwood151@web.de> writes:

>>> w32-shell-execute("open" "\\\\servername\\dir1\\dir2")
>>> eval((w32-shell-execute "open" file))
>>> It seems that Emacs automatically replaces each backslash with a
>>> double backslash.
>>> How can I change that so that it is working?
>> IIRC it is fixed in development branch of Org. You may want to use
> it or
>> wait for Org 8.3 to be released.
> Salut Nicolas,
> thanks a lot - indeed with the current org-lastest, the above
> mentioned problem seems to be solved.
> However I'm still having problem with paths like that:
> [[file+sys:\\servername.domain.de\dir\]]
> which produce the error "No such file c:/servername.domain.de/dir/"

I cannot reproduce it. However, I don't use Windows either. The part of
code responsible for URI normalization is located in
`org-element-link-parser':

        (when (and (file-name-absolute-p path)
                   (not (org-string-match-p "\\`[/~]/" path)))
          (setq path (concat "//" path)))

The "c:" is added elsewhere.

Regards,

  reply	other threads:[~2015-04-09 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 12:11 Problems with Hyperlinks containing backslashes Martin Beck
2015-04-09 17:46 ` Nicolas Goaziou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-07 15:18 Elwood151
2015-04-07 20:16 ` Nicolas Goaziou

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87zj6hnqin.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=Elwood151@web.de \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).