all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "djh" <henman@it.to-be.co.jp>
Cc: henman@it.to-be.co.jp
Subject: Incompatibility in emacs & aspell-0.60.4
Date: Wed, 09 Aug 2006 16:54:38 +0900	[thread overview]
Message-ID: <20060809165438.3032@henman-np.b-eng.it.to-be.co.jp> (raw)



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?


Regards,
   Darel Henman

             reply	other threads:[~2006-08-09  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09  7:54 djh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-18 16:35 Incompatibility in emacs & aspell-0.60.4 Chong Yidong
2006-08-29  8:16 ` djh
2006-08-29 20:27   ` Kevin Rodgers
2006-08-30  3:00   ` Chong Yidong
2006-10-26 11:28     ` Agustin Martin

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=20060809165438.3032@henman-np.b-eng.it.to-be.co.jp \
    --to=henman@it.to-be.co.jp \
    /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.