From: Julian Burgos <julian@hafro.is>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: flyspell and code blocks
Date: Mon, 23 Apr 2012 13:57:24 +0000 [thread overview]
Message-ID: <4F955FC4.7050600@hafro.is> (raw)
Hello fellow org'ers,
It is possible to make flyspell to ignore (i.e. do not spell check) the
text within code blocks (I mean blocks of texts separated by #+begin_src
and #+end src)? I did my homework but could not find a good answer.
Many thanks,
Julian
--
Julian Mariano Burgos, PhD
Hafrannsóknastofnunin/Marine Research Institute
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax: +354-5752001
Netfang/Email: julian@hafro.is
next reply other threads:[~2012-04-23 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 13:57 Julian Burgos [this message]
2012-04-23 14:13 ` flyspell and code blocks Jambunathan K
[not found] ` <81397ua64z.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-21 15:37 ` Francesco Pizzolante
2012-12-22 14:04 ` Jambunathan K
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=4F955FC4.7050600@hafro.is \
--to=julian@hafro.is \
--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).