https://community.splunk.com/t5/Splunk-Search/Prevent-query-autoformat-from-deleting-empty-lines/m-p/472817#M133080 <PRE><CODE>| rename COMMENT as "my comment" </CODE></PRE> <P>but it's not any better.</P> Thu, 05 Sep 2019 17:13:56 GMT DalJeanis 2019-09-05T17:13:56Z https://community.splunk.com/t5/Splunk-Search/Prevent-query-autoformat-from-deleting-empty-lines/m-p/472816#M133079 <P>It can enhance query readability to separate large queries into their logical components using empty lines:</P> <PRE><CODE>index = events `comment("find and filter events")` | ... | ... | ... `comment("derive statistics of type A")` | ... | ... `comment("derive statistics of type B")` | ... | ... `comment("sort and format the results")` | ... | ... </CODE></PRE> <P>But the Splunk search's auto-format removes empty lines. I'd like to prevent that. Is there a way to retain all auto-format functionality EXCEPT for deleting empty lines?</P> <P>If that's impossible, I'd like to find the minimum "filler-text" which I could use to separate logical blocks of a search.<BR /> Right now my only candidates are empty comments and noop. </P> <PRE><CODE>`comment("")` | noop </CODE></PRE> <P>Are there any better alternatives? I'm also suspicious that "noop" might not be benign.<BR /> I'm using Splunk Enterprise 7.3.0</P> Thu, 05 Sep 2019 15:05:33 GMT https://community.splunk.com/t5/Splunk-Search/Prevent-query-autoformat-from-deleting-empty-lines/m-p/472816#M133079 d_o_c 2019-09-05T15:05:33Z https://community.splunk.com/t5/Splunk-Search/Prevent-query-autoformat-from-deleting-empty-lines/m-p/472817#M133080 <PRE><CODE>| rename COMMENT as "my comment" </CODE></PRE> <P>but it's not any better.</P> Thu, 05 Sep 2019 17:13:56 GMT https://community.splunk.com/t5/Splunk-Search/Prevent-query-autoformat-from-deleting-empty-lines/m-p/472817#M133080 DalJeanis 2019-09-05T17:13:56Z