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?
