Eric Schulte <schulte.e...@gmail.com> writes: > Andrea Rossetti <andrea.rosse...@gmail.com> writes: > >> Hello Bastien and everyone reading, >> >> Bastien <b...@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
