Hi, * Kyle Wheeler [07-03-21 08:11:31 -0600] wrote:
On Wednesday, March 21 at 01:51 PM, quoth Paul Walker:Well, some mutt docs say that when adding new features, the old should be default. Adding spaces back by force is a one liner. I can do that if it's
I'm confused here. The $indent_string variable should control what the quoting string is. Why is the space having to be added back in the mutt code, rather than the variable?
I think, and I may be wrong, but I seem to recall that the problem is that f=f messages have to have a specific quoting string that is specified in the RFC, thus, to make sure that you're generating legal messages, it has to ignore $indent_string.
Yes. Per quoting-level the quoting char is exactly '>'. When re-adding spaces, some output line is generated as:
1) put prefix ('>' when making a reply, empty otherwise)
2) put '>' quote-level many times
3) put space
4) put content
...where point 3 is "new".
bye, Rocco
--
:wq!