From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Frankel Subject: Re: make new links show as figures? Date: Fri, 25 Oct 2013 12:49:49 -0400 Message-ID: References: <20c923d8f003b0f570dad32bfb8adcbd@mail.rickster.com> <57E3D773-303E-4E29-AACE-A0D7C78C7F01@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41291) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZkaF-0006kx-KL for emacs-orgmode@gnu.org; Fri, 25 Oct 2013 12:50:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZka9-0006ns-Ax for emacs-orgmode@gnu.org; Fri, 25 Oct 2013 12:49:59 -0400 Received: from [204.62.15.78] (port=43281 helo=mail.rickster.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZka9-0006nd-77 for emacs-orgmode@gnu.org; Fri, 25 Oct 2013 12:49:53 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Kitchin Cc: Alan Schmitt , emacs-orgmode@gnu.org, Carsten Dominik 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