unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: Agustin Martin <agustin.martin@hispalinux.es>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCHv2] textmodes/flyspell.el: Don't check pre-word if buffer was switched.
Date: Sat, 20 Apr 2013 11:46:57 -0400	[thread overview]
Message-ID: <xa1tobd9urv2.fsf@mina86.com> (raw)
In-Reply-To: <CAKy3oZpgzwA5Xm9XNcbCJCU1E=2uSSe3T4UbFQXeieMXStqDgA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]

On Sat, Apr 20 2013, Agustin Martin wrote:
> After that I tried harder to reproduce the problem with the original
> unchanged code without success, so I have my doubts about this change being
> really needed or the best one, `(numberp flyspell-pre-point)' test should
> already care of nil `flyspell-pre-point'.

Not exactly.  (numberp flyspell-pre-point) checks the variable before
buffer is switched in `flyspell-post-command-hook' at which point the
variable changes the value.

I confess that I'm not sure how the variable may be nil in given buffer
with `flyspell-pre-buffer' not being nil since those are always set
together, but for some reason I experienced a behaviour which I could
only explain if the following is true:

	(and flyspell-pre-buffer
	     (with-current-buffer flyspell-pre-buffer
	       (not flyspell-pre-point)))

> I'd appreciate a minimal step-by-step guide to reproduce the original
> problem with the original code, if it can be systematically
> reproduced. If it appeared randomly, please provide as much info as
> you can.

I was experiencing the problem every time I sent an email signed with
PGG.  I've never experienced it doing anything else or sending the mail
without signature.  The error in *Messages* reads:

	Error in post-command-hook (flyspell-post-command-hook): (wrong-type-argument integer-or-marker-p nil)

Unfortunately, I wasn't able to get a minimal set of configuration which
makes the problem appear, so it may be caused by interactions which
whatever hundred of configuration options I'm using.

If you wish to take a look, my configuration files are:
* https://github.com/mina86/dot-files/blob/master/dot-emacs
* https://github.com/mina86/dot-files/blob/master/dot-mail

If you want I can try and take a deeper look later on, but cannot
promise anything this week.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--

[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2.2: Type: application/pgp-signature, Size: 835 bytes --]

      reply	other threads:[~2013-04-20 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 18:09 [PATCH] textmodes/flyspell.el (flyspell-post-command-hook): Decided whether to check previous word while in correct buffer Michal Nazarewicz
2013-03-27  1:09 ` Stefan Monnier
2013-03-27 12:47   ` [PATCHv2] textmodes/flyspell.el: Don't check pre-word if buffer was switched Michal Nazarewicz
2013-04-20  4:53     ` Agustin Martin
2013-04-20 15:46       ` Michal Nazarewicz [this message]

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=xa1tobd9urv2.fsf@mina86.com \
    --to=mina86@mina86.com \
    --cc=agustin.martin@hispalinux.es \
    --cc=emacs-devel@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.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).