On 2022-03-01 18:30 -0600, sunnycemet...@gmail.com wrote:
> Consider appending the macro chain with .
That works out pretty nicely indeed, thanks!
--
Akshay.
Consider appending the macro chain with .
Hello,
I've been trying to find a way to suppress error messages in a macro or
a key binding that I create. I couldn't find a builtin way to do so by
reading through the docs and searching online.
To provide a basic example, I have a macro to open the error history,
scrolling to the
On Tue, Mar 03, 2015 at 03:28:03PM -0500, Peter Davis wrote:
> On Tue, Mar 03, 2015 at 08:14:25PM +0100, Matthias Apitz wrote:
> > >
> > > Error running "/Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs
> > > -nw
> > > '/var/folders/kj/ymbjk_bj5v394cx4ffynd8yhgp/T//mutt-pfd-studio-m
On Tue, Mar 03, 2015 at 08:14:25PM +0100, Matthias Apitz wrote:
> >
> > Error running "/Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs
> > -nw
> > '/var/folders/kj/ymbjk_bj5v394cx4ffynd8yhgp/T//mutt-pfd-studio-mac-pro-502-44534-19996952971688465714'"!
> >
> >
> > Not terribly inf
El día Tuesday, March 03, 2015 a las 01:57:34PM -0500, Peter Davis escribió:
> Well, redirecting stderr to a file didn't work. When I tried to run `mutt 2>
> mutterr.log`, the shell just hung there.
>
> I did manage to capture the error using iTerm2 logging, but it was a pain.
> The log capture
On Mon, Mar 02, 2015 at 03:59:16PM +1300, Chris Bannister wrote:
> On Sat, Feb 28, 2015 at 08:17:12PM -0500, Peter Davis wrote:
> > On Sat, Feb 28, 2015 at 10:57:32PM +0100, Matthias Apitz wrote:
> > >
> > > Run mutt in a xterm with logging enabled or, as a last, under
> > > strace/truss to catch
On Mon, Mar 02, 2015 at 03:59:16PM +1300, Chris Bannister wrote:
> On Sat, Feb 28, 2015 at 08:17:12PM -0500, Peter Davis wrote:
> > On Sat, Feb 28, 2015 at 10:57:32PM +0100, Matthias Apitz wrote:
> > >
> > > Run mutt in a xterm with logging enabled or, as a last, under
> > > strace/truss to catch
On Sat, Feb 28, 2015 at 08:17:12PM -0500, Peter Davis wrote:
> On Sat, Feb 28, 2015 at 10:57:32PM +0100, Matthias Apitz wrote:
> >
> > Run mutt in a xterm with logging enabled or, as a last, under
> > strace/truss to catch the messages.
>
> Hmmm. Is it possible to run mutt with
>
> mutt 2> myerr
On Sat, Feb 28, 2015 at 10:57:32PM +0100, Matthias Apitz wrote:
>
> Run mutt in a xterm with logging enabled or, as a last, under
> strace/truss to catch the messages.
Hmmm. Is it possible to run mutt with
mutt 2> myerrorlog
?
--
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com
El día Saturday, February 28, 2015 a las 04:50:57PM -0500, Peter Davis escribió:
> I'm trying to set my editor to 'emacs -nw', but I'm getting some kind of
> error message flashing at the bottom of the
> screen. Unfortunately, the error disappears too quickly for me to read it. Is
> there some w
I'm trying to set my editor to 'emacs -nw', but I'm getting some kind of error
message flashing at the bottom of the
screen. Unfortunately, the error disappears too quickly for me to read it. Is
there some way to redisplay these messages?
Thank you.
-pd
--
Peter Davis
* On 2002.10.14, in <[EMAIL PROTECTED]>,
* "Sven Dogbert Guckes" <[EMAIL PROTECTED]> wrote:
> * Lukas Ruf <[EMAIL PROTECTED]> [2002-10-14 10:40]:
> > I would like to know where mutt writes error messages to.
> > Reading the man pages did not
Richard,
On Mon, 14 Oct 2002, Richard Cattien wrote:
> mutt has errors? :-)
>
not I know of ;-)
wbr,
--
Lukas Ruf
http://www.lpr.ch http://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast,rawip}.org}
Wanna know anything about raw ip? Jo
Hi,
> I would like to know where mutt writes error messages to. Reading the
> man pages did not help me understand how to set on debug messages.
mutt has errors? :-)
bye,
richard
--
Richard `rickski' Cattien <[EMAIL PROTECTED]>
* Lukas Ruf <[EMAIL PROTECTED]> [2002-10-14 10:40]:
> I would like to know where mutt writes error messages to.
> Reading the man pages did not help me
> understand how to set on debug messages.
mutt does not have a debug mode - yet.
Sven
Dear all,
I would like to know where mutt writes error messages to. Reading the
man pages did not help me understand how to set on debug messages.
Thanks,
Lukas
--
Lukas Ruf
http://www.lpr.ch http://www.maremma.ch
http://www.{{topsy,nodeos}.net
On 06/10/02, 03:27:18PM -0500, David T-G wrote:
Then you must set spoolfile somewhere in your muttrc in order for mutt to
> be able to find ! when you start up, because -HOMESPOOL says that your
> mail is found under /var. That makes the "unknown variable" all that
> more peculiar.
My ~/.muttrc
John --
...and then John P Verel said...
%
% On 06/10/02, 02:24:34PM -0500, David T-G wrote:
%
% > % -HOMESPOOL. FWIW, this is a stand alone machine, hooked to a cable
% >
% > That tells me that your mail should be found in /var/*/mail rather than
...
% Procmail delivers my mail to /home/joh
On 06/10/02, 02:24:34PM -0500, David T-G wrote:
> % -HOMESPOOL. FWIW, this is a stand alone machine, hooked to a cable
>
> That tells me that your mail should be found in /var/*/mail rather than
> in your home dir, so you probably *do* need a mutt_dotlock with mail
> group perms to do dotlocki
John --
...and then John P Verel said...
%
% On 06/10/02, 01:46:21PM -0500, David T-G wrote:
%
...
% > :set ?spoolfile
% >
% > in mutt tell you?
% >
% Says "unknow option" -- which seems consistent with configuration option
Now *that* is odd. Do you not set spoolfile in your muttrc? Wha
On 06/10/02, 01:46:21PM -0500, David T-G wrote:
> % My mail comes via fetchmail from my ISP's POP server.
>
> I imagine it goes into your home dir somewhere, then, but it could go
> into the system mail spool. What does
>
> :set ?spoolfile
>
> in mutt tell you?
>
Says "unknow option" -- w
John, et al --
...and then John P Verel said...
%
% On 06/10/02, 12:44:57PM -0500, David T-G wrote:
%
% > Don't know why it did, but it should be pluralized.
% Pluralized it and it's fixed :)
Good :-)
% > % % Second problem: % % When I press F1, I get key not bound error.
% >
% > Do you ha
On 06/10/02, 02:25:28PM -0400, John P Verel wrote:
> The 1.2.5 version is in /etc, the 1.4 version is in the source for 1.4.
> Where should the new one live?
Fixed it. Mutt set up SYSCONFDIR as /home/john/mutt1.4/etc However, it
did not copy my Muttrc to it, nor change the path to the manual i
On 06/10/02, 12:44:57PM -0500, David T-G wrote:
> Don't know why it did, but it should be pluralized.
Pluralized it and it's fixed :)
> % % Second problem: % % When I press F1, I get key not bound error.
>
> Do you have the F1 binding in the system muttrc, or perhaps in yours?
> It's in the sys
John --
...and then John P Verel said...
%
% Made Mutt 1.4 today. I'm getting the following errors:
%
% Error in /home/john/.muttrc, line 359: thread: unknown sorting method
...
% set sort=thread (Works fine in 1.2)
Don't know why it did, but it should be pluralized.
%
% Second problem:
%
Made Mutt 1.4 today. I'm getting the following errors:
Error in /home/john/.muttrc, line 359: thread: unknown sorting method
This refers to a line which reads:
set sort=thread (Works fine in 1.2)
Second problem:
When I press F1, I get key not bound error.
Third thing:
In make intall log I
On Wed, Jan 10, 2001 at 04:53:14AM +, Tim Johnson wrote:
>Hello:
>
>I have compiled mutt version 1.2.5.
>
>./configure was run with --enable-pop as the only option.
>
>Upon running *make install*, I get the following error messages:
>
>/bin/sh: sgml2html:
Hello:
I have compiled mutt version 1.2.5.
./configure was run with --enable-pop as the only option.
Upon running *make install*, I get the following error messages:
/bin/sh: sgml2html: command not found
/usr/bin/install: manual*.html: No such file or directory
chgrp: you are not a member
On Thu, Dec 14, 2000 at 06:27:54PM +0200, Peter Pentchev wrote:
> I dare you to name a relatively-modern version of csh, tcsh, bash, ksh
> or zsh, which does not have test/[ as a builtin ;)
Ok, you got me there. I'm sure they all have this as a builtin, but
was that at least the historical reaso
On Thu, Dec 14, 2000 at 11:12:48AM -0500, Josh Huber wrote:
> On Thu, Dec 14, 2000 at 07:37:47AM -0800, David Alban wrote:
> > Of course, this would be O.K. I prefer the [[ ]] operator (found in
> > ksh and bash 2.x) because it is smarter and more resistant to syntax
> > errors that occur with [
On Thu, Dec 14, 2000 at 07:37:47AM -0800, David Alban wrote:
> Of course, this would be O.K. I prefer the [[ ]] operator (found in
> ksh and bash 2.x) because it is smarter and more resistant to syntax
> errors that occur with [ ] if a variable is undefined. But
> certainly one can use [ ] and
Peter,
At 2000/12/14/12:19 +0200 Peter Pentchev <[EMAIL PROTECTED]> wrote:
> Just a side note - is there a reason you could not use the standard '['
> test operator? Along with some quoting of possibly-null arguments, of
> course.. something like:
>
> [ -n "$1" ] && muttrc="$1"
>
> [ ! -e "$mu
On Wed, Dec 13, 2000 at 06:12:43PM -0800, David Alban wrote:
> Greetings!
>
> At 2000/12/13/18:58 -0600 David Champion <[EMAIL PROTECTED]> wrote:
> > You mean just to test the muttrc file and report parse errors?
> >
> > How about:
> > mutt -F test.muttrc -f /dev/null -e "push x" >/dev/null
Greetings!
At 2000/12/13/18:58 -0600 David Champion <[EMAIL PROTECTED]> wrote:
> You mean just to test the muttrc file and report parse errors?
>
> How about:
> mutt -F test.muttrc -f /dev/null -e "push x" >/dev/null
That's *way* cool!
Here's a script[1] which uses your idea to test $1 i
On 2000.12.13, in <[EMAIL PROTECTED]>,
"Charles Curley" <[EMAIL PROTECTED]> wrote:
> When working on my .muttrc, it would be very nice if there were some way
> to see error messages generated by bugs in the .muttrc. Is there any such
> mechanism?
You mean j
When working on my .muttrc, it would be very nice if there were some way
to see error messages generated by bugs in the .muttrc. Is there any such
mechanism?
--
-- C^2
No windows were crashed in the making of this email.
Looking for fine software and/or web pages?
http://w3
CTED]>
Cc: "Rod Pike" <[EMAIL PROTECTED]>
Sent: Tuesday, October 17, 2000 1:42 AM
Subject: Re: newbie? How to view mutt error messages.
Rod --
...and then Rod Pike said...
% Greetings,
%
% Newbie question
Actually, this happens in lots of programs :-)
%
% When I start ( and quit ) mutt there are sometimes error messages a the
% bottom of the screen that flash up and then are gone. Is there a log
Yep. Ain't it great
On Sat, Oct 14, 2000 at 08:57:30PM -0200 or so it is rumoured hereabouts,
Rod Pike thought:
> Greetings,
>
> Newbie question
>
> When I start ( and quit ) mutt there are sometimes error messages a the
> bottom of the screen that flash up and then are gone. Is there a log
&g
Greetings,
Newbie question
When I start ( and quit ) mutt there are sometimes error messages a the
bottom of the screen that flash up and then are gone. Is there a log
that I can look at that contains these messages so I can debug my setup?
Cheers,
Rod
On 2000-02-09 23:05:36 -0500, Chris Woodfield wrote:
> Going through the archives, I found this mail, which mirrors
> exactly the errors I'm getting. I'm running 1.0.1-us.
1.0.1-us doesn't have any PGP support. However, documentation on it
may have survived.
> THe other thing is that according
On Fri, Jan 21, 2000 at 05:10:38PM +, Lars Hecking wrote:
>
> > Error in /home/jmnova3/.muttrc, line 102: pgp_v2: unknown variable
> > Error in /home/jmnova3/.muttrc, line 103: pgp_v2_language: unknown variable
> > Error in /home/jmnova3/.muttrc, line 104: pgp_v2_pubring: unknown variable
> >
On 01/21, Lars Hecking rearranged the electrons to read:
> Now I *know* these variables won't work for this version of mutt because
> the pgp/gpg interface changed between 1.0 and 1.1 (or 0.95/0.96).
>
> See doc/PGP-Notes.txt and contrib/{gpg,pgp2,pgp5}.rc, and the usual
> funny manual.
Ugh
> Error in /home/jmnova3/.muttrc, line 102: pgp_v2: unknown variable
> Error in /home/jmnova3/.muttrc, line 103: pgp_v2_language: unknown variable
> Error in /home/jmnova3/.muttrc, line 104: pgp_v2_pubring: unknown variable
> Error in /home/jmnova3/.muttrc, line 105: pgp_v2_secring: unknown varia
Hey, it's me again. Hopefully this will be my last letter with a
problem! :-)
'mutt -v' says : Mutt 1.1.2i (2000-01-08)
So I know it should be able to handle PGP without a problem. However,
when I define a bunch of PGP settings in my .muttrc file as it says I
should be able to, I get the foll
Winston Moy <[EMAIL PROTECTED]> wrote:
>
> Thanks for the info... I was able to locate the cause, while I was
> tailing the active syslog... I had a corrupt alias database... once
> the database was cleaned up, Mutt was happy...
Wow, that's amazing:
> > > "Error sending message, child exited
Winston Moy <[EMAIL PROTECTED]> wrote:
>
> "Error sending message, child exited 70 (Internal error.)" when sending out.
Sendmail doesn't like the command line it's being given by Mutt. Here's
a simple shell script:
#!/bin/sh
echo "Args: " "$@" >> /tmp/sendmail.log
Save this script, th
- Begin Forwarded Message -
Date: Fri, 22 Oct 1999 08:43:30 -0500 (CDT)
From: Winston Moy <[EMAIL PROTECTED]>
Subject: "Error sending message, child exited 70 (Internal error.)" messages
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
MIME-Version:
he following error
"Error sending message, child exited 70 (Internal error.)" when sending out.
I invoked configure with the following options:
1. --with-slang
2. --with -slang --with-regex
Both version of mutt gave the same error messages.
50 matches
Mail list logo
