(base-files 4.1-2) Typos in Default Home Directory Files

2012-11-08 Thread Ethan Warth
I send this to report a comment typo in the the skeleton files automatically added to home folders (package base-files was updated to version 4.1-2 to verify the typos were still in the newest release). 1901/4086 MB RAM 0.00 0.00 0.00 2/7 Thu Nov 08 11:00:55 11:00 PM [0 jobs] [ethan@firetail: +1]

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)

2012-11-08 Thread Matt Seitz
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 jus

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)

2012-11-08 Thread Andrey Repin
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. >

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)

2012-11-08 Thread Matt Seitz
From: Matt Seitz From: Matt Seitz > I looked through "setup.log". I see that something triggered "aspell" > to > be installed on Nov. 5: > What's the best way for me to determine which packaged triggered adding the required dependency "aspell"? I'm suspecting the problem has something

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)

2012-11-08 Thread Matt Seitz
From: Matt Seitz I looked through "setup.log". I see that something triggered "aspell" to be installed on Nov. 5: 2012/11/05 06:48:59 Adding required dependency aspell: Selecting version 0.60.6.1-1 for installation. 2012/11/05 06:48:59 Adding required dependency libaspell15: Selecting versi

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)

2012-11-08 Thread Matt Seitz
From: Andrey Repin From: 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. Howe

Re: Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Earnie Boyd
On Thu, Nov 8, 2012 at 10:15 AM, Thomas Höhenleitner wrote: Please do not top post. > Thanks a lot, Earnie, > > for your answer. I do not know whitch patch command line switch do you > mean. With -l I had already tried. I should have said diff instead of patch. --strip-trailing-cr -- Earnie -

RE: Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Adam Dinwoodie
Thomas Höhenleitner wrote: > >2012/11/8 Thomas Höhenleitner >: >> >> 2012/11/8 Ryan Johnson >: >> Per , please don't include raw email addresses in your replies. This mailing list is archived online, and we'd rather not feed the spammers. See also http://cygwin.c

Re: Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Thomas Höhenleitner
May be because of the attatched file the mail before is not delivered.. Here is a temporary link to the attached file: https://www.dropbox.com/s/7etntr4jukp9t5l/ExamplePatch.zip 2012/11/8 Thomas Höhenleitner : > Hello Ryan, > > first I appologize for the wrong hunks-failed info. I did not remebe

Re: Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Thomas Höhenleitner
Thanks a lot, Earnie, for your answer. I do not know whitch patch command line switch do you mean. With -l I had already tried. In my answer to Ryan follows an example, I created. Bes regards, Thomas 2012/11/8 Earnie Boyd : > On Thu, Nov 8, 2012 at 5:30 AM, Thomas Höhenleitner wrote: > >> >> So

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)

2012-11-08 Thread Andrey Repin
Greetings, Matt Seitz! > It looks like the Fedora team originally installed the "aspell-en" > dictionary by default whenever "aspell" was installed. Then they dropped it > as a dependency for the same reason given earlier in this thread: that it's > not really required for "aspell". Then they ma

Re: Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Ryan Johnson
On 08/11/2012 5:30 AM, Thomas Höhenleitner wrote: Hello, using Cygwin patch.exe in a batch file I ran into the problem that patch failed for some reason ("hunk 1 out of 3 hunks failed"): Investigating this issue I found that inserting "unix2dos my.patch" before applying the patch was my friend!

Re: Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Earnie Boyd
On Thu, Nov 8, 2012 at 5:30 AM, Thomas Höhenleitner wrote: > > So now I had a closer look to the diff generated my.patch file and I > found out, that the file had somehow hybrid line endings: > * the header with the file names was unix-like > * the body with the diff info was dos-like > > The reas

Info for the item "does patch.exe work different than other unx patch tools?" (i.e. "hunk 1 out of 3 hunks failed")

2012-11-08 Thread Thomas Höhenleitner
Hello, using Cygwin patch.exe in a batch file I ran into the problem that patch failed for some reason ("hunk 1 out of 3 hunks failed"): Investigating this issue I found that inserting "unix2dos my.patch" before applying the patch was my friend! Being paranoid I tried "dos2unix my.patch" before