From: Juan Fiol <juanfiol@gmail.com>
To: 2696@emacsbugs.donarmstrong.com
Subject: bug#2696: 23.0.91; flyspell in TeX cite commands
Date: Tue, 17 Mar 2009 23:37:36 -0300 [thread overview]
Message-ID: <49C05E70.3000802@gmail.com> (raw)
In-Reply-To: <49C01740.6030402@gmx.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
martin rudalics wrote:
>> When a \cite command is too large, flyspell starts to check it after a
> given lenght. For
>> instance, flyspell would not check (CORRECTLY) for:
>>
> \cite{Macek1970PRAp235,Shakesh1978PRLp1037,Belkic1979PRp279,Meckbac1981PRAp1793,Garibot1980PRAp572}
>
>> but would highlight the following:
>>
> \cite{Macek1970PRAp235,Shakesh1978PRLp1037,Belkic1979PRp279,Meckbac1981PRAp1793,Garibot1980PRAp572,Garibot1983PRAp2792}
>
>> (it would highlight the last Garibot and PRAp in Garibot1983PRAp2792).
>> It probably is related to the length Emacs search for regular
> expresions but I do not know
>> how to fix it.
>
> `flyspell-tex-command-p' has
>
> (and (re-search-backward "\\\\" (- (point) 100) t)
>
> so maybe replacing 100 by some larger value might help.
>
> martin
>
>
Thanks for the prompt reply,
Martin's suggestion worked. I fixed it and the problem was fixed. How does it
follows now? Will it be corrected for next version of flyspell?
Thanks for your time,
Juan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknAXnAACgkQqiWjWCO20uy/LQCfaFw7aU98NLbYSpRtTgHQhWQl
+G8An2JQpNwul8vyQ3LYzeUmx9nMm9NT
=aq26
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-03-18 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 16:04 bug#2696: 23.0.91; flyspell in TeX cite commands Juan Fiol
2009-03-17 21:33 ` martin rudalics
2009-03-18 2:37 ` Juan Fiol [this message]
2009-03-18 6:26 ` martin rudalics
2011-07-11 14:00 ` Lars Magne Ingebrigtsen
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=49C05E70.3000802@gmail.com \
--to=juanfiol@gmail.com \
--cc=2696@emacsbugs.donarmstrong.com \
--cc=fiol@cab.cnea.gov.ar \
/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).