From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: filling of long captions
Date: Fri, 07 Feb 2014 11:12:23 +0100 [thread overview]
Message-ID: <874n4btens.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87ha8b1c0z.fsf@gmail.com
Hello,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
>> Nicolas, what do you think of enhancing the auto-filling (and
>> delete-indentation) capabilities for some affiliated keywords?
>>
>> #+CAPTION:
>> #+HEADER:
>> #+TBLFM:
>
> Not that it matters much, but "TBLFM" is not an affiliated keyword per
> se, it belongs to the table syntax. OTOH, you can have "CAPTION" and
> "HEADER" keywords on top of almost any element type.
>
> Anyway, the three keywords are very different.
>
> To start with the one I know the most, CAPTION can have an optional
> value, and multiple caption lines can have as many optional values.
>
> #+CAPTION[short caption]: long caption
> #+CAPTION[short caption, continued]: long caption, continued.
>
> Therefore, filling it can be tricky since you have to pay attention to
> both values.
>
> Moreover, if the "short" caption is too long to fit on one line, that
> line still needs to end with "]:" to be valid.
>
> #+CAPTION[very very ... long "short" caption]:
> #+CAPTION[continued even here]: long caption
> #+CAPTION: long caption continued.
>
This is something, that I had not thought about when I expressed my
wish. I did not even know, that consecutive #+CAPTION lines could also
have consecutive short captions. I see the difficulty here.
Usually, my votes are in favour of backwards compatibility. So, I am
not too sure about this suggestion myself: But here an obvious
'solution' would be to move the short caption to #+SHORT_CAPTION.
I see that such change would bring its own difficulties besides breaking
the backwards compatibility. Like what to do when there is a short
caption but no 'long' caption.
I am just continuing this discussion, as I do not have 'the occasional
three lines caption need' but the 'always multi-lines caption need'. In
my opinion, images in an article/paper/thesis/... should tell their
story independently of the text referring to them. So, my captions
tend to be (too?) long.
So, I would benefit a lot from whatever filling mechanism might get
implemented.
[...]
Regards,
Andreas
next prev parent reply other threads:[~2014-02-07 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 7:46 Feature request: filling of long captions Andreas Leha
2014-02-06 8:43 ` Bastien
2014-02-06 10:20 ` Andreas Leha
2014-02-06 10:40 ` Bastien
2014-02-06 11:14 ` Andreas Leha
2014-02-06 11:40 ` Thomas Holst
2014-02-06 17:26 ` Scott Randby
2014-02-06 22:08 ` Andrea Rossetti
2014-02-07 2:18 ` Eric Schulte
2014-02-07 7:36 ` Andreas Leha
2014-02-07 8:37 ` Nicolas Goaziou
2014-02-07 8:47 ` Bastien
2014-02-07 9:56 ` Nicolas Goaziou
2014-02-07 10:12 ` Andreas Leha [this message]
2014-02-07 10:28 ` Bastien
2014-02-07 10:30 ` Nicolas Goaziou
2014-02-07 10:35 ` Bastien
2014-02-07 16:49 ` Eric Schulte
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=874n4btens.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.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
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).