all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Debugging aspell problems
Date: Thu, 06 Aug 2020 17:12:56 +0200	[thread overview]
Message-ID: <86d04324g7.fsf@csic.es> (raw)
In-Reply-To: 83r1sj9a04.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:
> Let's use much more direct method: Process Explorer from Sysinternals.
> Please configure the Process Explorer (via View->Select Columns) so
> that it shows the following attributes for each process:

Thanks, this is indeed more direct. I did not know it existed. And I can
confirm your results.

> What I see on my system (with Hunspell) is that each time I type M-$,
> the Emacs process's I/O Writes counter increases by 4, and the I/O
> Write Bytes increases by 18.  Which is exactly what I would expect,
> since ispell.el sends these 4 strings to the speller:
>
>    !\n
>    +\n
>    %\n
>    ^buffer\n

I see now the problem. Emacs uses +\n to set aspell into tex mode while
it uses -\n for fundamental or other text modes. When +\n is entered,
mingw64's aspell crashes.

>   . do you perhaps have some local/private dictionary that affects the
>     issue?

No, everything is a pretty much stock configuration.

Sorry for the noise.

-- 
Juan José García Ripoll
http://juanjose.garciaripoll.com
http://quinfog.hbar.es




  reply	other threads:[~2020-08-06 15:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 11:04 Debugging aspell problems Juan José García-Ripoll
2020-08-05 14:26 ` Eli Zaretskii
2020-08-05 19:32   ` Juan José García-Ripoll
2020-08-06 13:31     ` Eli Zaretskii
2020-08-06 15:12       ` Juan José García-Ripoll [this message]
2020-08-06 17:55         ` Eli Zaretskii
2020-08-07  8:06           ` Juan José García-Ripoll

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=86d04324g7.fsf@csic.es \
    --to=juanjose.garciaripoll@gmail.com \
    --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 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.