From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Ispell: Skipping part of text in texinfo-mode
Date: Fri, 30 Aug 2024 15:19:37 +0200 [thread overview]
Message-ID: <m25xri9mhi.fsf@macmutant.fritz.box> (raw)
In-Reply-To: <86o75ae1af.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Aug 2024 13:46:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Then let's discuss them one by one, based on the Texinfo manual (which
> documents much more than you can find in our manuals). Some commands
> need to ignore their arguments, some don't.
Will do so, no problem. My first choice was by driven by auctex.texi
which I tested with.
> For example, @var's argument is more often than not be a real word or
> a phrase made out of words, like @var{next-file}.
I will remove 'var' from the skip list.
> It's definitely a possibility, I think, so we IMO should support it,
> at least as an option.
Hmm, we could say that people who want to use this must enable it with:
(add-hook 'texinfo-mode-hook (lambda ()
(setq ispell-parser 'texinfo)))
otherwise things will be as before.
> Doesn't ispell-check-comments only relevant to
> ispell-comments-and-strings?
Might be, then I still don't understand why my change instructs ispell
to spell-check comments. Something is still off and I don't know what.
> Does this support nested markup, as in
>
> @w{@code{(@var{file} . @var{buffer})}}
>
> in a way that will allow to spell-check "file" and "buffer"? I'm not
> sure syntax-table feature supports nesting.
No, my code ignores everything inside @code{...}. This is actually what
ispell does for .tex files. The syntax-table stuff is to skip over
things like @kbd{C-c @key{@}} @key{RET}} robustly.
Best, Arash
prev parent reply other threads:[~2024-08-30 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 16:25 Ispell: Skipping part of text in texinfo-mode Arash Esbati
2024-08-29 17:51 ` Eli Zaretskii
2024-08-30 8:13 ` Arash Esbati
2024-08-30 10:46 ` Eli Zaretskii
2024-08-30 13:19 ` Arash Esbati [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m25xri9mhi.fsf@macmutant.fritz.box \
--to=arash@gnu.org \
--cc=eliz@gnu.org \
--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.