emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] manual: confusing example of adding attributes to a link (affiliated keywords)
Date: Sat, 25 Jun 2022 18:39:33 +0800	[thread overview]
Message-ID: <87a6a1uivu.fsf@localhost> (raw)
In-Reply-To: <t96n1p$hv9$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> Certainly it is possible to document that attributes are mostly useful 
> for image links when they are block-level elements rather than inline 
> objects. Caveats of trying to use attributes for inline objects should 
> be clearly stated to avoid false expectation of supported feature.

Agree. Patches are welcome :)

>> You examples are pretty much dedicated to html. Do you know if
>> per-object attributes could be actually useful for other export
>> backends?
>
> The following example is somewhat contrived. Try to set different 
> options (width or e.g. angle) for several inline images. It applies to 
> LaTeX as well:
>
>
>      #+attr_latex: :center nil :options angle=30 :width 16mm
>      [[file:/usr/share/icons/hicolor/48x48/apps/emacs.png]]
>      and
>      [[file:/usr/share/icons/hicolor/48x48/apps/emacs.png]]
>      # second one should have angle=-30

What about something that is not a single-image paragraph?
Single-image paragraphs specifically are handled specially during
export.

Best,
Ihor


  reply	other threads:[~2022-06-25 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 16:25 [BUG] manual: confusing example of adding attributes to a link (affiliated keywords) Max Nikulin
2022-06-25  5:29 ` Ihor Radchenko
2022-06-25 10:12   ` Max Nikulin
2022-06-25 10:39     ` Ihor Radchenko [this message]
2022-06-25 11:55       ` Max Nikulin
2022-06-25 12:17         ` Ihor Radchenko

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=87a6a1uivu.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).