From: Rick Frankel <rick@rickster.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Alan Schmitt <alan.schmitt@polytechnique.org>,
emacs-orgmode@gnu.org,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: make new links show as figures?
Date: Fri, 25 Oct 2013 12:49:49 -0400 [thread overview]
Message-ID: <f201feb5913d631a11288e5a01d66498@mail.rickster.com> (raw)
In-Reply-To: <CAJ51ETo7nVpG0AjO0=+F0WqFEHnYMmEEQ_yCVh-7YEkFP6eq=A@mail.gmail.com>
On 2013-10-24 17:48, John Kitchin wrote:
> I don't think making chemdraw a babel language is the answer here. The
> way I know chemdraw is as a standalone binary executable that is all
> gui. there is no scripting. maybe you could build an xml file by hand,
> but i would never dream of that! maybe I am missing how you would use
> it.
Sorry, not familiar w/ chemdraw and you had originally mentioned that
you wanted clicking the link to open it in emacs.
> [[chemdraw:file.cdxml][file:file.png]]
>
> Is pretty close to what I had in mind. I would define the link click
> function to just strip off the png, and open the file.cdxml for
> example, then you do not need both of those pieces. I suppose this
> means you would have had to export the file as a new png after editing
> it to make a change though.
I realize that. I offered this approach as an alternative, as I
believe I can add the functionality to expand inline images in the
description portion, but i don't see a way to make the link portion
accept "aliases" for the file: protocol without major changes to link
handling. Even then, it seems a bit like a hack.
> [many use cases omitted]
> Those are what I was thinking about for using other links as images.
Other than having to repeat yourself, wouldn't the
[[custom:file.ext][file:file.png]] syntax allow for most/all of the
use cases mentioned?
rick
next prev parent reply other threads:[~2013-10-25 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 1:53 make new links show as figures? John Kitchin
2013-10-23 13:54 ` Rick Frankel
2013-10-24 7:28 ` Alan Schmitt
2013-10-24 10:08 ` Carsten Dominik
2013-10-24 13:45 ` Rick Frankel
2013-10-24 21:48 ` John Kitchin
2013-10-25 16:49 ` Rick Frankel [this message]
2013-10-26 12:10 ` John Kitchin
2013-10-30 16:02 ` Rick Frankel
2013-10-31 10:04 ` Alan Schmitt
2013-10-31 15:47 ` Rick Frankel
2013-10-31 16:20 ` Cook, Malcolm
2013-10-31 16:55 ` Rick Frankel
2013-10-31 17:06 ` Alan Schmitt
2013-10-24 23:41 ` Rick Frankel
2013-10-25 1:18 ` Rick Frankel
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=f201feb5913d631a11288e5a01d66498@mail.rickster.com \
--to=rick@rickster.com \
--cc=alan.schmitt@polytechnique.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).