unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Agustin Martin <agustin.martin@hispalinux.es>
To: 6539@debbugs.gnu.org
Subject: bug#6539: ispell-complete-word looks for wrong file (at least on w32)
Date: Tue, 6 Jul 2010 15:48:07 +0200	[thread overview]
Message-ID: <20100706134807.GA3297@agmartin.aq.upm.es> (raw)
In-Reply-To: <AANLkTimerRANmMwyWf4hgCYwScU2JdYUaNYY5E5YeVl9@mail.gmail.com>

On Mon, Jul 05, 2010 at 09:50:35PM +0200, Lennart Borgman wrote:
> On Mon, Jul 5, 2010 at 8:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Lennart Borgman <lennart.borgman@gmail.com>
> >> Date: Mon, 5 Jul 2010 19:55:28 +0200
> >> Cc: agustin.martin@hispalinux.es, 6539@debbugs.gnu.org
> >>
> >> > Why does it matter which file names are tried, if the net result will
> >> > be the same: to fail?
> >>
> >> I thought I did explain that above. The unix style file names can
> >> happen to work on the current default drive if the user did place the
> >> required files there.
> >
> > The chances of the user accidentally putting the file in the same
> > directory where Ispell looks for it, which doesn't exist on Windows
> > and needs to be created, are slim.  The chances of doing that without
> > looking at ispell.el and discovering the defcustom and its default
> > value are even more slim.
> 
> This can rather easily happen. Just imagine a user getting the error
> message and then putting the files there on the current drive.

Note that proposed new error message does not point to an specific
location (just uses 'standard default locations'), but to customize
`ispell-alternate-dictionary'.

-- 
Agustin





  reply	other threads:[~2010-07-06 13:48 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 [this message]
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

  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=20100706134807.GA3297@agmartin.aq.upm.es \
    --to=agustin.martin@hispalinux.es \
    --cc=6539@debbugs.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).