emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: org-ctrl-c-ctrl-c  in comments
Date: Tue, 08 Dec 2015 21:31:18 +0000	[thread overview]
Message-ID: <87lh94pqzd.fsf@mat.ucm.es> (raw)
In-Reply-To: 87lh94pwnk.fsf@alphaville.usersys.redhat.com

>>> "Nick" == Nick Dokos <ndokos@gmail.com> writes:

   > Uwe Brauer <oub@mat.ucm.es> writes:
   >> > Uwe Brauer <oub@mat.ucm.es> writes:
   >> 
   >> > Indeed - org-at-table-p gives nil if the table is inside
   >> > a comment or inside a source block (or inside any other block
   >> > afaict).
   >> 
   >> Well, how could this behavior be changed? I found it quite cumbersome.

   > Well, I'm not an expert on org syntax but reading the comments of
   > org-element.el, I see I was wrong about the other blocks: "greater
   > elements" can contain other elements (e.g. tables). The list of
   > "greater elements" given there is

   > ,----
   > | ;; Element containing other elements (and only elements) are called
   > | ;; greater elements.  Concerned types are: `center-block', `drawer',
   > | ;; `dynamic-block', `footnote-definition', `headline', `inlinetask',
   > | ;; `item', `plain-list', `property-drawer', `quote-block', `section'
   > | ;; and `special-block'.
   > `----

   > So center-blocks, quote-blocks and special blocks allow the table to
   > be recognized as a table, whereas comment-blocks, src-blocks and
   > verse-blocks do not.

Ok, thanks for clarifying this. I try to convince Nicolas to customize
this behavior, such that comment-blocks could be greater elements.


   > Nicolas et al. will surely correct any (more) mistakes in this.

  reply	other threads:[~2015-12-08 21:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 10:29 org-ctrl-c-ctrl-c in comments Uwe Brauer
2015-12-08 16:36 ` Charles C. Berry
2015-12-08 17:10   ` Uwe Brauer
2015-12-08 17:30     ` Nick Dokos
2015-12-08 17:36       ` Uwe Brauer
2015-12-08 18:34         ` Nick Dokos
2015-12-08 19:07           ` Uwe Brauer
2015-12-08 19:28             ` Nick Dokos
2015-12-08 21:31               ` Uwe Brauer [this message]
2015-12-08 21:39               ` Uwe Brauer
2015-12-08 21:46                 ` Nicolas Goaziou
2015-12-08 21:58                   ` Uwe Brauer
2015-12-08 22:29                   ` Uwe Brauer
2015-12-09  1:48                     ` Nick Dokos
2015-12-09  8:40                       ` Uwe Brauer
2015-12-09 13:26                         ` Nick Dokos
2015-12-09 17:23                           ` Uwe Brauer
2015-12-09 17:33                             ` Nick Dokos
2015-12-09 20:00                               ` Uwe Brauer
2015-12-09  1:31     ` Charles C. Berry
2015-12-09  1:35       ` Charles C. Berry
2015-12-09  8:45       ` Uwe Brauer
2015-12-09 11:48         ` Eric S Fraga
2015-12-09 20:04           ` Uwe Brauer
2015-12-09 13:29         ` Nick Dokos

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=87lh94pqzd.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).