public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@freemail.ru>
To: "Matt Seitz" <matseitz@cisco.com>, cygwin@cygwin.com
Subject: Re: aspell 0.60.6.1-1 does not install any dictionaries by default (RE: git gui 1.7.9-1:  "spell checking is unavailable" error message)
Date: Thu, 08 Nov 2012 19:16:00 -0000	[thread overview]
Message-ID: <69455956.20121108230605@mtu-net.ru> (raw)
In-Reply-To: <05C4181E65454C1A8F02506A85181CC1@cisco.com>

Greetings, Matt Seitz!

>>> https://bugzilla.redhat.com/show_bug.cgi?id=494084
>>>
>>> Does it make sense for Cygwin to follow Fedora's lead, and install
>>> "aspell-en" by default when "aspell" is installed?
>>
>> No, it makes sense to report this issue to Git maintaners.

> OK, I can do that.

> However, based on the Fedora bug reports, it sounds like this could be an 
> issue for other "aspell" client applications.   It appears that the normal 
> behavior for "aspell" clients is to report an error if the "default" 
> dictionary is specified and no dictionary is present.

Application should not error out on mistakes in a third-party module
configuration, that is not even required for application to run, and merely
providing a cosmetic functionality.

> So it seems like the options are:

> 1.  Change git-gui and other "aspell" based applications to suppress their 
> error message when the "default" dictionary is specified and no dictionary 
> is present.

Specified where? If it's a configuration in Git-GUI, it must report it as
inconsistency and suggest the way to amend it.
If it's a configuration in aspell, and Git-GUI merely asking for default
behavior, then again, Git-GUI should check, if the module can work at all,
before trying to use it and throw errors at the user.

> 2.  Change "setup.exe" to install the "default" dictionary (i.e., the 
> dictionary for the current locale) automatically when "aspell" is installed.

Unlikely to happen. Even if do, it would only be a suggestion.
Unless you take the burden of implementing full APT functionality into cygwin
setup.exe.

> 3.  Change "setup.exe" to remind the user to install the "default" 
> dictionary when "aspell" is installed.

> 4.  Keep the current behavior, and let the end-user figure out what went 
> wrong and how to fix it.

> Option 2 seems to be the solution that Fedora went with.


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 08.11.2012, <22:59>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-11-08 19:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  2:07 Matt Seitz
2012-11-08 14:46 ` Andrey Repin
2012-11-08 17:15   ` Matt Seitz
2012-11-08 19:16     ` Andrey Repin [this message]
2012-11-08 19:48       ` Matt Seitz
2012-11-08 17:19 Matt Seitz
2012-11-08 18:34 Matt Seitz

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=69455956.20121108230605@mtu-net.ru \
    --to=anrdaemon@freemail.ru \
    --cc=cygwin@cygwin.com \
    --cc=matseitz@cisco.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.
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).