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: Filling comments in Org code block vs in temporary buffer
Date: Wed, 24 Oct 2012 16:31:58 +0200	[thread overview]
Message-ID: <80ipa03pr5.fsf@somewhere.org> (raw)

#+TITLE:     Filling comments
#+LANGUAGE:  en

* Context

I've stopped using FillAdapt in Org files, and do not suffer any particular
problems, except this one (though, certainly unrelated).

* Problem

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

FYI, C-h k M-q gives:

    ╭────
    │ M-q runs the command fill-paragraph, which is an interactive compiled
    │ Lisp function in `fill.el'.
    │
    │ It is bound to M-q.
    │
    │ (fill-paragraph &optional JUSTIFY REGION)
    │
    │ Fill paragraph at or after point.
    ╰────

* Workaround

- Open it in a temporary buffer (via C-c ')
- Re-run M-q anywhere on the comment

#+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

FYI, when inside the temporary buffer, C-h k M-q just gives exactly the
same (and expected command): =fill-paragraph=.

* Questions

I think this is quite new, but could not identify anything peculiar in my
config. Do you have the same?

Do you understand why?

Best regards,
  Seb

-- 
Sebastien Vauban

next             reply	other threads:[~2012-10-24 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 14:31 Sebastien Vauban [this message]
2012-10-24 14:48 ` Filling comments in Org code block vs in temporary buffer Nicolas Goaziou
2012-10-24 18:53   ` Sebastien Vauban
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=80ipa03pr5.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

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