From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Filling comments in Org code block vs in temporary buffer
Date: Thu, 25 Oct 2012 10:34:04 +0200 [thread overview]
Message-ID: <803913ne6b.fsf@somewhere.org> (raw)
In-Reply-To: 87mwzbmwr4.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> Is there no way to make such a practical feature[1] available?
>
> There's a mechanism to send commands to the src-block through the
> appropriate major-mode. It may be possible to ask for a filling with that.
> But I don't think Org should treat a src-block as plain text when M-q is
> used.
>
>> [1] For example, mails I get are enclosed in a "verse" block, and I've the
>> habit of reformatting them before saving my "inbox" file.
>
> Verse blocks are for free-form poetry and cannot be filled. I suggest to use
> quote blocks, which can be filled, for that.
I used VERSE (instead of EXAMPLE) by following (what I understood from) your
advice, see http://comments.gmane.org/gmane.emacs.orgmode/33919.
Maybe that's stupid of mine, but I have such a capture template for received
emails:
#+begin_src emacs-lisp
(setq org-capture-templates
`(("m" "Mail" entry
(file+headline ,org-default-notes-file "Tasks")
"* TODO %:subject%? (from %:fromname) :mail:
SCHEDULED: %t
%:date-timestamp-inactive
#+begin_verse
%i
#+end_verse
From %a"
:empty-lines 1 :immediate-finish t)))
#+end_src
That allows for
- easy followup of emails to answer to (by setting SCHEDULED to today), and
- nice HTML export (LaTeX not especially used) of project documentation (where
mail extracts may serve as documentation).
Now, I don't need anything special (no treatment of the emails contents), but
I need some "respectful" filling (what FillAdapt did), so that the following:
#+begin_quote
> I think VERSE (patched) is better than EXAMPLE because you can still
> benefit from text markup (and LaTeX snippets). Sadly, mails can
> sometimes be, well, very distant from poetry...
#+end_quote
does not become:
#+begin_quote
> I think VERSE (patched) is better than EXAMPLE because you can still >
benefit from text markup (and LaTeX snippets). Sadly, mails can > sometimes
be, well, very distant from poetry...
#+end_quote
when refilled.
Any better advice?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-10-25 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 14:31 Filling comments in Org code block vs in temporary buffer Sebastien Vauban
2012-10-24 14:48 ` Nicolas Goaziou
2012-10-24 18:53 ` Sebastien Vauban
2012-10-24 20:38 ` Nicolas Goaziou
2012-10-25 8:34 ` Sebastien Vauban [this message]
2012-10-25 12:15 ` Nicolas Goaziou
2012-12-18 11:50 ` 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:
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=803913ne6b.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).