unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Alice <bobfredalice@googlemail.com>
Cc: 25766@debbugs.gnu.org
Subject: bug#25766: aspell problem in LaTeX mode
Date: Fri, 17 Feb 2017 15:29:51 +0200	[thread overview]
Message-ID: <83wpcpvtbk.fsf@gnu.org> (raw)
In-Reply-To: <CAOJxbrsA11dadga6n+B_Dq3j2p5ru+v22Ti0NXCcODsQmN_Hqw@mail.gmail.com> (message from Bob Alice on Fri, 17 Feb 2017 10:53:44 +0000)


[Please keep the bug address, 25766@debbugs.gnu.org, on the CC list.]

> From: Bob Alice <bobfredalice@googlemail.com>
> Date: Fri, 17 Feb 2017 10:53:44 +0000
> 
> It doesn't work. I tried:
> while((1));do ps -Alf|grep aspell >>results; done
> 
> but the only thing I get is:
> 0 S meuser 4839 4828 0 80 0 - 8093 - 10:42 ? 00:00:00 /usr/bin/aspell -a -m -d en --encoding=utf-8

This is all we need to know, so this did work.

> It doesn't show me what's being passed to aspell even for text where it finds spelling errors.

It isn't supposed to.

Now invoke aspell from your shell prompt exactly as shown above, i.e.

  /usr/bin/aspell -a -m -d en --encoding=utf-8

Aspell will then wait for input from standard input.  Type the string
you see in the ispell.el's debug buffer.  E.g., with hunspell, when I
invoke the command ispell-buffer-with-debug on your LaTeX file, I see
this in the ispell debug buffer:

  ispell-region: string pos (29->53), eol: 53, [in-comment]: [nil], [add-comment]: [nil], [string]: [^\autoref{alice} envolope
]

which tells me that the string it will pass to the speller is
"^\autoref{alice} envolope" (without the quotes).  So type this string
and hit [Enter].  Then see what aspell outputs in return.

Once again, please CC the bug address so that this discussion gets
recorded there.

Thanks.





  parent reply	other threads:[~2017-02-17 13:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 20:52 bug#25766: aspell problem in LaTeX mode Bob Alice
2017-02-17  7:19 ` Eli Zaretskii
     [not found]   ` <CAOJxbrtYVWVwtDCyomQa7ARY9eCHQPUC-X-+Sk4Vqa3RybNJ7Q@mail.gmail.com>
2017-02-17 10:22     ` Eli Zaretskii
     [not found]       ` <CAOJxbrsA11dadga6n+B_Dq3j2p5ru+v22Ti0NXCcODsQmN_Hqw@mail.gmail.com>
2017-02-17 13:29         ` Eli Zaretskii [this message]
2017-02-17 16:21           ` Bob Alice
2017-02-17 16:37             ` Eli Zaretskii
2017-02-18 10:27               ` Bob Alice
2017-02-18 11:52                 ` Eli Zaretskii
2017-02-18 12:45                   ` Bob Alice
2017-02-17 16:46 ` Glenn Morris
2017-02-18 10:42   ` Bob Alice

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=83wpcpvtbk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25766@debbugs.gnu.org \
    --cc=bobfredalice@googlemail.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 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).