> in case not obvious, i am suggesting a nil value for org adapt indentation. > thus no physical indentation of all lines including planning lines. > i'd even suggest no physical indentation as default for example and > source blocks, but that is a can of worms.
I know that this is a can of worms, but I agree. Given that the effects of org-adapt-indentation can be mimicked in other ways without having the literal spaces present in the file it may not be as big a deal as we think. The other reason I think this is a good idea is because I have been working on a formal grammar for the org syntax, and everything would be SO much simpler about the implementation after the first pass parse if the canonical representation of an Org file did not allow significant whitespace (with an exception for plain lists). Just avoiding having to deal with any number of nasty edge cases for correctly aligning org babel blocks would be worth it. Not to mention the fact that it means that you have to do a triple pass over each incoming line in order to be sure that what you are passing to an org babel block has had the leading whitespace removed (once for a normal parse, second time to adjust whitespace and a third time to actually parse the babel block). No significant leading whitespace would remove the need for an entire pass in the parser. I will have more on the subject when I finally get around to sharing the grammar, but suffice to say, that having org-adapt-indentation set to true and putting the leading spaces in the file (instead of doing whatever it is that doom does by default) induces significant complexity into the implementation. I would love to see it gone, as I'm sure anyone wanting to parse org files in future will too. Best! Tom
