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 08:36:04 +0100 [thread overview]
Message-ID: <87d2iztlwb.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87d2izbr1c.fsf@gmail.com
Eric Schulte <schulte.eric@gmail.com> writes:
> Andrea Rossetti <andrea.rossetti@gmail.com> writes:
>
>> Hello Bastien and everyone reading,
>>
>> Bastien <bzg@gnu.org> writes:
>>> Could you list other options that are good candidates for such
>>> auto-filling fonctionality? We'd better implement them all at
>>> once.
>>
>> I'd suggest to split the wish-list in two buckets, i.e.
>>
>> 1) some "#+..." commands would benefit of a line-continuation
>> mechanism (like the backslash at EOL in a multilined C/C++
>> #define macro)
>>
>> 2) some line-continuation-aware "#+..." commands (thanks to
>> implementations for step 1) would benefit of auto-filling
>>
>> To me #+TBLFM seems to fit into bucket 1, #+CAPTION into
>> bucket 2. My Christmas wish is #+MACRO into bucket 1.
>>
>> Kindest regards,
>>
>> Andrea
>>
>
> For a while now I've been wishing that keywords (namely #+Caption:)
> could be equivalently specified as blocks (e.g., #+begin/end_Caption:).
>
> Would that be another possible solution here?
I can not think of any downside, so I guess it would work at least
as well for me.
It might be harder to implement, since multiple caption lines are
already parsed correctly by Org.
The begin/end_caption blocks would have their advantages in terms of
syntax highlighting / readability of the Org buffer.
Regards,
Andreas
next prev parent reply other threads:[~2014-02-07 7:36 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 [this message]
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=87d2iztlwb.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).