emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Martin Carlé" <mc@aiguphonie.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] [new exporter] [markdown] spoiled URL containing '=' if using http/s org-links
Date: Fri, 13 Jun 2014 19:26:50 +0300	[thread overview]
Message-ID: <m1k38kojw5.fsf@on27.dyndns.org> (raw)
In-Reply-To: <87ioo56qeg.fsf@bzg.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

Dear Bastien,

yes, I just checked it against the master branch, and how great,
the URL of org-links stays intact now!!!

So, that's solved. Yet, there is another minor issue, as any underscore
char '_' that is contained in the link description (not the URL part)
of an org-link is swallow up and will not appear on the markdown side.


Moreover, seeing all these nice bug fixes that led to today's release,
let me come back to older and maybe somehow forgotten feature request:

http://lists.gnu.org/archive/html/emacs-orgmode/2010-03/msg00379.html

Can't we make these kind of intrusive target-markups-brackets been
hidden, at least optionally, and instead be fontified just similar as link are?
Or could there be posted some hint how to best hack this as a private solution?


Thank you and the list for answering,
mc

On 2014-06-13 Fri 13:43, Bastien <bzg@gnu.org> wrote:
> Hi Martin,
>
> can you try Org latest version from git and says if this still happen?
>
> Thanks,

-- 
Fetch my gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 805 bytes --]

      reply	other threads:[~2014-06-13 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 11:02 [bug] [new exporter] [markdown] spoiled URL containing '=' if using http/s org-links Martin Carlé
2014-06-13 10:43 ` Bastien
2014-06-13 16:26   ` Martin Carlé [this message]

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=m1k38kojw5.fsf@on27.dyndns.org \
    --to=mc@aiguphonie.com \
    --cc=bzg@gnu.org \
    --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).