emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Huszagh <huszaghmatt@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: incorrect documentation for file-desc header argument?
Date: Tue, 28 Jul 2020 21:35:13 -0700	[thread overview]
Message-ID: <87lfj3c51a.fsf@gmail.com> (raw)


The org info documentation states

     The ‘file-desc’ header argument defines the description (see *note
     Link Format::) for the link.  If ‘file-desc’ has no value, Org uses
     the generated file name for both the “link” and “description” parts
     of the link.

However, if I evaluate the

#+BEGIN_SRC asymptote :results value file :file circle.pdf :output-dir img/

I get


I believe the documentation (and this is corroborated by the discussion
of the original patch
that the intended result is


Is my assessment correct? Can anyone else confirm this bug?


             reply	other threads:[~2020-07-29  4:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  4:35 Matt Huszagh [this message]
2020-07-29  4:50 ` Matt Huszagh
2020-07-29  5:03 ` Kyle Meyer
2020-07-29  7:41   ` Eric S Fraga
2020-07-30  1:19   ` Matt Huszagh
2020-07-30  2:29     ` Kyle Meyer

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:

  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=87lfj3c51a.fsf@gmail.com \
    --to=huszaghmatt@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: incorrect documentation for file-desc header argument?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).