unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#3369: 23.0.94; ispell fails to detect latest aspell version
@ 2009-05-24 22:13 ` Leo
  2009-05-24 23:30   ` bug#3369: marked as done (23.0.94; ispell fails to detect latest aspell version) Emacs bug Tracking System
  0 siblings, 1 reply; 2+ messages in thread
From: Leo @ 2009-05-24 22:13 UTC (permalink / raw)
  To: emacs-pretest-bug

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Function `ispell-check-version' fails on

@(#) International Ispell Version 3.1.20 (but really Aspell 0.61-20071105)

due to this:

  (search-forward-regexp
			"(but really Aspell \\([0-9]+\\.[0-9\\.]+\\)?)" nil t)

Because of this, flyspell-buffer also fails.

It can be fixed by changing to:

  (search-forward-regexp
			"(but really Aspell \\([0-9]+\\.[0-9\\.-]+\\)?)" nil t)

Leo





^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#3369: marked as done (23.0.94; ispell fails to detect latest aspell version)
  2009-05-24 22:13 ` bug#3369: 23.0.94; ispell fails to detect latest aspell version Leo
@ 2009-05-24 23:30   ` Emacs bug Tracking System
  0 siblings, 0 replies; 2+ messages in thread
From: Emacs bug Tracking System @ 2009-05-24 23:30 UTC (permalink / raw)
  To: Chong Yidong

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


Your message dated Sun, 24 May 2009 19:27:18 -0400
with message-id <87skiunktl.fsf@cyd.mit.edu>
and subject line Re: 23.0.94; ispell fails to detect latest aspell version
has caused the Emacs bug report #3369,
regarding 23.0.94; ispell fails to detect latest aspell version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3369: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3369
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 2676 bytes --]

From: Leo <sdl.web@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.94; ispell fails to detect latest aspell version
Date: Sun, 24 May 2009 23:13:58 +0100
Message-ID: <m0zld2xi6x.fsf@cam.ac.uk>

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Function `ispell-check-version' fails on

@(#) International Ispell Version 3.1.20 (but really Aspell 0.61-20071105)

due to this:

  (search-forward-regexp
			"(but really Aspell \\([0-9]+\\.[0-9\\.]+\\)?)" nil t)

Because of this, flyspell-buffer also fails.

It can be fixed by changing to:

  (search-forward-regexp
			"(but really Aspell \\([0-9]+\\.[0-9\\.-]+\\)?)" nil t)

Leo


[-- Attachment #3: Type: message/rfc822, Size: 1189 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Leo <sdl.web@gmail.com>
Cc: 3369-done@emacsbugs.donarmstrong.com
Subject: Re: 23.0.94; ispell fails to detect latest aspell version
Date: Sun, 24 May 2009 19:27:18 -0400
Message-ID: <87skiunktl.fsf@cyd.mit.edu>

> Function `ispell-check-version' fails on
>
> @(#) International Ispell Version 3.1.20 (but really Aspell
> 0.61-20071105)

Fixed, thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-05-24 23:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <87skiunktl.fsf@cyd.mit.edu>
2009-05-24 22:13 ` bug#3369: 23.0.94; ispell fails to detect latest aspell version Leo
2009-05-24 23:30   ` bug#3369: marked as done (23.0.94; ispell fails to detect latest aspell version) Emacs bug Tracking System

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).