From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Status fix for "Regression in fill-paragraph behavior"?
Date: Mon, 27 May 2013 15:33:17 +0200 [thread overview]
Message-ID: <20130527133317.GG15604@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <B7EEF3066CD1D24081DBFF5E9F5E68D402053791BA@EXCNLDCM06.europe.unity>
Hello Peter,
On Mon, May 27, 2013 at 01:03:41PM +0200, Wagemans, Peter wrote:
>
> Nicolas Goaziou wrote:
>
> > Also, you have to admit that Org is a bit more complex than Text mode
> > (or Fundamental mode), and may have different requirements.
>
> It sure is a great tool, with a lot of useful functionality. But the
> new paragraph fill breaks my old workflows, so I am trying to find a
> way around that (preferably the easiest ;-). Is there some way or
> setting to tell org that in a node or perhaps all nodes in a subtree
> it should apply the adaptive fill from fill.el to text paragraphs, so
> that the fill-prefix is automatically recognized like in fundamental
> and text mode? Or is there some function that I can call (and bind to
> some key combination) to apply the old paragraph fill to some text
> paragraph? So that plain text paragraphs and citations that don't use
> any org features can be filled in the old way.
Untested idea: you could adapt org-fill-paragraph to suit your needs and
call the custom fill function when you need it.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-05-27 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 10:19 Status fix for "Regression in fill-paragraph behavior"? Wagemans, Peter
2013-05-24 12:16 ` Nicolas Goaziou
2013-05-24 13:10 ` Wagemans, Peter
2013-05-24 13:58 ` Nicolas Goaziou
2013-05-24 19:35 ` Wagemans, Peter
2013-05-24 20:23 ` Nicolas Goaziou
2013-05-27 11:03 ` Wagemans, Peter
2013-05-27 13:33 ` Suvayu Ali [this message]
2013-05-31 12:34 ` Nicolas Goaziou
2013-05-24 17:27 ` Samuel Wales
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=20130527133317.GG15604@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.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).