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

From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Align argument in #+attr_latex for tabular env. is whitespace sensitive
Date: Fri, 15 Feb 2013 19:53:00 +0100	[thread overview]
Message-ID: <86bobll88j.fsf@somewhere.org> (raw)
In-Reply-To: 87bobl7mhu.fsf@gmail.com

Hi Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>>> This syntax is wrong anyway. It should be:
>>>
>>>   #+attr_latex: :width "5cm"
>>>
>>> or
>>>
>>>   #+attr_latex: :width 5cm
>>
>> From the tests I made on images, with the Beamer back-end, those did not work.
>> It had to be:
>>
>>     #+ATTR_LaTeX: :options "width=5cm"
>>
>> Right?
>
> Correct. :width is for tables.

Thanks.

For my information (and not only for me, I guess), is there a fundamental
reason (I guess yes) why width is a first-class parameter for tables and an
option among others for images?

Looking from a 50 ft perspective, I would even imagine the opposite: images
will have to be scales in almost all cases (that is: have their image
attribute set), while tables will often take the space they need to.

Is there a reason why images can't have their own attributes as well?  I would
find that much, much more easy to apply, if we don't have to write the same
"functional" request in two different manners, depending on the context.

Best regards,
  Seb

-- 
Sebastien Vauban

next prev parent reply	other threads:[~2013-02-15 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 17:30 Align argument in #+attr_latex for tabular env. is whitespace sensitive John Hendy
2013-02-12 19:22 ` Nicolas Goaziou
2013-02-12 19:40   ` John Hendy
2013-02-12 19:44     ` Nicolas Goaziou
2013-02-12 19:51       ` John Hendy
2013-02-15 10:05   ` Sebastien Vauban
2013-02-15 13:08     ` Nicolas Goaziou
2013-02-15 18:53       ` Sebastien Vauban [this message]
2013-02-15 19:44         ` Nicolas Goaziou

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=86bobll88j.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /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).