GNU bug report logs - #807
Incompatibility in emacs & aspell-0.60.4

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 807 in the body.
You can then email your comments to 807 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #3 received at quiet <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: quiet <quiet <at> debbugs.gnu.org>
Subject: Incompatibility in emacs & aspell-0.60.4
Date: Wed, 27 Aug 2008 16:38:09 -0400

Package: emacs,w32
Tags: unreproducible

(Filing a report for an old item from FOR-RELEASE.)

http://lists.gnu.org/archive/html/emacs-devel/2006-08/msg00310.html

Initial report:
  
  I am trying to establish where an incompatibility resides.
  
  Suspicious points are in emacs's changes to ispell.el, the
  ispell-init-process, or most likely in the new (Oct. 2005) aspell
  code. Or it might be my particular configuration with cygwin. But,
  again I didn't have a problem with the old version of aspell and the
  new one works from the command line.
  
  Description of the problem:
  
  The error message is displayed after the 2nd successfull
  (ispell-get-coding-system) upon trying to do another step.  See below:
  
  
  File; ispell.el
  Line: # 2535
  
          (set-process-coding-system ispell-process
          (ispell-get-coding-system)
                                     (ispell-get-coding-system) ))
                                                               ^
  ---------
  Result: iso-8859-1 [2 times]
  error: "Input file descriptor of ispell closed"
  ---------
  
  If instrumented and issued a 'G'o cmd. the debuger stops at
  line # 2560
           (error "%s" (mapconcat 'identity ispell-filter "\n"))))  
  
  
  The is the same error message when ran without the debugger.
  
  "ispell-init-process: Error: nroff: dlopen returned "No such file or
  directory".
  
  
  I have sent out a similar not to the aspell group, but I want to ask
  if anyone on this group has tried to use
  
     cvs emacs with aspell-0.60.4 
  
  and if so did you have the probelm I ran into?

Message #14 received at 807 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: henman <at> it.to-be.co.jp
Cc: Glenn Morris <rgm <at> gnu.org>, 807 <at> debbugs.gnu.org
Subject: Re: Incompatibility in emacs & aspell-0.60.4
Date: Sun, 11 Sep 2011 19:30:18 +0200

Glenn Morris <rgm <at> gnu.org> writes:

>   I am trying to establish where an incompatibility resides.
>
>   Suspicious points are in emacs's changes to ispell.el, the
>   ispell-init-process, or most likely in the new (Oct. 2005) aspell
>   code. Or it might be my particular configuration with cygwin. But,
>   again I didn't have a problem with the old version of aspell and the
>   new one works from the command line.
>
>   Description of the problem:
>
>   The error message is displayed after the 2nd successfull
>   (ispell-get-coding-system) upon trying to do another step.  See below:

Is this still a problem in Emacs 23?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Message #19 received at 807 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: 807 <at> debbugs.gnu.org
Subject: Re: Incompatibility in emacs & aspell-0.60.4
Date: Sun, 11 Sep 2011 19:33:24 +0200

Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes:

> Is this still a problem in Emacs 23?

The submitter's address bounces, so I'm closing this report.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.