From: solomon theNinja <solomontheninja@gmail.com>
To: Bastien <bzg@gnu.org>,
solomon theNinja <solomontheninja@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Custom image link types in LaTeX
Date: Fri, 14 Feb 2020 21:18:56 +0200 [thread overview]
Message-ID: <CAJyovgveuBLQ=m06zdT0OWVwVSPbzronu-xRJqaKyd_OFQD+rQ@mail.gmail.com> (raw)
In-Reply-To: <875zg9t7fi.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Alright, I'll wait. Meanwhile I have a few crude advises in my config that
allow some functionality, so no hurry :)
On Fri, Feb 14, 2020 at 7:17 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Bastien <bzg@gnu.org> writes:
>
> > solomon theNinja <solomontheninja@gmail.com> writes:
> >
> >> I'll be happy to implement exporting custom image links myself, given
> >> time, if that's the issue.
> >
> > Sure, please go ahead! If your change is more than 15 lines or so,
> > you might need to sign the FSF copyright assignment:
> >
> > https://orgmode.org/request-assign-future.txt
> >
> >> - If it was not clear, in "custom links" I'm referring to links
> >> defined with `org-link-set-parameters` that have a special export
> >> behavior.
> >
> > Yes, that's what they are for.
>
> Note that I need to slightly improve the tooling in "ol.el", so
> I suggest to wait for these changes, as it might make this feature
> trivial.
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1676 bytes --]
next prev parent reply other threads:[~2020-02-14 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 17:47 Custom image link types in LaTeX solomon theNinja
2020-02-14 10:02 ` Bastien
2020-02-14 17:17 ` Nicolas Goaziou
2020-02-14 19:18 ` solomon theNinja [this message]
2020-02-14 20:13 ` solomon theNinja
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='CAJyovgveuBLQ=m06zdT0OWVwVSPbzronu-xRJqaKyd_OFQD+rQ@mail.gmail.com' \
--to=solomontheninja@gmail.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).