Bug#534474: Recent change broke my mailboxes configuration
Hi Antonio, On Mon, Aug 17, 2009 at 22:15:20 +0100, Antonio Radici wrote: I had a conversation [0] with the mutt developers and it seems that this configuration is unsupported and the fact that it was working before was unintended. So, do you want me to pursue this thing further? Thank you for pursuing this so far, but I'm OK with stopping at this point. Upstream has clarified that this behaviour is intended, and I can adapt my configuration to the current behaviour. Probably if they think that this is the way it should work we should ask them to udpate the documentation, can you please confirm whether the documentation is up-to-date with the expected behavior? In current mercurial, doc/manual.txt states It is also possible to substitute the output of a Unix command in an initialization file. This is accomplished by enclosing the command in backticks (``). In Example 3.5, Using external command's output in configuration files, the output of the Unix command uname -a will be substituted before the line is parsed. Since initialization files are line oriented, only the first line of output from the Unix command will be substituted. and I consider that sufficient documentation of the current behaviour. Kind regards, Ray -- USDoJ/Judge Jackson: Microsoft has performed an illegal operation and will be shut down. James Turinsky in alt.sysadmin.recovery -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534474: Recent change broke my mailboxes configuration
tag 534474 +wontfix thanks Hi, I had a conversation [0] with the mutt developers and it seems that this configuration is unsupported and the fact that it was working before was unintended. It seems that mutt-dev didn't intend backticks for expansion on multiple lines, you can have a look at Rocco's answer [1], he says the following: The solution for that bug is either to not use backticks and have the script generate a real file, or make source script like 'foo.sh|'. So, do you want me to pursue this thing further? Probably if they think that this is the way it should work we should ask them to udpate the documentation, can you please confirm whether the documentation is up-to-date with the expected behavior? Cheers Antonio [0] http://marc.info/?t=12504235071r=1w=2 [1] http://marc.info/?l=mutt-devm=125051307718265w=2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534474: Recent change broke my mailboxes configuration
tag 534474 +fixed-upstream thanks On Wed, Aug 05, 2009 at 12:28:17PM +0200, J.H.M. Dassen (Ray) wrote: The issue is reproducible for me with upstream mercurial HEAD using the reproducer I provided previously, but not with revision fa4990c5b5c6 (which corresponds to mutt-1.5.18). Bisection leads to the following result: The first bad revision is: changeset: 5827:776ef9dbe4d2 branch: HEAD user:Rocco Rutte pd...@gmx.net date:Fri May 29 21:24:29 2009 +0200 summary: Add flags to mutt_read_line() for EOL-stripping and continuation support -- Hi, sorry for getting back to you so late but I was on holidays for three weeks in July and then I had to catch up with work-related stuff, now I'm catching up with the mutt bts queue. I've tested ths and I was able to reproduce it, thanks for your clear explanation; I've tested this with the latest tip from upstream and it seems fixed, I'm now tracking back the commit to see what fixed this so we can include it to our patched version of mutt. I will let you know ASAP Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534474: Recent change broke my mailboxes configuration
# Reproducer was supplied back in June tags 534474 - moreinfo - unreproducible # See below tags 534474 + upstream thanks The issue is reproducible for me with upstream mercurial HEAD using the reproducer I provided previously, but not with revision fa4990c5b5c6 (which corresponds to mutt-1.5.18). Bisection leads to the following result: The first bad revision is: changeset: 5827:776ef9dbe4d2 branch: HEAD user:Rocco Rutte pd...@gmx.net date:Fri May 29 21:24:29 2009 +0200 summary: Add flags to mutt_read_line() for EOL-stripping and continuation support -- UNIX is not so much a product as it is a painstakingly compiled oral history of the hacker culture. It is our Gilgamesh epic. Doc Searls in The Morlock Market, Linux Journal, January 2001. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534474: Recent change broke my mailboxes configuration
Hi Antonio, On Wed, Jun 24, 2009 at 21:03:08 +0200, Antonio Radici wrote: If you can reproduce it against a 1.5.18-6 and an 1.5.20-1 (with different behaviors) can you please attach two .muttdebug0 files (one per version) (generated with mutt -d5) that contains some hits of '$' when you are in the pager? So we will see if both mailboxes are actually checked. Please find attached a small reproducer for the problem: * md/ : contains two Maildir folders =foo and =bar, each containing one, new mail message. * muttrc : muttrc with which to reproduce the problem * mboxes : script called by the mailboxes command in muttrc * 1.5.18-6+b1/ : steps followed with this version and resulting muttdebug files. This version behaves as expected: mutt recognises that both folders contain new mail. * 1.5.20-2/ : steps followed with this version and resulting muttdebug files. This version does not behave as expected: mutt only recognises new mail in the folder =foo . Kind regards, Ray -- Windows 2001: Oh my god, it is full of bugs mutt-reproducer.tar.bz2 Description: Binary data
Bug#534474: Recent change broke my mailboxes configuration
Package: mutt Version: 1.5.20-1 Severity: important What am I trying to do: Have mutt check for new mail in a list of mailboxes that is dynamically generated. How am I trying to do it: Using the mailboxes command with backtick substitution in my ~/.muttrc. What behaviour did I expect: When I have mailboxes `echo '=foo \'; echo '=bar'` in my ~/.muttrc, I expect mutt to check both the =foo and =bar folders for new mail, as it has been doing up to and including 1.5.18-6+b1. What behaviour did I get: With 1.5.20-1, only =foo is checked for new mail; =bar is not checked. -- Package-specific info: Mutt 1.5.20 (2009-06-14) Copyright (C) 1996-2009 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: Linux 2.6.30 (x86_64) ncurses: ncurses 5.7.20090523 (compiled with 5.7) libidn: 1.15 (compiled with 1.15) hcache backend: GDBM version 1.8.3. 10/15/2002 (built Aug 27 2008 08:41:43) Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh MIXMASTER=mixmaster To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. patch-1.5.13.cd.ifdef.2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing-proposed-updates'), (500, 'oldstable'), (500, 'stable'), (400, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mutt depends on: ii libc62.9-18 GNU C Library: Shared libraries ii libcomerr2 1.41.6-1common error description library ii libgdbm3 1.8.3-4 GNU dbm database routines (runtime ii libgnutls26 2.6.6-1 the GNU TLS library - runtime libr ii libgpg-error01.6-1 library for common error values an ii libgpgme11 1.1.8-2 GPGME - GnuPG Made Easy ii libgssapi-krb5-2 1.7dfsg~beta3-1 MIT Kerberos runtime libraries - k ii libidn11 1.15-1 GNU Libidn library, implementation ii libk5crypto3 1.7dfsg~beta3-1 MIT Kerberos runtime libraries - C ii libkrb5-31.7dfsg~beta3-1 MIT Kerberos runtime libraries ii libncursesw5 5.7+20090523-1 shared libraries for terminal hand ii libsasl2-2 2.1.23.dfsg1-1 Cyrus SASL - authentication abstra Versions of packages mutt recommends: ii exim4 4.69-11metapackage to ease Exim MTA (v4) ii exim4-daemon-heavy [mail- 4.69-11Exim MTA (v4) daemon with extended ii libsasl2-modules 2.1.23.dfsg1-1 Cyrus SASL - pluggable authenticat ii locales 2.9-18 GNU C Library: National Language ( ii mime-support 3.46-1 MIME files 'mime.types' 'mailcap Versions of packages mutt suggests: ii aspell 0.60.6-1 GNU Aspell spell-checker ii ca-certificates 20081127 Common CA certificates ii gnupg 1.4.9-4 GNU privacy guard - a free PGP rep ii ispell 3.1.20.0-4.5 International Ispell (an interacti pn mixmaster none (no description available) ii openssl 0.9.8k-3 Secure Socket Layer (SSL) binary a pn urlview none (no description available) Versions of packages mutt is related to: ii mutt 1.5.20-1 text-based mailreader supporting M pn mutt-dbg none (no description available) pn mutt-patched none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534474: Recent change broke my mailboxes configuration
tag 534474 +moreinfo unreproducible thanks On Wed, Jun 24, 2009 at 07:10:59PM +0200, J.H.M. Dassen (Ray) wrote: How am I trying to do it: Using the mailboxes command with backtick substitution in my ~/.muttrc. What behaviour did I expect: When I have mailboxes `echo '=foo \'; echo '=bar'` in my ~/.muttrc, I expect mutt to check both the =foo and =bar folders for new mail, as it has been doing up to and including 1.5.18-6+b1. What behaviour did I get: With 1.5.20-1, only =foo is checked for new mail; =bar is not checked. Hi, thanks for your bug report; first of all: are you using maildirs or mboxes, from what you've written (folder) it seems that you're using maildirs but I want to confirm this. Then, are you sure that that mailboxes setting works on 1.5.18-6? I've just tested it against my IMAP folders and when I hit '$' it is clear from .muttdebug0 that only the first folder is checked, if I use mailboxes `echo '=foo =bar'` both folders are checked. If you can reproduce it against a 1.5.18-6 and an 1.5.20-1 (with different behaviors) can you please attach two .muttdebug0 files (one per version) (generated with mutt -d5) that contains some hits of '$' when you are in the pager? So we will see if both mailboxes are actually checked. If you will be able to reproduce it I will probably ask you for more info. Please also attach the minimal .muttrc required to reproduce this bug. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534474: Recent change broke my mailboxes configuration
Hi Antonio,
On Wed, Jun 24, 2009 at 21:03:08 +0200, Antonio Radici wrote:
thanks for your bug report; first of all: are you using maildirs or
mboxes
I'm using maildirs.
Then, are you sure that that mailboxes setting works on 1.5.18-6?
Yes, I am. When I have 1.5.18-6+b1 installed, the setting
mailboxes `cd $HOME/Maildir find -mindepth 2 -maxdepth 2 -name 'new'
-type d | grep -v '^\./postponed/new' | sed -e 's,/new$, \\,' -e 's,^\./,=,'
echo '=dummy'`
works as desired ('c' cycles through all folders with new mail), whereas
with 1.5.20-1, no new mail is reported ('c' does not offer any folders with
new mail; the first folder in the generated list does not have new mail in
it).
If you can reproduce it against a 1.5.18-6 and an 1.5.20-1 (with different
behaviors) can you please attach two .muttdebug0 files (one per version)
(generated with mutt -d5) that contains some hits of '$' when you are
in the pager? So we will see if both mailboxes are actually checked.
If you will be able to reproduce it I will probably ask you for more info.
Please also attach the minimal .muttrc required to reproduce this bug.
I'll get back to you on this; it's time to get some sleep now.
Greetings,
Ray
--
I think the most important thing about Linux is that it gives people the
ability to do what they want.
Alan Cox in http://www2.linuxjournal.com/articles/culture/012.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
