tec/org-mode
tec
/
org-mode
forked from mirrors/org-mode
1
0
Fork 0
Code Pull Requests Releases Activity

org-manual: Clarify :results file graphics header argument meaning 

* doc/org-manual.org (Format): Clarify the difference between
:results file and :results file graphics.  Update the example to
something that can be tried locally.
This commit is contained in:
Ihor Radchenko 2022-11-04 12:01:19 +08:00
parent a3b9bb8faa
commit f5c89ba5f9
No known key found for this signature in database
GPG Key ID: 6470762A7DA11D8B
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/org-manual.org
View File

@ -18408,13 +18408,17 @@ follows from the type specified above.
When used along with =file= type, the result is a link to the file
specified in =:file= header argument. However, unlike plain =file=
type, nothing is written to the disk. The block is used for its
side-effects only, as in the following example:
type, code block output is not written to the disk. The block is
expected to generate the file by its side-effects only, as in the
following example:
#+begin_example
,#+begin_src shell :results file link :file "download.tar.gz"
wget -c "https://example.com/download.tar.gz"
,#+begin_src shell :results file link :file "org-mode-unicorn.svg"
wget -c "https://orgmode.org/resources/img/org-mode-unicorn.svg"
,#+end_src
,#+RESULTS:
[[file:org-mode-unicorn.svg]]
#+end_example
- =org= ::