X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-15.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_THREADED,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,USER_IN_DEF_DKIM_WL X-Spam-Check-By: sourceware.org X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApUKANAKnFCrRDoG/2dsb2JhbABEhVG9EwN9gQiCHgEBAQMBCAoBJUYGBQUGFSYLVwYbCRGHYgUMm3qgNIx5gjuCRGEDiCU1hRqIB4EcjTyBa4MQ Message-ID: <5733F57212A14FD8A2096B318136BA7A@cisco.com> From: "Matt Seitz" To: References: <1743526806 DOT 20121108183618 AT mtu-net DOT ru> <05C4181E65454C1A8F02506A85181CC1 AT cisco DOT com> <69455956 DOT 20121108230605 AT mtu-net DOT ru> In-Reply-To: <69455956.20121108230605@mtu-net.ru> 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, 8 Nov 2012 11:48:32 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: Andrey Repin > > 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? Sorry, I wasn't clear. The "git-gui" program is just telling "aspell" to use the default "aspell" dictionary. It's then up to "aspell" to decide what the default dictionary is. The relevant "git-gui" code appears to be here: http://repo.or.cz/w/git-gui.git/blob/HEAD:/git-gui.sh#l3913 > 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. OK, I can suggest that to the Git maintainers. -- 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