emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Trevor Murphy <trevor.m.murphy@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Trevor Murphy <trevor.m.murphy@gmail.com>
Subject: [PATCH] org.el: Don't flyspell check within source code blocks
Date: Sat, 25 May 2013 03:17:26 -0400	[thread overview]
Message-ID: <1369466246-5113-2-git-send-email-trevor.m.murphy@gmail.com> (raw)
In-Reply-To: <1369466246-5113-1-git-send-email-trevor.m.murphy@gmail.com>

* lisp/org.el (org-mode-flyspell-verify): Check if
  `org-element-at-point' is of type `src-block', and don't flyspell if
  that's the case.

TINYCHANGE
---
 lisp/org.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index 94078f9..81428f5 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -23596,7 +23596,8 @@ To get rid of the restriction, use \\[org-agenda-remove-restriction-lock]."
 	 (not (member-ignore-case word (org-get-export-keywords)))
 	 (not (member-ignore-case
 	       word (mapcar 'car org-element-block-name-alist)))
-	 (not (member-ignore-case word '("BEGIN" "END" "ATTR"))))))
+	 (not (member-ignore-case word '("BEGIN" "END" "ATTR")))
+	 (not (not (eq (org-element-type (org-element-at-point)) 'src-block))))))
 
 (defun org-remove-flyspell-overlays-in (beg end)
   "Remove flyspell overlays in region."
-- 
1.8.2.3

  reply	other threads:[~2013-05-25  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  7:17 [PATCH] org.el: Don't flyspell check within source code blocks Trevor Murphy
2013-05-25  7:17 ` Trevor Murphy [this message]
2013-05-25  7:24   ` Trevor Murphy
2013-08-31  6:23 ` Carsten Dominik
  -- strict thread matches above, loose matches on Subject: below --
2013-05-25  7:23 [PATCH] Take 2 on " Trevor Murphy
2013-05-25  7:23 ` [PATCH] " Trevor Murphy
2013-05-25 15:52   ` Bastien
2013-05-30  0:55     ` Trevor Murphy
2013-05-30 15:54     ` Matt Lundin

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=1369466246-5113-2-git-send-email-trevor.m.murphy@gmail.com \
    --to=trevor.m.murphy@gmail.com \
    --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).