From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: ivy-bibtex and orgmode inserts ebib: link
Date: Fri, 22 Mar 2019 07:59:13 -0400 [thread overview]
Message-ID: <CAJ51ETqA+TggY1_BwUXHxHRVZ98HuaUbXZG_jSuq4tPKXpTn3w@mail.gmail.com> (raw)
In-Reply-To: <87tvfvw3jc.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
I guess this
http://kitchingroup.cheme.cmu.edu/blog/2016/11/04/New-link-features-in-org-9/
will show you most of what you need to make new links.
org-link-set-parameters Also makes new links.
On Fri, Mar 22, 2019 at 7:37 AM Eric S Fraga <esflists@gmail.com> wrote:
> I am going down a rabbit hole here...
>
> Short question: how can I add a new link type to org? It used to be
> that we would use ~org-add-link-type~ but this is
> deprecated. Fine. The documentation points to
> ~org-link-set-parameters~ instead but this can only set the parameters
> for known links. Known links seem to be defined by a complex regex in
> ~org-link-types-re~.
>
> What is the replacement for ~org-add-link-type~ in the latest version of
> org, if any? Or do I have to both add to the regex and set link
> parameters separately?
>
> Thank you!
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.2.2-324-gd58827
>
> --
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
[-- Attachment #2: Type: text/html, Size: 1842 bytes --]
next prev parent reply other threads:[~2019-03-22 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 10:39 ivy-bibtex and orgmode inserts ebib: link Eric S Fraga
2019-03-22 11:10 ` Eric S Fraga
2019-03-22 11:29 ` Eric S Fraga
2019-03-22 11:50 ` Nicolas Goaziou
2019-03-22 11:59 ` John Kitchin [this message]
2019-03-22 12:06 ` Joost Kremers
2019-03-22 12:22 ` Eric S Fraga
2019-03-22 12:14 ` Eric S Fraga
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=CAJ51ETqA+TggY1_BwUXHxHRVZ98HuaUbXZG_jSuq4tPKXpTn3w@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--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).