emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Behavior of M-q on comments in code blocks
Date: Wed, 05 Feb 2014 11:44:54 +0100	[thread overview]
Message-ID: <86fvnxg7o9.fsf@somewhere.org> (raw)

Hello,

Some time ago, doing a M-q on a comment in a code block did work.

For example, the following:

#+begin_src emacs-lisp
  ;; display symbol definitions, as found in the relevant manual (for AWK, C, Emacs Lisp, LaTeX, M4, Makefile, Sh and other languages that have documentation in Info)
  (global-set-key
    (kbd "<C-f1>") 'info-lookup-symbol)
#+end_src

became:

#+begin_src emacs-lisp
  ;; display symbol definitions, as found in the relevant manual (for AWK, C,
  ;; Emacs Lisp, LaTeX, M4, Makefile, Sh and other languages that have
  ;; documentation in Info)
  (global-set-key
    (kbd "<C-f1>") 'info-lookup-symbol)
#+end_src

after `M-q' on the comment line (without going to the indirect buffer).

This does not work anymore, as you can see on
http://screencast.com/t/iauhzbvnmXXn. It even completely breaks the
block itself.

Though, I can't say whether the fact it does not work anymore is due to
changes in Org or in my Emacs configuration. Any hint?

Best regards,
  Seb

-- 
Sebastien Vauban

             reply	other threads:[~2014-02-05 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 10:44 Sebastien Vauban [this message]
2014-02-05 11:37 ` Behavior of M-q on comments in code blocks Thorsten Jolitz
2014-02-05 12:05 ` Bastien
2014-02-05 14:09   ` Sebastien Vauban
2014-02-05 15:26     ` Bastien
2014-02-05 15:32       ` Sebastien Vauban
2014-02-05 16:18         ` Bastien
2014-02-13 14:46   ` Sebastien Vauban

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=86fvnxg7o9.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@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).