Re: OT Big Dummy mutt question
Bob Bernstein wrote: > On Sun, 23 Apr 2017, songbird wrote: > >> i'm using the version of mutt in testing/stretch >> and can say that i have no setting in .muttrc at >> all and it just works. > > I tried the "no setting in .muttrc" and that did the trick. > > Which strikes me as sorta weird, but then, with so much > weirdness around nowadays, why pick on mutt? > > What should we call that approach, Alt-Minimalist? > > Incidentally: > > $ mutt -v | grep SPELL > -ISPELL ha! interesting! :) > $ which ispell > /usr/bin/ispell > > Thanks all! y.w. :) glad it is working. also interesting to compare: $ mutt -v | grep SPELL ISPELL="/usr/bin/ispell" (currently at version: NeoMutt 20170113 (1.7.2) on i386) songbird
Re: OT Big Dummy mutt question
On Sun, 23 Apr 2017, songbird wrote: i'm using the version of mutt in testing/stretch and can say that i have no setting in .muttrc at all and it just works. I tried the "no setting in .muttrc" and that did the trick. Which strikes me as sorta weird, but then, with so much weirdness around nowadays, why pick on mutt? What should we call that approach, Alt-Minimalist? Incidentally: $ mutt -v | grep SPELL -ISPELL $ which ispell /usr/bin/ispell Thanks all! -- "Natasha! First we shoot jet, then we go after moose and squirrel."
Re: OT Big Dummy mutt question
Bob Bernstein wrote: > Mutt (1.5.23) is rebuffing my every attempt to get ispell > working. Currently I have in .muttrc: > > set ispell="ispell --mode=email" > > This threw no error when mutt launched, so it was with high > spirits that I tried to send off deliberately misspelled emails. > Alas and alack. these arrived at their intended destinations > with their test misspellings intact. > > Could it be (he asked) that spell-checking in mutt does not > follow on auto-magically (if that is the word I'm looking for > here) via the bare expedient of creating an entry in .muttrc > such as is on display several lines above? > > Throwing myself on Google's mercy leads me to believe that the > only editor permitted (so to speak) with mutt is vim. I refuse > to accept this, and, if found to be true, would protest in the > strongest available terms through proper channels. > > Please help. i'm using the version of mutt in testing/stretch and can say that i have no setting in .muttrc at all and it just works. what does mutt -v | grep SPELL say? and/or: if you remove your set line does it work? or if you use /usr/bin/ispell? songbird
Re: OT Big Dummy mutt question
On Sun, 23 Apr 2017, David Wright wrote: According to my key bindings, you should press i when in the compose menu [...] Yes, my 'help' there also shows i associated with ispell. But pressing i only causes the screen to blip very momentarily without showing any ispell activity and then return to where it was. No change is made to the message. ispell seems functional when tried from the command line. :( -- "Natasha! First we shoot jet, then we go after moose and squirrel."
Re: OT Big Dummy mutt question
On Sun 23 Apr 2017 at 19:47:49 (-0400), Bob Bernstein wrote: > Mutt (1.5.23) is rebuffing my every attempt to get ispell working. > Currently I have in .muttrc: > > set ispell="ispell --mode=email" > > This threw no error when mutt launched, so it was with high spirits > that I tried to send off deliberately misspelled emails. Alas and > alack. these arrived at their intended destinations with their test > misspellings intact. > > Could it be (he asked) that spell-checking in mutt does not follow > on auto-magically (if that is the word I'm looking for here) via the > bare expedient of creating an entry in .muttrc such as is on display > several lines above? According to my key bindings, you should press i when in the compose menu, the one where you then press y to send it, or e to edit it again. At this point, the message is in /tmp or /var/tmp or wherever you configured it. > Throwing myself on Google's mercy leads me to believe that the only > editor permitted (so to speak) with mutt is vim. I refuse to accept > this, and, if found to be true, would protest in the strongest > available terms through proper channels. Eh? You can use any editor; I use emacs. You should put set editor="invocation command and parameters" in the same file as the ispell setting. /usr/share/doc/mutt/manual.txt* Cheers, David.
OT Big Dummy mutt question
Mutt (1.5.23) is rebuffing my every attempt to get ispell working. Currently I have in .muttrc: set ispell="ispell --mode=email" This threw no error when mutt launched, so it was with high spirits that I tried to send off deliberately misspelled emails. Alas and alack. these arrived at their intended destinations with their test misspellings intact. Could it be (he asked) that spell-checking in mutt does not follow on auto-magically (if that is the word I'm looking for here) via the bare expedient of creating an entry in .muttrc such as is on display several lines above? Throwing myself on Google's mercy leads me to believe that the only editor permitted (so to speak) with mutt is vim. I refuse to accept this, and, if found to be true, would protest in the strongest available terms through proper channels. Please help. Thank you. -- "Natasha! First we shoot jet, then we go after moose and squirrel."
