David --
...and then David Champion said...
%
% On 2002.01.13, in <[EMAIL PROTECTED]>,
% "David T-G" <[EMAIL PROTECTED]> wrote:
% >
% > I don't necessarily agree that mutt should spit out a message, though I
% > can see that this could be confusing. What I would do would be to go
% > ...
On 2002.01.13, in <[EMAIL PROTECTED]>,
"David T-G" <[EMAIL PROTECTED]> wrote:
>
> I don't necessarily agree that mutt should spit out a message, though I
> can see that this could be confusing. What I would do would be to go
> ...
> % Feedback is an important element of any user interfac
Sam --
...and then Samuel Padgett said...
%
% David T-G <[EMAIL PROTECTED]> writes:
%
% > I think the actual flea is that ispell does not follow
% > $wait_key, myself.
%
% I'll buy that.
Sold!
%
% > Who wants to start a movement to get that changed, or submit a
% > feature patch?
%
% I co
David T-G <[EMAIL PROTECTED]> writes:
> I think the actual flea is that ispell does not follow
> $wait_key, myself.
I'll buy that.
> Who wants to start a movement to get that changed, or submit a
> feature patch?
I could do the former or the latter, although the latter would
require permission
Sam, et al --
...and then Samuel Padgett said...
%
...
% return code with "echo $?". When running Ispell from Mutt,
% however, you don't have this. You press 'i'. Nothing happens.
% You press 'i' again. Nothing happens. "Why isn't Ispell
% running?" you think. "What did I break? Were ther
At some point hitherto, Samuel Padgett hath spake thusly:
> Derek D. Martin <[EMAIL PROTECTED]> writes:
>
> > This is part of the Unix philosophy, which goes something like, "if
> > there's nothing to report, then report nothing." Armed with this
> > knowledge, there's really no need for such a
Kenneth Pronovici <[EMAIL PROTECTED]> writes:
> Ok, I get it. Errors and output disappear so fast that you can't
> really see them, which I hadn't noticed before. Doing what I suggested
> above would at least let you see that *something* ran, though. Hmm, not
> as worthwhile as I thought, sor
> then,
>
>> vi .muttrc
>
>ispell=muttspell.sh
>
> It seems like this would probably do what you want, right?
Ok, I get it. Errors and output disappear so fast that you can't
really see them, which I hadn't noticed before. Doing what I suggested
above would at least let you see th
> Feedback is an important element of any user interface, GUI or
> text-based, UNIX or not.
Ok... so I'd have to agree... but why can't you just wrap aspell in a
script of your own, i.e.
> vi muttspell.sh
#!/bin/sh
aspell $*
echo "Aspell completed with return ($?)"
then,
> vi .
Derek D. Martin <[EMAIL PROTECTED]> writes:
> This is part of the Unix philosophy, which goes something like, "if
> there's nothing to report, then report nothing." Armed with this
> knowledge, there's really no need for such a message...
I would amend that to say, "If there's no need to report
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Samuel Padgett hath spake thusly:
> I sometimes spell check my messages before I send them using
> Ispell (actually, Aspell), and often I have no errors. When this
> is the case, however, Mutt does not indicate that the spell
I sometimes spell check my messages before I send them using
Ispell (actually, Aspell), and often I have no errors. When this
is the case, however, Mutt does not indicate that the spell
checker ran at all! Is there any way I can tell Mutt to display a
message, for instance, "Ispell exited with r
12 matches
Mail list logo
