From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: make new links show as figures? Date: Sat, 26 Oct 2013 08:10:06 -0400 Message-ID: References: <20c923d8f003b0f570dad32bfb8adcbd@mail.rickster.com> <57E3D773-303E-4E29-AACE-A0D7C78C7F01@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=bcaec53963ca6214a904e9a3bf27 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Va2gz-0003oG-DG for emacs-orgmode@gnu.org; Sat, 26 Oct 2013 08:10:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Va2gy-0004cT-Hg for emacs-orgmode@gnu.org; Sat, 26 Oct 2013 08:10:09 -0400 Received: from mail-pd0-x236.google.com ([2607:f8b0:400e:c02::236]:33859) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Va2gy-0004by-AT for emacs-orgmode@gnu.org; Sat, 26 Oct 2013 08:10:08 -0400 Received: by mail-pd0-f182.google.com with SMTP id q10so5092878pdj.13 for ; Sat, 26 Oct 2013 05:10:06 -0700 (PDT) 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: Rick Frankel Cc: Alan Schmitt , "emacs-orgmode@gnu.org" , Carsten Dominik --bcaec53963ca6214a904e9a3bf27 Content-Type: text/plain; charset=ISO-8859-1 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 > Yes, I think [[custom:file.ext][file:file.png]] would cover all those cases. --bcaec53963ca6214a904e9a3bf27 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


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. =A0Even 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<= br> use cases mentioned?

rick

Yes, = I think [[custom:file.ext][file:file.png]] would cover all those cases.
=
--bcaec53963ca6214a904e9a3bf27--