all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: 35967@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#35967: [PATCH] avoid flyspell error if point is at bob
Date: Fri, 14 Jun 2019 21:14:15 +0200	[thread overview]
Message-ID: <87pnngdlo8.fsf@igel.home> (raw)
In-Reply-To: <87pnngqaau.fsf@gmail.com> (Alex Branham's message of "Fri, 14 Jun 2019 13:41:29 -0500")

On Jun 14 2019, Alex Branham <alex.branham@gmail.com> wrote:

> diff --git a/lisp/textmodes/flyspell.el b/lisp/textmodes/flyspell.el
> index d18916dfd0..22f9db4363 100644
> --- a/lisp/textmodes/flyspell.el
> +++ b/lisp/textmodes/flyspell.el
> @@ -423,9 +423,10 @@ flyspell-prog-text-faces
>  
>  (defun flyspell-generic-progmode-verify ()
>    "Used for `flyspell-generic-check-word-predicate' in programming modes."
> -  ;; (point) is next char after the word. Must check one char before.
> -  (let ((f (get-text-property (- (point) 1) 'face)))
> -    (memq f flyspell-prog-text-faces)))
> +  (unless (eql (point) (point-min))
> +    ;; (point) is next char after the word. Must check one char before.
> +    (let ((f (get-text-property (- (point) 1) 'face)))

Perhaps change this to (1- (point)).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."





  reply	other threads:[~2019-06-14 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 20:43 bug#35967: [PATCH] avoid flyspell error if point is at bob Alex Branham
2019-05-29 16:08 ` Eli Zaretskii
2019-05-30 11:58   ` Basil L. Contovounesios
2019-06-11 14:12   ` npostavs
2019-06-11 14:39     ` Eli Zaretskii
2019-06-14 18:17       ` Alex Branham
2019-06-14 18:31         ` npostavs
2019-06-14 18:41           ` Alex Branham
2019-06-14 19:14             ` Andreas Schwab [this message]
2019-06-17 19:04               ` Alex Branham
2019-06-18 12:18   ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnngdlo8.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=35967@debbugs.gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=npostavs@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.