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 ! ;)
