emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Wed, 24 Oct 2012 20:53:53 +0200	[thread overview]
Message-ID: <80625zpupq.fsf@somewhere.org> (raw)
In-Reply-To: 87y5iwlye7.fsf@gmail.com

Hello Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> When trying to refill the comment directly in the following code block
>> (staying in the Org file), it has *no effect*.
>>
>> #+begin_src emacs-lisp
>>   ;; a single space does end a sentence. But this sentence is the longest I could write...
>>   (setq-default sentence-end-double-space nil)
>> #+end_src
>
> Org doesn't know how to fill foreign code. Thus, you cannot fill
> directly a src-block (or an example block or even an export block for
> that matter).
>
> As you tried, you can edit that chunk of code in a separate buffer with
> the appropriate major mode (and subsequent filling rules) using C-c '.

For sure, that did work before -- at least in my setup... Maybe because of
FillAdapt and such, which I used back then.

Is there no way to make such a practical feature[1] available?

Best regards,
  Seb

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

-- 
Sebastien Vauban

  reply	other threads:[~2012-10-24 18:53 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 [this message]
2012-10-24 20:38     ` Nicolas Goaziou
2012-10-25  8:34       ` Sebastien Vauban
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=80625zpupq.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).