emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: regcl <regcl@channing.harvard.edu>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: controling width of graphviz source block result
Date: Sat, 22 Feb 2014 22:01:11 -0500	[thread overview]
Message-ID: <87vbw6zg5k.fsf@channing.harvard.edu> (raw)
In-Reply-To: <87d2if1qox.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 22 Feb 2014 09:45:18 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> regcl <regcl@channing.harvard.edu> writes:
>
>> So I am understanding from your answer that attribues only "modify" the
>> next immediate "thing" in the .org document, and do not persist, so to
>> speak.
>
> "things" are called "elements" in Org lingo and "attributes" are called
> "affiliated keywords". So, yes, affiliated keywords apply to the element
> right after them.
>
>> But I have discovered that it works to stack them up like this ...
>>
>> #+ATTR_HTML: :width 1000
>> #+ATTR_ODT: :width 15 :height 15
>> [[file:gnus.png]]
>>
>> ... so I am a little confused. 
>>
>> Could you please clarify?
>
> Both keywords are affiliated keywords. There is only one element in this
> example (a paragraph containing a single link). Affiliated keywords
> apply to the next element, not the next affiliated keyword.
>
> For more information, see:
>
>   http://orgmode.org/worg/dev/org-syntax.html
>
> or the comments at the beginning of "org-element.el".
>
>
> Regards,

Thank you, this is helpful. May require a little study ;)

best,
regcl

next prev parent reply	other threads:[~2014-02-23  3:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 16:55 controling width of graphviz source block result regcl
2014-02-21 17:25 ` Nicolas Goaziou
2014-02-21 20:11   ` regcl
2014-02-22  8:45     ` Nicolas Goaziou
2014-02-23  3:01       ` regcl [this message]
2014-06-12 22:29       ` regcl
2014-06-14 11:54         ` Nicolas Goaziou
2014-06-17 12:25         ` Sebastien Vauban

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=87vbw6zg5k.fsf@channing.harvard.edu \
    --to=regcl@channing.harvard.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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

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