emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Edward DeMeulle <ed@demeulle.org>
To: emacs-orgmode@gnu.org
Subject: Re: auto-fill non-op, fill-paragraph error
Date: Fri, 28 Sep 2012 06:32:44 -0700	[thread overview]
Message-ID: <87k3veclxf.fsf@demeulle.org> (raw)
In-Reply-To: <878vbur6t5.fsf@bzg.ath.cx>

org-element-parse-buffer is a Lisp function in `org-element.el'.

(org-element-parse-buffer &optional GRANULARITY VISIBLE-ONLY)

Recursively parse the buffer and return structure.
If narrowing is in effect, only parse the visible part of the

Optional argument GRANULARITY determines the depth of the
recursion.  It can be set to the following symbols:

`headline'          Only parse headlines.
`greater-element'   Don't recurse into greater elements excepted
		    headlines and sections.  Thus, elements
		    parsed are the top-level ones.
`element'           Parse everything but objects and plain text.
`object'            Parse the complete buffer (default).

When VISIBLE-ONLY is non-nil, don't parse contents of hidden

Assume buffer is in Org mode.


org-fill-paragraph is an interactive compiled Lisp function in

(org-fill-paragraph &optional JUSTIFY)

Fill element at point, when applicable.

This function only applies to comment blocks, comments, example
blocks and paragraphs.  Also, as a special case, re-align table
when point is at one.

If JUSTIFY is non-nil (interactively, with prefix argument),
justify as well.  If `sentence-end-double-space' is non-nil, then
period followed by one space does not end a sentence, so don't
break a line there.  The variable `fill-column' controls the
width for filling.

For convenience, when point is at a plain list, an item or
a footnote definition, try to fill the first paragraph within.


  reply	other threads:[~2012-09-28 13:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  1:39 Edward DeMeulle
2012-09-18  6:44 ` Bastien
2012-09-18 14:09   ` Edward DeMeulle
2012-09-24 12:02     ` modeless
2012-09-24 13:57       ` Bastien
     [not found]         ` <CALLZsM=Z_tOqNGT=V8kfcFAZhU0LjW6iQ04hVBBuGREh9hjeuA@mail.gmail.com>
     [not found]           ` <87vcf3l9cu.fsf@bzg.ath.cx>
     [not found]             ` <CALLZsMn_OahEnx2LhsUAUMTfvaR3gTVW2wrFWo7vY99DiMDFbw@mail.gmail.com>
     [not found]               ` <87a9wektfg.fsf@bzg.ath.cx>
2012-09-25 15:56                 ` Jörn Gersdorf
2012-09-27  1:23                   ` Edward DeMeulle
2012-09-27  8:11                     ` Bastien
2012-09-27 14:16                       ` Edward DeMeulle
2012-09-27 14:42                         ` Edward DeMeulle
2012-09-27 21:23                           ` Bastien
2012-09-28  3:41                             ` Edward DeMeulle
2012-09-28  6:37                               ` Bastien
2012-09-28 13:32                                 ` Edward DeMeulle [this message]
2012-09-28 13:54                                   ` Bastien
2012-09-28 14:39                                     ` Edward DeMeulle
2012-09-28 14:54                                       ` Bastien
2012-09-28 14:56                                         ` Edward DeMeulle
2012-09-28 15:06                                           ` Edward DeMeulle
2012-09-28 19:27                                         ` Achim Gratz
2012-09-29  4:06                                           ` Edward DeMeulle
2012-09-29  4:27                                             ` Nick Dokos
2012-09-29  5:14                                               ` Edward DeMeulle
2012-09-29  5:28                                           ` Bastien

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:

  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=87k3veclxf.fsf@demeulle.org \
    --to=ed@demeulle.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).