Re: Suppress error messages
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.
Re: Suppress error messages
Consider appending the macro chain with .
Suppress error messages
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 bottom by default—so that I see the latest messages: macro index - '' 'display error-history' However, when the entries in the error history don't fill the screen all the way, I get an error message saying "Bottom of message is shown." Obviously this isn't a terribly huge deal and I can simply ignore the error message, but it's still an unnecessary annoyance to see errors that are—at least to me—inconsequential. Essentially, what I'm looking for is the mutt equivalent of vim's ":silent!" command which would perhaps work in the following fashion: macro index - '' Any tips or tricks on how to suppress these error messages would be greatly appreciated! -- Akshay Hegde
Re: Flashing error messages?
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-mac-pro-502-44534-19996952971688465714'! Not terribly informative, actually. Try running the same command from the shell; for me it looks like the arg after -nw is a file name; try to configure in ~/.muttrc a shell script to launch /Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs ... to check better the args passed to it and the errors of emacs itself. Ah! the arg is a file name ... the temp file through which mutt and emacs pass the message draft. I did try running `emacs -nw` from the command line, and it worked with no problems. However, when I taked on that file name, I got a slew of errors, possibly due to that // that mutt inserted for some reason: [pfd-studio-mac-pro:~] peterdavis% /Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs -nw '/var/folders/kj/ymbjk_bj5v394cx4ffynd8yhgp/T//mutt-pfd-studio-mac-pro-502-44534-19996952971688465714' Warning: arch-dependent data dir (/Users/xin/Documents/emacs-mac-port/build/libexec/emacs/24.3/x86_64-apple-darwin11.4.2/) does not exist. Warning: arch-independent data dir (/Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/etc/) does not exist. Warning: Lisp directory `/Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/lisp' does not exist. Warning: Lisp directory `/Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/leim' does not exist. Error: charsets directory not found: /Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/etc/charsets Emacs will not function correctly without the character map files. Please check your installation! Thank you. Now to unravel this. Well, just to wrap this up, I finally unravelled this. I have multiple Emacsen installed, from a long history, etc. So this was mainly a matter of making sure mutt was invoking the right one by specifying a full path in the editor command. Thanks! -pd -- Peter Davis The Tech Curmudgeon http://www.techcurmudgeon.com
Re: Flashing error messages?
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 the messages. Hmmm. Is it possible to run mutt with mutt 2 myerrorlog ? What happened when you tried it? I'm afraid I have not had a chance to get back to this. I'll report here when I do. Thanks, -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com
Re: Flashing error messages?
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 captured all the escape sequences, etc. that mutt uses to paint the screen. Here's the error: 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 informative, actually. Try running the same command from the shell; for me it looks like the arg after -nw is a file name; try to configure in ~/.muttrc a shell script to launch /Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs ... to check better the args passed to it and the errors of emacs itself. matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 La referencia de la Duma a la anexión de la RDA, en este caso al contrario con la Crimlía sin referéndum, no solamente tiene gracia sino da en el blanco.- Marinos Yannikos @MarinosYannikos en un blog de RTdeutsch.
Re: Flashing error messages?
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 the messages. Hmmm. Is it possible to run mutt with mutt 2 myerrorlog ? What happened when you tried it? 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 captured all the escape sequences, etc. that mutt uses to paint the screen. Here's the error: 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 informative, actually. Thanks, -pd -- Peter Davis The Tech Curmudgeon http://www.techcurmudgeon.com
Re: Flashing error messages?
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 informative, actually. Try running the same command from the shell; for me it looks like the arg after -nw is a file name; try to configure in ~/.muttrc a shell script to launch /Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs ... to check better the args passed to it and the errors of emacs itself. Ah! the arg is a file name ... the temp file through which mutt and emacs pass the message draft. I did try running `emacs -nw` from the command line, and it worked with no problems. However, when I taked on that file name, I got a slew of errors, possibly due to that // that mutt inserted for some reason: [pfd-studio-mac-pro:~] peterdavis% /Applications/Emacs-mac-port.app/Contents/MacOS/bin/emacs -nw '/var/folders/kj/ymbjk_bj5v394cx4ffynd8yhgp/T//mutt-pfd-studio-mac-pro-502-44534-19996952971688465714' Warning: arch-dependent data dir (/Users/xin/Documents/emacs-mac-port/build/libexec/emacs/24.3/x86_64-apple-darwin11.4.2/) does not exist. Warning: arch-independent data dir (/Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/etc/) does not exist. Warning: Lisp directory `/Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/lisp' does not exist. Warning: Lisp directory `/Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/leim' does not exist. Error: charsets directory not found: /Users/xin/Documents/emacs-mac-port/build/share/emacs/24.3/etc/charsets Emacs will not function correctly without the character map files. Please check your installation! Thank you. Now to unravel this. -pd -- Peter Davis The Tech Curmudgeon http://www.techcurmudgeon.com
Re: Flashing error messages?
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 myerrorlog ? What happened when you tried it? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Flashing error messages?
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 The Tech Curmudgeon http://www.techcurmudgeon.com
Re: Flashing error messages?
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 way to redisplay these messages? Run mutt in a xterm with logging enabled or, as a last, under strace/truss to catch the messages. HIH matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 La referencia de la Duma a la anexión de la RDA, en este caso al contrario con la Crimlía sin referéndum, no solamente tiene gracia sino da en el blanco.- Marinos Yannikos @MarinosYannikos en un blog de RTdeutsch.
Re: Flashing error messages?
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
mutt 1.4 -- where does mutt write error messages to?
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,{promethos,netbeast,rawip}.org}
Wanna know anything about raw ip? Join [EMAIL PROTECTED] on www.rawip.org
Re: mutt 1.4 -- where does mutt write error messages to?
* 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
Re: mutt 1.4 -- where does mutt write error messages to?
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]
Re: mutt 1.4 -- where does mutt write error messages to?
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? Join [EMAIL PROTECTED] on www.rawip.org
Re: mutt 1.4 -- where does mutt write error messages to?
* 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 help me understand how to set on debug messages. mutt does not have a debug mode - yet. Yes, it does. You have to compile with --enable-debug, then run with -dN, where N is a number from 1-4 indicating how fine-grained you want to get. (I think it only cares about 1-4 -- I think all numbers higher than 4 give the same result as 4 -- but I could be wrong.) The output goes into ~/.muttdebug0. .muttdebug0 is renamed to .muttdebug1, etc. Almost like pine. -- -D.We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. LET'S HAVE SUCH A COFFEE! NOW! [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
Making 1.4: Error messages
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 get:
if test -f /home/john/mutt1.4/bin/mutt_dotlock test xmail != x ; then
\
chgrp mail /home/john/mutt1.4/bin/mutt_dotlock \
chmod 2755 /home/john/mutt1.4/bin/mutt_dotlock || \
{ echo Can't fix mutt_dotlock's permissions! 2 ; exit 1 ; }
\
fi
chgrp: changing group of `/home/john/mutt1.4/bin/mutt_dotlock':
Operation not permitted
Can't fix mutt_dotlock's permissions!
make[2]: *** [install-exec-local] Error 1
Is this important?
John
Re: Making 1.4: Error messages
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:
%
% 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 system muttrc by default. What do you see when you hit ? to
look at your current bindings? Is it there at all?
%
% Third thing:
%
% In make intall log I get:
%
% if test -f /home/john/mutt1.4/bin/mutt_dotlock test xmail != x ; then
% \
% chgrp mail /home/john/mutt1.4/bin/mutt_dotlock \
% chmod 2755 /home/john/mutt1.4/bin/mutt_dotlock || \
% { echo Can't fix mutt_dotlock's permissions! 2 ; exit 1 ; }
% \
% fi
% chgrp: changing group of `/home/john/mutt1.4/bin/mutt_dotlock':
% Operation not permitted
% Can't fix mutt_dotlock's permissions!
% make[2]: *** [install-exec-local] Error 1
%
% Is this important?
It just means you're installing as you instead of root but that you built
mutt to expect to find a mutt_dotlock to do locking for it. If you have
an old mutt_dotlock on the system then I would say it's no biggie EXCEPT
that recently someone else posted that mutt compiles in the location of
mutt_dotlock instead of searching your path, so in the worst case you
might have to symlink your mutt_dotlock to the system one with the proper
perms. Only testing will tell if you really need it. If your mail is
not in /var/*/mail where only mail can create files then you don't even
need special perms (well, assuming that you can always write in your own
dirs, anyway).
%
% John
HTH HAND
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg28848/pgp0.pgp
Description: PGP signature
Re: Making 1.4: Error messages
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 system muttrc by default. What do you see when you hit ?
to look at your current bindings? Is it there at all?
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?
% % Third thing: % % In make intall log I get: % % if test -f
/home/john/mutt1.4/bin/mutt_dotlock test xmail != x ; then % \ %
chgrp mail /home/john/mutt1.4/bin/mutt_dotlock \ % chmod
2755 /home/john/mutt1.4/bin/mutt_dotlock || \ % { echo Can't
fix mutt_dotlock's permissions! 2 ; exit 1 ; } % \ % fi % chgrp:
changing group of `/home/john/mutt1.4/bin/mutt_dotlock': % Operation
not permitted % Can't fix mutt_dotlock's permissions! % make[2]: ***
[install-exec-local] Error 1 % % Is this important?
It just means you're installing as you instead of root but that you
built mutt to expect to find a mutt_dotlock to do locking for it. If
you have an old mutt_dotlock on the system then I would say it's no
biggie EXCEPT that recently someone else posted that mutt compiles in
the location of mutt_dotlock instead of searching your path, so in the
worst case you might have to symlink your mutt_dotlock to the system
one with the proper perms. Only testing will tell if you really need
it. If your mail is not in /var/*/mail where only mail can create
files then you don't even need special perms (well, assuming that you
can always write in your own dirs, anyway).
My mail comes via fetchmail from my ISP's POP server.
If I look at the configuration options for 1.2.5, I see -USE_DOTLOCK.
These settings came via the rpm from Red Hat. 1.4 shows +USE_SETGID and
+USE_DOTLOCK, plus +DL_STANDALONE. Could these setting be sources of
the problem?
Re: Making 1.4: Error messages
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 in the macro. I did and it's fixed.
Re: Making 1.4: Error messages
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 have the F1 binding in the system muttrc, or perhaps in yours? % It's in the system muttrc by default. What do you see when you hit ? % to look at your current bindings? Is it there at all? % % 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? You won't be able to write in /etc 'cuz you're not root, so under your home tree (--prefix=...) is good. % % % % Third thing: % % In make intall log I get: % % if test -f You really shouldn't reformat other people's paragraphs :-) ... % it. If your mail is not in /var/*/mail where only mail can create % files then you don't even need special perms (well, assuming that you % can always write in your own dirs, anyway). % % 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? % % If I look at the configuration options for 1.2.5, I see -USE_DOTLOCK. % These settings came via the rpm from Red Hat. 1.4 shows +USE_SETGID and % +USE_DOTLOCK, plus +DL_STANDALONE. Could these setting be sources of % the problem? Well, it's just a difference rather than a problem. If you turned off USE_DOTLOCK you wouldn't have to worry about installing the dotlock program but you'd then have to be sure that other locking worked. ...and then John P Verel said... % % 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 Right. % did not copy my Muttrc to it, nor change the path to the manual in the Now *that* is interesting; I am almost certain it should have done the copy. You did finish up with a make install, right? % macro. I did and it's fixed. Yeah, it won't change that. Someone should probably file a flea but, well, one of these days... HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28853/pgp0.pgp Description: PGP signature
Re: Making 1.4: Error messages
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 -- which seems consistent with configuration option -HOMESPOOL. FWIW, this is a stand alone machine, hooked to a cable mode, poping mail using fetchmail. % % If I look at the configuration options for 1.2.5, I see -USE_DOTLOCK. % These settings came via the rpm from Red Hat. 1.4 shows +USE_SETGID and % +USE_DOTLOCK, plus +DL_STANDALONE. Could these setting be sources of % the problem? Well, it's just a difference rather than a problem. If you turned off USE_DOTLOCK you wouldn't have to worry about installing the dotlock program but you'd then have to be sure that other locking worked. Doesn't procmail (used here) take care of locking? % Fixed it. Mutt set up SYSCONFDIR as /home/john/mutt1.4/etc However, it Right. % did not copy my Muttrc to it, nor change the path to the manual in % the F1 macro. Now *that* is interesting; I am almost certain it should have done the copy. You did finish up with a make install, right? Yep. John
Re: Making 1.4: Error messages
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? What if you try to change folders to ! (that's the folder name); does it work? % -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 dotlocking -- though, again, your system one might be found and do the job. % mode, poping mail using fetchmail. Still, I've never seen a setup that doesn't have a spoolfile :-) % ... % Well, it's just a difference rather than a problem. If you turned off % USE_DOTLOCK you wouldn't have to worry about installing the dotlock % program but you'd then have to be sure that other locking worked. % % Doesn't procmail (used here) take care of locking? Not when you're saving a message to another folder; mutt has to lock a mailbox when it writes to it or cleans it. % ... % % Now *that* is interesting; I am almost certain it should have done the % copy. You did finish up with a make install, right? % Yep. Interesting... % % John HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28855/pgp0.pgp Description: PGP signature
Re: Making 1.4: Error messages
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/john/Mail, as default mailbox. Most, % of course, gets filtered into various mbox files by procmail. 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. Well, we've figured out the answers to your original questions; we should probably let this thread die :-) % % John HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28857/pgp0.pgp Description: PGP signature
Re: Making 1.4: Error messages
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 says: set spoolfile='~/Mail/mbox' Well, we've figured out the answers to your original questions; we should probably let this thread die :-) Morte ! ;)
Re: make install error messages
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: command not found /usr/bin/install: manual*.html: No such file or directory chgrp: you are not a member of group `mail': Operation not permitted Can't fix mutt_dotlock's permissions! make[2]: *** [install-exec-local] Error 1 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 The mutt executable appears to have been installed properly in /usr/local/bin. Are these error message to be of concern to me? If so, what may I be doing wrong. I would say you're not going to have man pages, and you may or may not have trouble reading your mail. Mutt has to lock your mailbox with mutt_dotlock in most cases. If you cannot give that program the right suid/sgid permissions (any permission/uid/gid that will write in your mail spool directory), your box cannot establish a proper exclusive use lock (so that another process such as Sendmail cannot alter your mail spool file while Mutt is trying to read/write it, and vice versa). By and large, mail programs (both MDAs and MUAs) will just quit, or some sleep(3) a while and try again a certain number of times. As per the documentation somewhere, the suid/gid functionality was broken out into a separate exe so that debugging of that one small piece (a helper exe) would reduce the sheer volume of exploitable code. It's almost a programmatic firewall of sorts. -- Oo---o, Oo---o, O-weem-oh-wum-ooo-ayyy In the jungle, the silicon jungle, the process sleeps tonight. Joe Philipps [EMAIL PROTECTED], http://www.philippsfamily.org/Joe/ public PGP/GPG key 0xFA029353 available via http://www.keyserver.net PGP signature
make install error messages
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 of group `mail': Operation not permitted Can't fix mutt_dotlock's permissions! make[2]: *** [install-exec-local] Error 1 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 The mutt executable appears to have been installed properly in /usr/local/bin. Are these error message to be of concern to me? If so, what may I be doing wrong. TIA Tim
Re: Error messages
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
That's *way* cool!
Here's a script[1] which uses your idea to test $1 if it's defined and
$HOME/.muttrc if it isn't:
(the script itself quoted for context)
#!/bin/bash
pgm=`basename $0`
die () {
echo 12 "$pgm: $1"
exit 1
} # die
muttrc=$HOME/.muttrc.common
[[ -n $1 ]] muttrc="$1"
[[ ! -e $muttrc ]] die "$muttrc: no such file"
[[ ! -f $muttrc ]] die "$muttrc: not regular file"
[[ ! -r $muttrc ]] die "$muttrc: cannot open"
echo | mutt -F "$muttrc" -f /dev/null -e "push nnx" /dev/null
[snip]
P.S. If you run this script and get:
[[: command not found
[[: command not found
[[: command not found
[[: command not found
you need to upgrade to bash 2.x.
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 "$muttrc" ] die "$muttrc: no such file"
[ ! -f "$muttrc" ] die "$muttrc: not regular file"
[ ! -r "$muttrc" ] die "$muttrc: cannot open"
Just this way, it works for me in FreeBSD's /bin/sh, which is pretty much
as standard a Bourne shell as you can get..
G'luck,
Peter
--
This inert sentence is my body, but my soul is alive, dancing in the sparks of your
brain.
Re: Error messages
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 "$muttrc" ] die "$muttrc: no such file" [ ! -f "$muttrc" ] die "$muttrc: not regular file" [ ! -r "$muttrc" ] die "$muttrc: cannot open" 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 then double quote the variables within, as you have done. Just this way, it works for me in FreeBSD's /bin/sh, which is pretty much as standard a Bourne shell as you can get.. FreeBSD doesn't come with bash? (Maybe I should have used perl. :-) -- This inert sentence is my body, but my soul is alive, dancing in the sparks of your brain. Cool .sig. :-) David -- Live in a world of your own, but always welcome visitors.
Re: Error messages
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 then double quote the variables within, as you have done. AFAIK, it also doesn't fork a process as well, using [[ ]] the tests are done internally to bash/ksh, and are thus much faster. -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
Re: Error messages
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 [ ] if a variable is undefined. But certainly one can use [ ] and then double quote the variables within, as you have done. AFAIK, it also doesn't fork a process as well, using [[ ]] the tests are done internally to bash/ksh, and are thus much faster. I dare you to name a relatively-modern version of csh, tcsh, bash, ksh or zsh, which does not have test/[ as a builtin ;) And to answer an unquoted question in David Alban's mail, FreeBSD does not come with bash in the base system, it does have both bash1 and bash2 in its Ports Collection, and as packages on the officially distributed FreeBSD CD's. G'luck, Peter -- What would this sentence be like if it weren't self-referential?
Re: Error messages
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 reason for this? I seem to remember this being a reason to use [[ ]] in the past. Thanks for the tip, :) -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
Error messages
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.trib.com/~ccurley
Re: Error messages
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 just to test the muttrc file and report parse errors? How about: mutt -F test.muttrc -f /dev/null -e "push x" /dev/null -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Error messages
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 if it's defined and
$HOME/.muttrc if it isn't:
#!/bin/bash
pgm=`basename $0`
die () {
echo 12 "$pgm: $1"
exit 1
} # die
muttrc=$HOME/.muttrc.common
[[ -n $1 ]] muttrc="$1"
[[ ! -e $muttrc ]] die "$muttrc: no such file"
[[ ! -f $muttrc ]] die "$muttrc: not regular file"
[[ ! -r $muttrc ]] die "$muttrc: cannot open"
echo | mutt -F "$muttrc" -f /dev/null -e "push nnx" /dev/null
The "echo |" accounts for the situation where there are so many errors
that mutt prompts the user to hit the enter key:
source: reading aborted due too many errors in /etc/hosts
Press any key to continue...
The n's in front of the x in the push statement are to answer any
interactive mutt questions with "no" before exiting mutt. For
instance, because I don't use ~/Mail, mutt will ask me:
/usr/people/alban/Mail does not exist. Create it? ([y]/n):
and if I only pushed an "x" then then "x" would be used in an attempt to
answer the question. And "x" is not an acceptable answer to mutt. So
when a user ran the above script in this situation, the script would
appear to hang, because mutt was waiting for the answer to the question.
In addition, if the user knew enough to answer "n", the script would
*still* seem to hang. The reason is this. With "push x", the "x" would
have already been used in the first attempt to answer the question. And
because the "x" is no longer pending, it will not be used to exit, and
the mailbox is entered (even if it is /dev/null) and will sit there with
mutt awaiting the next command. Of course, the savvy user could enter
"nx" instead of just "n". The "echo" and the "push nnx" in the
script should make this unnecessary.
And if there are no interactive questions to be answered, then each
"n" causes mutt to harmlessly try to repeat a search that has never
been specified.
David
P.S. If you run this script and get:
[[: command not found
[[: command not found
[[: command not found
[[: command not found
you need to upgrade to bash 2.x.
[1] I call the script mutttest but undoubtedly there's a better name
than that for it.
--
Live in a world of your own, but always welcome visitors.
Re: newbie? How to view mutt error messages.
Yes, yes. There's a log which contains the full error message. Perhaps someone can give you the exact file -- David www.richSOB.com - Original Message - From: "David T-G" [EMAIL PROTECTED] To: "Mutt Users' List" [EMAIL PROTECTED] Cc: "Rod Pike" [EMAIL PROTECTED] Sent: Tuesday, October 17, 2000 1:42 AM Subject: Re: newbie? How to view mutt error messages.
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 that mutt is so fast? % that I can look at that contains these messages so I can debug my setup? I don't know that compiling with debugging turned on would help, but firing off script before starting mutt and then taking a look at the resultant output file will at least let you see that error text (in the middle of all of the other screen-painting stuff that has to make it a pretty ugly file to review). % % Cheers, % Rod HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. PGP signature
Re: newbie? How to view mutt error messages.
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 that I can look at that contains these messages so I can debug my setup? do a mutt 2~/mutt-errs That will redirect error messages to the file mutt-errs in your home directory. -- Conor Daly [EMAIL PROTECTED] Domestic Sysadmin :-)
newbie? How to view mutt error messages.
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
Re: PGP error messages
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 to said doc/manual.txt, the only options for pgp_default_version are pgp2, pgp5, and gpg. I just installed 6.5.2...am I going to be able to use that, or do I have to roll back to 5.x? Get an "i" version of mutt and either use the included pgp6.rc, or set pgp_default_version to "pgp6". -- http://www.guug.de/~roessler/
Re: PGP error messages
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
Error in /home/jmnova3/.muttrc, line 105: pgp_v2_secring: unknown variable
Error in /home/jmnova3/.muttrc, line 106: pgp_default_version: unknown variable
Error in /home/jmnova3/.muttrc, line 107: pgp_receive_version: unknown variable
Error in /home/jmnova3/.muttrc, line 108: pgp_send_version: unknown variable
Error in /home/jmnova3/.muttrc, line 109: pgp_key_version: unknown variable
source: errors in /home/jmnova3/.muttrc
Press any key to continue...
Now I *know* these variables work for other people, because I've looked
through the example .rc files linked from the mutt.org website. What am
I doing wrong?
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.
Going through the archives, I found this mail, which mirrors exactly the
errors I'm getting. I'm running 1.0.1-us.
Funny thing is, all of these variables are referred to in the
doc/manual.txt file, except for the pgp_v2* variables. I can't even put
the pgp_default_version variable in my .muttrc without getting the unkown
variable editor.
THe other thing is that according to said doc/manual.txt, the only options
for pgp_default_version are pgp2, pgp5, and gpg. I just installed
6.5.2...am I going to be able to use that, or do I have to roll back to
5.x?
-Chris Woodfield
PGP error messages
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 following errors when starting mutt: 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 variable Error in /home/jmnova3/.muttrc, line 106: pgp_default_version: unknown variable Error in /home/jmnova3/.muttrc, line 107: pgp_receive_version: unknown variable Error in /home/jmnova3/.muttrc, line 108: pgp_send_version: unknown variable Error in /home/jmnova3/.muttrc, line 109: pgp_key_version: unknown variable source: errors in /home/jmnova3/.muttrc Press any key to continue... Now I *know* these variables work for other people, because I've looked through the example .rc files linked from the mutt.org website. What am I doing wrong? (For the record, however, I can view sign PGP messages without a problem. It's just the variables that seem to be giving me trouble.) - Jamie
Re: PGP error messages
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 variable
Error in /home/jmnova3/.muttrc, line 106: pgp_default_version: unknown variable
Error in /home/jmnova3/.muttrc, line 107: pgp_receive_version: unknown variable
Error in /home/jmnova3/.muttrc, line 108: pgp_send_version: unknown variable
Error in /home/jmnova3/.muttrc, line 109: pgp_key_version: unknown variable
source: errors in /home/jmnova3/.muttrc
Press any key to continue...
Now I *know* these variables work for other people, because I've looked
through the example .rc files linked from the mutt.org website. What am
I doing wrong?
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.
Error sending message, child exited 70 (Internal error.) messages
Hi, I've recently compiled the following mutt version (mutt -v below) on a Sun Ultra 5 running Solaris 2.7. Mutt 1.0pre4us (1999-10-11) Copyright (C) 1996-9 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.7 [using slang 10309] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/lib/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. I can read my inbox, but I would get the 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. Any pointers, ideas ,recommendation would be appreciated. Thanks +---+ | Winston Moy Email: [EMAIL PROTECTED] | | Texas Instruments | | 6500 Chase Oaks Blvd. M/S: 8440 Pc Drop: PSK3| | Plano, Tx. 75086 | | Ph: (972) 575-2278| +---+
Error sending message, child exited 70 (Internal error.) messages
- 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: 1.0 Content-MD5: 00utInUpcjOYJxq+arbWdw== Hi, I've recently compiled the following mutt version (mutt -v below) on a Sun Ultra 5 running Solaris 2.7. Mutt 1.0pre4us (1999-10-11) Copyright (C) 1996-9 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.7 [using slang 10309] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/lib/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. I can read my inbox, but I would get the 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. Any pointers, ideas ,recommendation would be appreciated. Thanks +---+ | Winston Moy Email: [EMAIL PROTECTED] | | Texas Instruments | | 6500 Chase Oaks Blvd. M/S: 8440 Pc Drop: PSK3| | Plano, Tx. 75086 | | Ph: (972) 575-2278| +---+ - End Forwarded Message - +---+ | Winston Moy Email: [EMAIL PROTECTED] | | Texas Instruments | | 6500 Chase Oaks Blvd. M/S: 8440 Pc Drop: PSK3| | Plano, Tx. 75086 | | Ph: (972) 575-2278| +---+
Re: Error sending message, child exited 70 (Internal error.) messages
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, then in Mutt, "set sendmail=/path/to/script". Then, send a dummy message, and when finished, check the /tmp/sendmail.log file to see what arguments sendmail was supposed to be called with. Then try calling sendmail with those arguments and see why it fails. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Error sending message, child exited 70 (Internal error.) messages
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 70 (Internal error.)" when sending out. The "Internal Error" message was actually correct! It's just that, from the way the message is reported, it's not terribly obvious that the child process is sendmail, and that it was sendmail that had the internal error. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
