Re: ispell file-error "Setting current directory"

Re: ispell file-error "Setting current directory"

[Dan Jacobson]

rms> Here's how check-ispell-version chooses the directory to use:

rms> 	(default-directory (or (and (boundp 'temporary-file-directory)
rms> 				    temporary-file-directory)
rms> 			       default-directory))

rms> Please examine those variables and see what directory it chooses and
rms> why.

It happened again today.  Had to start a new emacs as replying to mail
was blocked by it.  It must be a complex interaction between
ispell, gnus, ffap, (and ange-ftp? (which I never use)).
In all buffers concerned, the variables you mentioned are $HOME or
/tmp, i.e., OK.

 All I know is
Debugger entered--Lisp error: (file-error "Setting current directory"
"no such file or directory" "/home/jidanni/http:/www.geocities.com/jidanni/")
  call-process("ispell" nil t nil "-vv")
  check-ispell-version()
  ispell-init-process()
  ispell-buffer-local-words()
  ispell-accept-buffer-local-defs()
  flyspell-accept-buffer-local-defs()
  flyspell-mode-on()
  flyspell-mode(1)
  #[nil "^HM-^D^G^@M-A M-^H^H?M-^E^V^@M-BM-C VM-^E^V^@M-DM-E!M-^G" [buffer-read-only turn-on-auto-fill 88888 buffer-size flyspell-mode 1] 2]()
  run-hooks(text-mode-hook)
  text-mode()
  pop-to-buffer("*wide reply to Johnny Lin*<4>")
  message-pop-to-buffer("*wide reply to Johnny Lin*<4>")
  message-reply(nil t)
  gnus-summary-reply((13503) t)
  gnus-summary-reply-with-original(nil t)
  gnus-summary-wide-reply-with-original(nil)
  call-interactively(gnus-summary-wide-reply-with-original)

The geocities  buffer was created by a typo minutes earlier. I had
immediately killed it after it appeared.
emacs-version"21.3.1"

Re: ispell file-error "Setting current directory"

[Kevin Rodgers]

Dan Jacobson wrote:
 > rms> Here's how check-ispell-version chooses the directory to use:
 >
 > rms> 	(default-directory (or (and (boundp 'temporary-file-directory)
 > rms> 				    temporary-file-directory)
 > rms> 			       default-directory))
 >
 > rms> Please examine those variables and see what directory it chooses and
 > rms> why.
 >
 > It happened again today.  Had to start a new emacs as replying to mail
 > was blocked by it.  It must be a complex interaction between
 > ispell, gnus, ffap, (and ange-ftp? (which I never use)).
 > In all buffers concerned, the variables you mentioned are $HOME or
 > /tmp, i.e., OK.

That can't be.

 >  All I know is
 > Debugger entered--Lisp error: (file-error "Setting current directory"
 > "no such file or directory" 
"/home/jidanni/http:/www.geocities.com/jidanni/")
 >   call-process("ispell" nil t nil "-vv")
 >   check-ispell-version()

In the *Backtrace* buffer, point should be at the beginning of the
call-process() line.  Move to the check-ispell-version() line, and
please report what these commands display:

e (current-buffer) RET
e default-directory RET
e temporary-file-directory RET

 >   ispell-init-process()
 >   ispell-buffer-local-words()
 >   ispell-accept-buffer-local-defs()
 >   flyspell-accept-buffer-local-defs()
 >   flyspell-mode-on()
 >   flyspell-mode(1)
 >   #[nil "^HM-^D^G^@M-A M-^H^H?M-^E^V^@M-BM-C VM-^E^V^@M-DM-E!M-^G" 
[buffer-read-only turn-on-auto-fill 88888 buffer-size flyspell-mode 1] 2]()
 >   run-hooks(text-mode-hook)
 >   text-mode()
 >   pop-to-buffer("*wide reply to Johnny Lin*<4>")
 >   message-pop-to-buffer("*wide reply to Johnny Lin*<4>")
 >   message-reply(nil t)
 >   gnus-summary-reply((13503) t)
 >   gnus-summary-reply-with-original(nil t)
 >   gnus-summary-wide-reply-with-original(nil)
 >   call-interactively(gnus-summary-wide-reply-with-original)
 >
 > The geocities  buffer was created by a typo minutes earlier. I had
 > immediately killed it after it appeared.
 > emacs-version"21.3.1"

-- 
Kevin Rodgers

Re: ispell file-error "Setting current directory"

[Dan Jacobson]

>>>>> "K" == Kevin Rodgers <ihs_4664@yahoo.com> writes:
K> please report what these commands display:

I would but Stallman emailed me this patch meaning it's probably fixed
now. Maybe next time I should forward these pacthes to the list, who
are in much better position to test them than I, and who should know
that a fix has already been found.

*** ispell.el	01 Nov 2004 13:20:28 -0500	1.149
--- ispell.el	23 Nov 2004 17:04:09 -0500	
***************
*** 769,774 ****
--- 769,776 ----
  	(if buf (kill-buffer buf)))
        (set-buffer (get-buffer-create " *ispell-tmp*"))
        (erase-buffer)
+       (unless (file-exists-p default-directory)
+ 	(setq default-directory (expand-file-name "~/")))
        (setq status (call-process
  		    ispell-program-name nil t nil
  		    ;; aspell doesn't accept the -vv switch.

Re: ispell file-error "Setting current directory"

[Kevin Rodgers]

Dan Jacobson wrote:
>>>>>>"K" == Kevin Rodgers <ihs_4664@yahoo.com> writes:
> 
> K> please report what these commands display:
> 
> I would but Stallman emailed me this patch meaning it's probably fixed
> now. Maybe next time I should forward these pacthes to the list, who
> are in much better position to test them than I, and who should know
> that a fix has already been found.
> 
> *** ispell.el	01 Nov 2004 13:20:28 -0500	1.149
> --- ispell.el	23 Nov 2004 17:04:09 -0500	
> ***************
> *** 769,774 ****
> --- 769,776 ----
>   	(if buf (kill-buffer buf)))
>         (set-buffer (get-buffer-create " *ispell-tmp*"))
>         (erase-buffer)
> +       (unless (file-exists-p default-directory)
> + 	(setq default-directory (expand-file-name "~/")))
>         (setq status (call-process
>   		    ispell-program-name nil t nil
>   		    ;; aspell doesn't accept the -vv switch.

That's not a fix, it's a workaround.  The bug that sets default-directory
to something other than a directory still exists.

-- 
Kevin Rodgers

Re: ispell file-error "Setting current directory"

[Stefan Monnier]

K> please report what these commands display:
>> I would but Stallman emailed me this patch meaning it's probably fixed
>> now. Maybe next time I should forward these pacthes to the list, who
>> are in much better position to test them than I, and who should know
>> that a fix has already been found.
>> *** ispell.el	01 Nov 2004 13:20:28 -0500	1.149
>> --- ispell.el	23 Nov 2004 17:04:09 -0500	
>> ***************
>> *** 769,774 ****
>> --- 769,776 ----
>> (if buf (kill-buffer buf)))
>> (set-buffer (get-buffer-create " *ispell-tmp*"))
>> (erase-buffer)
>> +       (unless (file-exists-p default-directory)
>> + 	(setq default-directory (expand-file-name "~/")))
>> (setq status (call-process
>> ispell-program-name nil t nil
>> ;; aspell doesn't accept the -vv switch.

> That's not a fix, it's a workaround.  The bug that sets default-directory
> to something other than a directory still exists.

No I think it's a fix.  `ispell' does not need to run in any particular
directory (i.e. it doesn't have to run in the directory of the file on which
you're working).  `default-directory' can be validly set to a non-existent
directory (either because it hasn't been made yet, or because it's on
a remote host, or ...).
So you may as well run ispell in ~/ and get on with your life.


        Stefan

Re: ispell file-error "Setting current directory"

[Stefan Monnier]

>> All I know is
>> Debugger entered--Lisp error: (file-error "Setting current directory"
>> "no such file or directory"
>    "/home/jidanni/http:/www.geocities.com/jidanni/")
>> call-process("ispell" nil t nil "-vv")
>> check-ispell-version()

Where does http:/www.geocities.com/jidanni/ come from?
Obviously the problem is that some piece of code is using a URL for
a file name.

> In the *Backtrace* buffer, point should be at the beginning of the
> call-process() line.  Move to the check-ispell-version() line, and
> please report what these commands display:

> e (current-buffer) RET
> e default-directory RET
> e temporary-file-directory RET

The `e' command does not pay attention to the position of point in the
debugger buffer.


        Stefan