2 mutt questions

[Bill Jonas]

--x71cOvsLpdxMSN5+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 31, 2002 at 04:17:17PM -0500, Mike Starke wrote:
> Hmm, I just figured out what that problem was (after all this time).
> I had a line in my .muttrc like this: "set indent_string=3D"\ "
> It doesn't like the backslash. Any idea how to get around that?

Well, I strongly recommend against changing it much from the default.
But to answer your question, you'd generally want to double the
backslash.  (Since it's used as an escape character, you need to use
'\\' to get a literal '\'.)  I tried this, though, and it doesn't work.
Quadrupling it does, however.  My guess, without having looked at the
Mutt source, is that the string gets interpreted twice, somehow.

I just noticed that this only applied if you use double quotes; if you
use single quotes, a single pair of backslashes should suffice.  I think
this is probably due to the double-quoted string getting interpreted as
it's read in from the file and then again as it's on its way out to the
reply, whereas the single quotes mean it just gets interpreted once.
That's only a guess, though.

So use either:

set indent_string=3D"\\\\ "

or:

set indent_string=3D'\\ '

--=20
Bill Jonas    *    bill@billjonas.com    *    http://www.billjonas.com/
"They that can give up  essential  liberty to obtain a little temporary
safety deserve neither liberty nor safety."        -- Benjamin Franklin

--x71cOvsLpdxMSN5+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9wa5GdmHcUxFvDL0RAgdVAJ46pkJJ1XAI6OqWU/rBvf4p7h8FKQCgnatp
A2Ok5t+ryLrr4SGNAhAqvdQ=
=8Sdd
-----END PGP SIGNATURE-----

--x71cOvsLpdxMSN5+--