From: Lennart Borgman <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6539@debbugs.gnu.org, agustin6martin@gmail.com
Subject: bug#6539: ispell-complete-word looks for wrong file (at least on w32)
Date: Wed, 30 Jun 2010 23:04:11 +0200 [thread overview]
Message-ID: <AANLkTilb2TOjU8FZa49asdU15742hntRTeehjMB1c-Ih@mail.gmail.com> (raw)
In-Reply-To: <831vbob5qz.fsf@gnu.org>
On Wed, Jun 30, 2010 at 10:55 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Lennart Borgman <lennart.borgman@gmail.com>
>> Date: Wed, 30 Jun 2010 20:13:42 +0200
>> Cc: agustin6martin@gmail.com, 6539@debbugs.gnu.org
>>
>> On Wed, Jun 30, 2010 at 7:31 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> From: Lennart Borgman <lennart.borgman@gmail.com>
>> >> Date: Wed, 30 Jun 2010 13:45:56 +0200
>> >> Cc: 6539@debbugs.gnu.org
>> >>
>> >> OK, thanks. The default for ispell-alternate-dictionary is not a full
>> >> path on w32 so that is a bug.
>> >
>> > How would you suggest to fix this "bug"? I see only 2 possibilities
>> > (besides leaving this as they are and letting w32 users customize the
>> > value, as I did): either (a) signal an error, or (b) search the entire
>> > hard disk storage for a file named `words'.
>>
>> I would perhaps suggest leaving it as nil on w32. That would make it
>> more clear that this is not a left over from unix systems, but rather
>> something a user must setup on w32 systems to make it work.
>
> Then you'd see
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>
> Is that really better?
Hm, maybe not. Then perhaps a suitable file name for w32 is better?
An accompanying explanatory message would of course be even better.
next prev parent reply other threads:[~2010-06-30 21:04 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilb2TOjU8FZa49asdU15742hntRTeehjMB1c-Ih@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6539@debbugs.gnu.org \
--cc=agustin6martin@gmail.com \
--cc=eliz@gnu.org \
/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 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).