emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Brett Viren <bv@bnl.gov>, Carsten Dominik <dominik@uva.nl>,
	Org Mode <emacs-orgmode@gnu.org>,
	Tim Cross <theophilusx@gmail.com>
Subject: Re: why prepend "file://" to abs paths in html output?
Date: Thu, 13 Jul 2017 14:55:02 +0200	[thread overview]
Message-ID: <871spkfqe1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY0CYRwk+sBkeaXichtkeXfP41b=YWFFQGcFXEs2Tiokfg@mail.gmail.com> (Kaushal Modi's message of "Thu, 13 Jul 2017 12:50:52 +0000")

Kaushal Modi <kaushal.modi@gmail.com> writes:

> Hmm. Thanks for that hint. Would it be OK to define backend-specific link
> abbreviations?

I don't think so. 

Back-end are able to manipulate links the way they want without Org core
interfering. IOW, this black magick should operate whitin "ox-hugo.el"
itself, IMO.

BTW, I still don't understand why an export back-end (unlike an user)
would need to use link abbreviations.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-07-13 12:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08  0:38 why prepend "file://" to abs paths in html output? Matt Price
2017-07-08 10:33 ` Nicolas Goaziou
2017-07-08 12:37   ` Kaushal Modi
2017-07-08 14:08     ` Nicolas Goaziou
2017-07-08 14:19       ` Carsten Dominik
2017-07-08 19:13         ` Nicolas Goaziou
2017-07-08 23:37           ` Tim Cross
2017-07-09 10:45             ` Nicolas Goaziou
2017-07-10 12:53               ` Kaushal Modi
2017-07-10 13:31                 ` Nicolas Goaziou
2017-07-10 13:58               ` Brett Viren
2017-07-10 19:54                 ` Kaushal Modi
2017-07-10 21:44                   ` Kaushal Modi
2017-07-13 12:39                   ` Nicolas Goaziou
2017-07-13 12:50                     ` Kaushal Modi
2017-07-13 12:55                       ` Nicolas Goaziou [this message]
2017-07-13 13:01                         ` Kaushal Modi
2017-07-13 13:14                           ` Nicolas Goaziou
2017-07-13 12:46                 ` Nicolas Goaziou
2017-07-10 22:12               ` Tim Cross

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=871spkfqe1.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bv@bnl.gov \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=theophilusx@gmail.com \
    /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).