Hi all, I'm having the following problem (or rather, inconvenience). When typing my ConTeX, I tend to properly indent all of my text, following the section headings. This makes my source a bit more readable. However, when I apply the same tactic to typing environments, all of the indentation is preserved in the output. This is of course to be expected, but it requires me to break the indentation for every typing environment, making very ugly source. Anyone else who also finds this problematic? What I'd like to see, is an option for a typing environment (say, stripindent) that makes the pretty printing code remove a fixed amount of indentation from every line. I've implemented this for some of my custom prettyprinters, but that's a lot of duplicate code, and it won't help others. Ideally, this would look at the indent of the \starttyping command and strip that much, but I don't think this is possible in TeX (or is it?) Slightly less ideal would be to look at all the lines, decide what the smallest indent is, and strip that. This would of course require buffering all the lines and start processing only when the final one is in, which is not very efficient given the current pretty printer implementation. What will probably work well enough is to look at the first line, and strip that much whitespace from all lines. This could be implemented entirely in lua. Would there be any interest for something like this? I could whip up a patch if there is. Where would be the logical place to do this? I don't see any need to let individiual pretty printers keep control over this, so I guess it is best handled before the pretty printers get at the line (So in buffers.typeline, probably. I guess inline \type commands don't need this, so this should work out). This also needs some initialization in buffers.type and buffers.typefile so we can detect what the first line is. Ideally, there would also be some sort of manual override, like: \starttyping[stripindent=4] but, I don't think any options are supported there currently (and adding them is very much over my head, since that would involve serious TeX coding...). To reach a conclusion, if I managed to implement this properly, would there be any interest for using this and including this in ConTeXt? Gr. Matthijs