From: Thomas Holst <thomas.holst@de.bosch.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Feature request: filling of long captions
Date: Thu, 6 Feb 2014 12:40:24 +0100 [thread overview]
Message-ID: <ywod8utoxydz@de.bosch.com> (raw)
In-Reply-To: <87r47gtrvs.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Thu, 6 Feb 2014 12:14:31 +0100")
Hi,
· Andreas Leha <andreas.leha@med.uni-goettingen.de> wrote:
> Hi Bastien,
>
> Bastien <bzg@gnu.org> writes:
>
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>> Do you mean (1) other places in org files (other than #+caption) or
>>> (2) other functionality that should be supported at #+caption
>>> filling?
>>
>> Normally lines matching the regexp ^#\+\S-+ (like #+CAPTION) should
>> not be filled. We would introduce an exception where successive
>> #+CAPTION lines are correctly parsed by Org -- so the question is
>> how many of such options should fill like #+CAPTION will do (maybe
>> before Christmas.)
>
> Well, I am not sure that I understand this. #+CAPTION lines are IMO
> parsed correctly by Org -- just the filling is missing.
>
> I do not (at the moment) see other 'options' like #+CAPTION that are
> missing auto-fill capabilities.
what about #+HEADER: for source code blocks. Filling might be difficult since
I don't know if something like:
#+HEADER: :var foo=
#+HEADER: "bar"
is handled correctly by babel parser.
The same holds true for #+ATTR_LATEX:
--
Mit freundlichen Grüßen / Best regards
Thomas Holst
DGS-EC/ESE4
Tel. +49 (711) 811-40681
PC-Fax +49 (711) 811-5182208
next prev parent reply other threads:[~2014-02-06 11:49 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 [this message]
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
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=ywod8utoxydz@de.bosch.com \
--to=thomas.holst@de.bosch.com \
--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).