On 9/12/12 1:17 PM, "[email protected]" <[email protected]> wrote:

>On Wed, 12 Sep 2012, Rainer Gerhards wrote:
>
>>> It looks like I really overlooked that... Besides, escapes other than
>>> \' are currently not supported. The good thing probably is that this
>>> means I can introduce them without breaking anything, simply because
>>> that was already broken all the time ;)
>>
>> OK, looks like I will have this ready tomorrow. I will also add an
>>escape
>> \xhh where h is a hex digit. Essentially, this can be used to specify
>>any other character and as such can be used as a general work-around.
>>Besides that, any other escapes that I should consider to include? The
>>usual set \n\t\r... doesn't make too much sense in this context, does it?
>
>\t may, but the end of line ones don't
>
>we really need an option to skip escaping tabs while still escaping all
>the other control characters. too many logs include tabs and it gets
>'interesting' to try and read them with #011 replacing them :)

I definitely agree with the notion of having a way to escape all control
characters except for tabs; I already have some logic in place in my
applications to handle literal tabs, but other control characters make
sense to escape.  Right now I have to turn off the feature to escape
control characters just to preserve the tab behavior so as not to break
parsing.  +1 for this suggestion from me!

Thank you,

Abby

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to