(This question may fall into the "primarily opinion based" category, in which case it should be closed. I shall try to make it sufficiently focused but I expect no special treatment. I anticipate that it may need some work if it is to remain.)
Following the recommendation of presentation or article which I now only vaguely remember I have been experimenting with a particular code format:
fn[args_] := ( expr // operation1 // operation2 // operation3 )
I have found this format to be reasonably general and have above average readability. I note that my use of it (which is by no means unique) seems to be well accepted so I think others must find it readable too.
A couple of things keep me from adopting this format as my go-to style: the first is the requirement for additional
Function constructs over more heavily bracketed code. The second is the way that this code is automatically formatted in Notebook Input Cells which is what my question is about.
(Pardon the long introduction but I feel that context is necessary.)
// postfix operations are written one on each line the standard code indenter does this:
I find this indenting weird and inconvenient. I suppose it exists to indicate that
operation1 is "inside"
operation5, etc., but that's not really how I think about these operations; rather I think of them as a series of sequential steps performed in order from one to five.
It also ends up crowding code into the right margin when there would otherwise be plenty of room.
All that out of the way my actual question is this: do other people regularly benefit from the indenting shown above, and what coding style(s) is it useful for?
If this indenting is not of use in other styles or from different perspectives I would perhaps campaign to have the indenting changed in future versions to the vertically aligned form shown in the first code block in this question.