Re: mutt 1.5 much slower than mutt 1.4
Am 25.07.2012 12:47, schrieb Anton Shterenlikht:
On Tue, Jul 24, 2012 at 11:00:39PM +0200, Matthias Andree wrote:
Am 24.07.2012 19:18, schrieb Anton Shterenlikht:
mail/mutt is much slower on my amd64 and ia64
-current boxes after it was updated from 1.4
to 1.5. Each keystroke takes few seconds to
act. Below is my mutt 1.5 config:
...
Anybody else is seeing this behaviour?
Not here on amd64 9-stable -- which may have little relevance for
10-current.
Any advice?
Any chance to figure out what mutt is doing, like with truss or
similar?
I'll need to read up on this.
I'm not sure if I can trust the truss WRT return values (looks like a 32
vs 64 bit issue), there tons of unknown error.
But there is a recurring action around dealing with
/tmp/mutt-mech-cluster*. This I/O might be expensive, depending on the
/tmp file system. RAM disk might be useful to speed things up... Any
idea what's it doing?
getpid() = 4295169008
(0x1000313f0)
getpid() = 4295169008
(0x1000313f0)
lstat(/tmp/.muttJqtqdK,0x7fffc0a0) ERR#4295172128
'Unknown error: 204832'
mkdir(/tmp/.muttJqtqdK,0700) = 4295170448
(0x100031990)
open(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj,O_RDWR|O_NOFOLLOW|O_CREAT|O_EXCL,0600)
= 4295170328 (0x100031918)
close(4) = 4295170688
(0x100031a80)
link(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj,/tmp/mutt-mech-cluster241-XSYQpzbj)
= 4295170808 (0x100031af8)
lstat(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj,{
mode=-rw--- ,inode=331538,size=0,blksize=16384 }) = 4295172128 (0x100032020)
lstat(/tmp/mutt-mech-cluster241-XSYQpzbj,{ mode=-rw---
,inode=331538,size=0,blksize=16384 }) = 4295172128 (0x100032020)
unlink(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj) = 4295170928
(0x100031b70)
unlink(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj)
ERR#4295170928 'Unknown error: 203632'
rmdir(0x7fffc878,0x1001b2c30,0x2,0x2,0x2,0xa000c813d400)
= 0 (0x0)
open(/tmp/mutt-mech-cluster241-XSYQpzbj,O_RDWR|O_NOFOLLOW|O_CREAT,0600) =
4295170328 (0x100031918)
lstat(/tmp/mutt-mech-cluster241-XSYQpzbj,{ mode=-rw---
,inode=331538,size=0,blksize=16384 }) = 4295172128 (0x100032020)
fstat(4,{ mode=-rw--- ,inode=331538,size=0,blksize=16384 }) =
4295171888 (0x100031f30)
fcntl(4,F_GETFL,) = 4295168408
(0x100031198)
fstat(4,{ mode=-rw--- ,inode=331538,size=0,blksize=16384 }) =
4295171888 (0x100031f30)
write(4,From r...@bristol.ac.uk Sun Jul ...,2041) = 4295172488
(0x100032188)
lseek(4,0x0,SEEK_SET) = 4295169848
(0x100031738)
fstat(4,{ mode=-rw--- ,inode=331538,size=2041,blksize=16384 }) =
4295171888 (0x100031f30)
read(4,From r...@bristol.ac.uk Sun Jul ...,16384) = 4295178608
(0x100033970)
close(4) = 4295170688
(0x100031a80)
unlink(/tmp/mutt-mech-cluster241-XSYQpzbj) = 4295170928
(0x100031b70)
Is debugging turned on; was mutt built WITH_DEBUG=yes?
yes, I just rebuilt with this set.
Uh, I rather meant that debugging might cause unoptimized code, but
given such repeated I/O to /tmp files I think that's more the culprit.
Any of the patches causing it?
Do you dare remount /tmp as asynchronous file system? I don't see
fsync(), so async might help a bit, and is reasonable for /tmp.
Can you verify the header cache databases, or move them away just for
the sake of the experiment?
sorry, I don't know what you mean here.
You enabled header caches during the build, and if they were excessively
large or broken, that might also cause slowdowns; but they need to be
run-time configured, which you did not, so forget this.
Does it help if you make clean before building world? This has
cured
strance effects on occasions in -STABLE (RELENG_[6-9]) branches for
me.
Well, I might do this later, if no other
clue emerges.
Looking at the truss output, unless the 32nd bit set is required by the
IA64 calling conventions, that may be necessary regardless of the mutt
issue.
ok, thanks, I'll ask in ia64 list.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt 1.5 much slower than mutt 1.4
Am 25.07.2012 12:47, schrieb Anton Shterenlikht:
On Tue, Jul 24, 2012 at 11:00:39PM +0200, Matthias Andree wrote:
Am 24.07.2012 19:18, schrieb Anton Shterenlikht:
mail/mutt is much slower on my amd64 and ia64
-current boxes after it was updated from 1.4
to 1.5. Each keystroke takes few seconds to
act. Below is my mutt 1.5 config:
...
Anybody else is seeing this behaviour?
Not here≥ on amd64 9-stable -- which may have little relevance for
10-current.
Any advice?
Any chance to figure out what mutt is doing, like with truss or similar?
I'll need to read up on this.
I'm not sure if I can trust the truss WRT return values (looks like a 32
vs 64 bit issue), there tons of unknown error.
But there is a recurring action around dealing with
/tmp/mutt-mech-cluster*. This I/O might be expensive, depending on the
/tmp file system. RAM disk might be useful to speed things up... Any
idea what's it doing?
getpid() = 4295169008 (0x1000313f0)
getpid() = 4295169008 (0x1000313f0)
lstat(/tmp/.muttJqtqdK,0x7fffc0a0) ERR#4295172128 'Unknown error:
204832'
mkdir(/tmp/.muttJqtqdK,0700) = 4295170448
(0x100031990)
open(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj,O_RDWR|O_NOFOLLOW|O_CREAT|O_EXCL,0600)
= 4295170328 (0x100031918)
close(4) = 4295170688 (0x100031a80)
link(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj,/tmp/mutt-mech-cluster241-XSYQpzbj)
= 4295170808 (0x100031af8)
lstat(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj,{ mode=-rw---
,inode=331538,size=0,blksize=16384 }) = 4295172128 (0x100032020)
lstat(/tmp/mutt-mech-cluster241-XSYQpzbj,{ mode=-rw---
,inode=331538,size=0,blksize=16384 }) = 4295172128 (0x100032020)
unlink(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj) = 4295170928
(0x100031b70)
unlink(/tmp/.muttJqtqdK/mutt-mech-cluster241-XSYQpzbj) ERR#4295170928
'Unknown error: 203632'
rmdir(0x7fffc878,0x1001b2c30,0x2,0x2,0x2,0xa000c813d400) = 0 (0x0)
open(/tmp/mutt-mech-cluster241-XSYQpzbj,O_RDWR|O_NOFOLLOW|O_CREAT,0600) =
4295170328 (0x100031918)
lstat(/tmp/mutt-mech-cluster241-XSYQpzbj,{ mode=-rw---
,inode=331538,size=0,blksize=16384 }) = 4295172128 (0x100032020)
fstat(4,{ mode=-rw--- ,inode=331538,size=0,blksize=16384 }) = 4295171888
(0x100031f30)
fcntl(4,F_GETFL,) = 4295168408 (0x100031198)
fstat(4,{ mode=-rw--- ,inode=331538,size=0,blksize=16384 }) = 4295171888
(0x100031f30)
write(4,From r...@bristol.ac.uk Sun Jul ...,2041) = 4295172488 (0x100032188)
lseek(4,0x0,SEEK_SET) = 4295169848 (0x100031738)
fstat(4,{ mode=-rw--- ,inode=331538,size=2041,blksize=16384 }) =
4295171888 (0x100031f30)
read(4,From r...@bristol.ac.uk Sun Jul ...,16384) = 4295178608 (0x100033970)
close(4) = 4295170688 (0x100031a80)
unlink(/tmp/mutt-mech-cluster241-XSYQpzbj) = 4295170928 (0x100031b70)
Is debugging turned on; was mutt built WITH_DEBUG=yes?
yes, I just rebuilt with this set.
Uh, I rather meant that debugging might cause unoptimized code, but
given such repeated I/O to /tmp files I think that's more the culprit.
Any of the patches causing it?
Do you dare remount /tmp as asynchronous file system? I don't see
fsync(), so async might help a bit, and is reasonable for /tmp.
Can you verify the header cache databases, or move them away just for
the sake of the experiment?
sorry, I don't know what you mean here.
You enabled header caches during the build, and if they were excessively
large or broken, that might also cause slowdowns; but they need to be
run-time configured, which you did not, so forget this.
Does it help if you make clean before building world? This has cured
strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me.
Well, I might do this later, if no other
clue emerges.
Looking at the truss output, unless the 32nd bit set is required by the
IA64 calling conventions, that may be necessary regardless of the mutt
issue.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt 1.5 much slower than mutt 1.4
On Wed, Jul 25, 2012 at 12:51:57AM -0400, Jason Hellenthal wrote:
On Tue, Jul 24, 2012 at 06:18:43PM +0100, Anton Shterenlikht wrote:
mail/mutt is much slower on my amd64 and ia64
-current boxes after it was updated from 1.4
to 1.5. Each keystroke takes few seconds to
act. Below is my mutt 1.5 config:
=== The following configuration options are available for mutt-1.5.21:
MUTT_ASPELL=off: Enable aspell support
MUTT_COMPRESSED_FOLDERS=on: Enable compressed folders
MUTT_CYRUS_SASL2=off: Enable SASL2 authentication
MUTT_DEBUG=off: Enable debugging capabilities
MUTT_FLOCK=off: Enable flock() usage
MUTT_GPGME=off: Enable gpgme interface
MUTT_GREETING_PATCH=off: Enable greeting
MUTT_HTML=on: Enable HTML documentation
MUTT_ICONV=on: Enable iconv support
MUTT_IDN=off: Enable idn support
MUTT_IFDEF_PATCH=off: Enable ifdef feature
MUTT_IMAP_HEADER_CACHE=on: Enable imap header cache
MUTT_ISPELL=off: Enable ispell support
MUTT_LOCALES_FIX=off: Enable locales fix
MUTT_MAILBOX_MANPAGES=on: Install mbox.5/mmdf.5 manpages
MUTT_MAILDIR_HEADER_CACHE=off: Enable maildir header cache
MUTT_MAILDIR_MTIME_PATCH=off: Enable Maildir mtime patch
MUTT_MBOX_HOOK_PATCH=off: Enable enhanced mbox-hook
MUTT_NCURSES=on: Enable ncurses support
MUTT_NCURSES_PORT=off: Use ncurses from port
MUTT_NNTP=off: Enable news reader
MUTT_PARENT_CHILD_MATCH_PATCH=off: Enable parent/child match
MUTT_QUOTE_PATCH=on: Enable extended quoting
MUTT_REVERSE_REPLY_PATCH=off: Enable reverse_reply
MUTT_SGMLFORMAT=on: Enable sgml support
MUTT_SIDEBAR_PATCH=off: Enable sidebar
MUTT_SIGNATURE_MENU=off: Enable signature menu
MUTT_SLANG=off: Enable slang support
MUTT_SMIME_OUTLOOK_COMPAT=on: SMIME outlook compatible
MUTT_SMTP=off: Enable SMTP relay support
MUTT_TRASH_PATCH=off: Enable trash folder support
MUTT_XML=off: Use XML tools for docu
=== Use 'make config' to modify these settings
BUZI#
Anybody else is seeing this behaviour?
No I can't say that I am. I have been using it since it stepped its way
into mail/mutt-devel
Any advice?
Willing to post your muttrc ?
There are ~50 aliases, and then
# Setup
#
my_hdr From: me...@bristol.ac.uk
set envelope_from
# mailboxes
set record=+sent
set postponed=+postponed
set mbox=+received
unset save_empty
# behaviour, avoid unnecessary questions
unset confirmappend
set write_bcc = no
set delete = yes
set abort_nosubject = no
set move= yes
set print = ask-no
#set arrow_cursor=yes
set edit_headers=yes
#**
# wrapping
#
# wrap the lines at the word ends
set smart_wrap = yes
# put + at the beginning of wrapped lines
#set markers= yes
# leave 0 free space when wrapping
#set wrap = 0
#**
#set editor=vi
set ispell =aspell -c
set print_command=fold -s -w77 | lpr
#set print_command=fold -s -w77 | head -n 59 | lpr
#set print_command=fold -s -w75 | pr -F | lpr -Ptext
#set print_command=fold -s -w75 | pr -F | lpr
set signature=$HOME/work/signature
# forward icluding attachments
set mime_forward=ask-yes
set forward_decode=no
# urlview
macro index \cb |urlview\n
macro pager \cb |urlview\n
# date and time
set date_format=!%a, %b %d, %Y at %I:%M:%S%p %Z
set index_format=%3C %Z %{%b %d} %-15.15L (%4l) %s
# mailing lists
#
lists freebsd-questions questions \
freebsd-current freebsd-ia64 freebsd-doc \
fort...@gcc.gnu.org
subscribe freebsd-questions questions \
freebsd-current freebsd-ia64 freebsd-doc \
fort...@gcc.gnu.org
# colours
color indicator black white
color index brightwhite black ~h freebsd-current
color index brightyellowblack ~h freebsd-doc
color index brightyellowred ~h freebsd-gecko
color index brightwhite cyan~h freebsd-hackers
color index brightred black ~h freebsd-ia64
color index brightblue red ~h freebsd-mobile
color index brightmagenta black ~h freebsd-ports
color index brightgreen black ~h freebsd-questions
color index black green ~h freebsd-scsi
color index brightwhite red ~h freebsd-security
color index brightcyan black ~h freebsd-sparc
color index brightblue black ~h freebsd-standards
color index black magenta ~h freebsd-toolchain
color index black cyan~h freebsd-wireless
color index black yellow ~h freebsd-x11
color index brightwhite blue~h ports-ia64
color index brightwhite green ~h fort...@gcc.gnu.org
That's all
Thanks
--
Anton Shterenlikht
Room 2.6,
Re: mutt 1.5 much slower than mutt 1.4
On Tue, Jul 24, 2012 at 11:00:39PM +0200, Matthias Andree wrote: Am 24.07.2012 19:18, schrieb Anton Shterenlikht: mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: ... Anybody else is seeing this behaviour? Not here≥ on amd64 9-stable -- which may have little relevance for 10-current. Any advice? Any chance to figure out what mutt is doing, like with truss or similar? I'll need to read up on this. Is debugging turned on; was mutt built WITH_DEBUG=yes? yes, I just rebuilt with this set. Is the lag CPU-bound (near 100% CPU) and if yes, in system or in user space, or is the lag IO-bound (near 100% wait)? This is on ia64 r237134 For example, when I type mutt, then c and choose a folder, I get: -- Mutt: Directory [~/Mail], File mask: !^\.[^.] Sorting mailbox... which goes for over 50 sec. At the same time I see in top: PIDUIDTHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 92075 1001 1 220 24248K 21384K biowr 0 0:02 3.08% mutt The same on quitting q (about 40 sec): PIDUIDTHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 92075 1001 1 210 24248K 21384K biowr 1 0:03 2.20% mutt Can you verify the header cache databases, or move them away just for the sake of the experiment? sorry, I don't know what you mean here. Does it help if you make clean before building world? This has cured strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me. Well, I might do this later, if no other clue emerges. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt 1.5 much slower than mutt 1.4
On Tue, Jul 24, 2012 at 11:00:39PM +0200, Matthias Andree wrote: Am 24.07.2012 19:18, schrieb Anton Shterenlikht: mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: ... Anybody else is seeing this behaviour? Not here≥ on amd64 9-stable -- which may have little relevance for 10-current. Any advice? Any chance to figure out what mutt is doing, like with truss or similar? This is the trace when I try to open a folder ( 1MB): http://seis.bris.ac.uk/~mexas/mutt.truss.open.folder I also see that I might be using old libraries: # ldd /usr/local/bin/mutt /usr/local/bin/mutt: libncursesw.so.8 = /lib/libncursesw.so.8 (0x1202f6000) libgssapi.so.10 = /usr/lib/libgssapi.so.10 (0x1203aa000) libheimntlm.so.11 = /usr/lib/libheimntlm.so.11 (0x1203ca000) libkrb5.so.11 = /usr/lib/libkrb5.so.11 (0x1203e4000) libhx509.so.11 = /usr/lib/libhx509.so.11 (0x1204c6000) libcom_err.so.5 = /usr/lib/libcom_err.so.5 (0x12055) libcrypto.so.6 = /lib/libcrypto.so.6 (0x120562000) libasn1.so.11 = /usr/lib/libasn1.so.11 (0x120812000) libwind.so.11 = /usr/lib/libwind.so.11 (0x120918000) libheimbase.so.11 = /usr/lib/libheimbase.so.11 (0x120952000) libroken.so.11 = /usr/lib/libroken.so.11 (0x120968000) libcrypt.so.5 = /lib/libcrypt.so.5 (0x120996000) libssl.so.6 = /usr/lib/libssl.so.6 (0x1209d) libz.so.6 = /lib/libz.so.6 (0x120a72000) libintl.so.9 = /usr/local/lib/libintl.so.9 (0x120aaa000) libthr.so.3 = /lib/libthr.so.3 (0x120acc000) libc.so.7 = /lib/libc.so.7 (0x120b1a000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x120dca000) # make -C /usr/src check-old-libs Checking for old libraries /lib/libcrypto.so.6 /usr/lib/libssl.so.6 # I probably need to do make-delete-old, and then rebuild mail/mutt again. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
mutt 1.5 much slower than mutt 1.4
mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: === The following configuration options are available for mutt-1.5.21: MUTT_ASPELL=off: Enable aspell support MUTT_COMPRESSED_FOLDERS=on: Enable compressed folders MUTT_CYRUS_SASL2=off: Enable SASL2 authentication MUTT_DEBUG=off: Enable debugging capabilities MUTT_FLOCK=off: Enable flock() usage MUTT_GPGME=off: Enable gpgme interface MUTT_GREETING_PATCH=off: Enable greeting MUTT_HTML=on: Enable HTML documentation MUTT_ICONV=on: Enable iconv support MUTT_IDN=off: Enable idn support MUTT_IFDEF_PATCH=off: Enable ifdef feature MUTT_IMAP_HEADER_CACHE=on: Enable imap header cache MUTT_ISPELL=off: Enable ispell support MUTT_LOCALES_FIX=off: Enable locales fix MUTT_MAILBOX_MANPAGES=on: Install mbox.5/mmdf.5 manpages MUTT_MAILDIR_HEADER_CACHE=off: Enable maildir header cache MUTT_MAILDIR_MTIME_PATCH=off: Enable Maildir mtime patch MUTT_MBOX_HOOK_PATCH=off: Enable enhanced mbox-hook MUTT_NCURSES=on: Enable ncurses support MUTT_NCURSES_PORT=off: Use ncurses from port MUTT_NNTP=off: Enable news reader MUTT_PARENT_CHILD_MATCH_PATCH=off: Enable parent/child match MUTT_QUOTE_PATCH=on: Enable extended quoting MUTT_REVERSE_REPLY_PATCH=off: Enable reverse_reply MUTT_SGMLFORMAT=on: Enable sgml support MUTT_SIDEBAR_PATCH=off: Enable sidebar MUTT_SIGNATURE_MENU=off: Enable signature menu MUTT_SLANG=off: Enable slang support MUTT_SMIME_OUTLOOK_COMPAT=on: SMIME outlook compatible MUTT_SMTP=off: Enable SMTP relay support MUTT_TRASH_PATCH=off: Enable trash folder support MUTT_XML=off: Use XML tools for docu === Use 'make config' to modify these settings BUZI# Anybody else is seeing this behaviour? Any advice? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt 1.5 much slower than mutt 1.4
Am 24.07.2012 19:18, schrieb Anton Shterenlikht: mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: ... Anybody else is seeing this behaviour? Not here™ on amd64 9-stable -- which may have little relevance for 10-current. Any advice? Any chance to figure out what mutt is doing, like with truss or similar? Is debugging turned on; was mutt built WITH_DEBUG=yes? Is the lag CPU-bound (near 100% CPU) and if yes, in system or in user space, or is the lag IO-bound (near 100% wait)? Can you verify the header cache databases, or move them away just for the sake of the experiment? Does it help if you make clean before building world? This has cured strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt 1.5 much slower than mutt 1.4
strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me. s/strance/strange/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mutt 1.5 much slower than mutt 1.4
On Tue, Jul 24, 2012 at 06:18:43PM +0100, Anton Shterenlikht wrote: mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: === The following configuration options are available for mutt-1.5.21: MUTT_ASPELL=off: Enable aspell support MUTT_COMPRESSED_FOLDERS=on: Enable compressed folders MUTT_CYRUS_SASL2=off: Enable SASL2 authentication MUTT_DEBUG=off: Enable debugging capabilities MUTT_FLOCK=off: Enable flock() usage MUTT_GPGME=off: Enable gpgme interface MUTT_GREETING_PATCH=off: Enable greeting MUTT_HTML=on: Enable HTML documentation MUTT_ICONV=on: Enable iconv support MUTT_IDN=off: Enable idn support MUTT_IFDEF_PATCH=off: Enable ifdef feature MUTT_IMAP_HEADER_CACHE=on: Enable imap header cache MUTT_ISPELL=off: Enable ispell support MUTT_LOCALES_FIX=off: Enable locales fix MUTT_MAILBOX_MANPAGES=on: Install mbox.5/mmdf.5 manpages MUTT_MAILDIR_HEADER_CACHE=off: Enable maildir header cache MUTT_MAILDIR_MTIME_PATCH=off: Enable Maildir mtime patch MUTT_MBOX_HOOK_PATCH=off: Enable enhanced mbox-hook MUTT_NCURSES=on: Enable ncurses support MUTT_NCURSES_PORT=off: Use ncurses from port MUTT_NNTP=off: Enable news reader MUTT_PARENT_CHILD_MATCH_PATCH=off: Enable parent/child match MUTT_QUOTE_PATCH=on: Enable extended quoting MUTT_REVERSE_REPLY_PATCH=off: Enable reverse_reply MUTT_SGMLFORMAT=on: Enable sgml support MUTT_SIDEBAR_PATCH=off: Enable sidebar MUTT_SIGNATURE_MENU=off: Enable signature menu MUTT_SLANG=off: Enable slang support MUTT_SMIME_OUTLOOK_COMPAT=on: SMIME outlook compatible MUTT_SMTP=off: Enable SMTP relay support MUTT_TRASH_PATCH=off: Enable trash folder support MUTT_XML=off: Use XML tools for docu === Use 'make config' to modify these settings BUZI# Anybody else is seeing this behaviour? No I can't say that I am. I have been using it since it stepped its way into mail/mutt-devel Any advice? Willing to post your muttrc ? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- - (2^(N-1)) JJH48-ARIN pgpmKwLTEC2l9.pgp Description: PGP signature
