David Champion wrote: > ant wrote: no need to Cc me, i'm subscribed via gmane .
... >> without seeing the exact file i'm not going to be >> able to interpret your strings above. you may have >> left out something important and i can't make sense >> of things like: >> >> > set imap_pass =3D 'word1\$word2=E2=80=98 -> word1\\ #Really! >> >> i.e. i see no closing quote character and that may be >> affecting other stuff later... > > Rainer's mail contains quoted-printable-encoded unicode "smart quotes", > which are usually not very smart. Ant's mutt, because it doesn't > understand unicode, is leaving them encoded as =E2=80=98 and such. yep, that is why i suspect i'm seeing a cut and paste introduced change or some other environmental effect. > Rainer, this doesn't happen for me. This test: > > cat >>muttrc.test <<EOF > set imap_pass = 'abc$xyz' > push ":set ?imap_pass<enter>" > EOF > mutt -D -F muttrc.test | egrep imap_pass= > > ... does what you'd expect: prints "imap_pass="abc$xyz"' on my screen. > > I haven't tested against an IMAP server, but this shows what I want to see: > >:set ?imap_pass > > Does your muttrc contain actual unicode smart quotes or are those just > an artifact of pasting into Apple Mail? They could cause unforeseen > results in mutt's parser. *nods* ant
