all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: agustin.martin@hispalinux.es, 6539@debbugs.gnu.org
Subject: bug#6539: ispell-complete-word looks for wrong file (at least on	w32)
Date: Mon, 05 Jul 2010 20:39:59 +0300	[thread overview]
Message-ID: <83iq4t96a8.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimv_64helPTLcyQLQNlx0pKcr10r_QshUploS2J@mail.gmail.com>

> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Mon, 5 Jul 2010 19:32:33 +0200
> Cc: Agustin Martin <agustin.martin@hispalinux.es>, 6539@debbugs.gnu.org
> 
> > For the rest, the patch looks fine, but why not test /usr/dict/words
> > with file-readable-p as well?  Then, if it does not exist, the
> > defcustom will evaluate to nil, and the error message will be even
> > more to the point.
> 
> 
> Such a test will make things even worse with unix style file names on
> w32 since they with these paths Emacs will look on the current drive.
> That does not have to be the same drive next time the library is
> loaded.

Why does it matter which file names are tried, if the net result will
be the same: to fail?

Read my lips: the _ONLY_ way to make this feature work on Windows is
to customize the value of ispell-complete-word-dict or that of
ispell-alternate-dictionary.  Unless you do that, this feature will
_ALWAYS_ fail on Windows; the only thing we can do is make the error
message more helpful.  And if the option _is_ customized, I trust the
user to include the drive letter in the value.






  reply	other threads:[~2010-07-05 17:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30  9:18 bug#6539: ispell-complete-word looks for wrong file (at least on w32) Lennart Borgman
2010-06-30 10:38 ` Agustin Martin
2010-06-30 11:45   ` Lennart Borgman
2010-06-30 12:27     ` Agustin Martin
2010-06-30 17:35       ` Eli Zaretskii
2010-07-05 11:30         ` Agustin Martin
2010-07-05 11:52         ` Agustin Martin
2010-07-05 12:27           ` Lennart Borgman
2010-07-05 17:23           ` Eli Zaretskii
2010-07-05 17:32             ` Lennart Borgman
2010-07-05 17:39               ` Eli Zaretskii [this message]
2010-07-05 17:55                 ` Lennart Borgman
2010-07-05 18:23                   ` Eli Zaretskii
2010-07-05 19:50                     ` Lennart Borgman
2010-07-06 13:48                       ` Agustin Martin
2010-07-06 15:12             ` Agustin Martin
2010-07-06 18:26               ` Eli Zaretskii
2010-06-30 18:07       ` Lennart Borgman
2010-06-30 17:31     ` Eli Zaretskii
2010-06-30 18:13       ` Lennart Borgman
2010-06-30 20:55         ` Eli Zaretskii
2010-06-30 21:04           ` Lennart Borgman
2010-07-01  3:16             ` Eli Zaretskii
2010-07-01  9:45               ` Lennart Borgman
2010-07-01 16:54                 ` Eli Zaretskii
2010-07-01 17:01                   ` Lennart Borgman
2011-07-13 23:42                   ` Lars Magne Ingebrigtsen
2010-07-01  1:34   ` Stefan Monnier
2010-07-01  3:17     ` Eli Zaretskii
2010-07-23 15:32       ` Stefan Monnier
2010-07-23 16:47         ` Agustin Martin
2010-07-23 18:01         ` Eli Zaretskii

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=83iq4t96a8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=6539@debbugs.gnu.org \
    --cc=agustin.martin@hispalinux.es \
    --cc=lennart.borgman@gmail.com \
    /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.