Issue #16119 has been updated by Josh Cooper. Status changed from Accepted to In Topic Branch Pending Review Target version changed from 2.7.20 to 2.7.x Affected Puppet version set to 2.7.19 Branch set to https://github.com/puppetlabs/puppet/pull/1090
For the record, it's easy to edit files on Windows or Unix that contain both CR and/or NL... just use emacs. But yeah, it's not very user-friendly. Updated in topic branch. ---------------------------------------- Bug #16119: We reject the \r escape sequence as invalid, which makes it hard to write Windows strings in a Unix editor https://projects.puppetlabs.com/issues/16119#change-70196 Author: Nick Fagerlund Status: In Topic Branch Pending Review Priority: Normal Assignee: Josh Cooper Category: parser Target version: 2.7.x Affected Puppet version: 2.7.19 Keywords: windows crnl newline EOL Branch: https://github.com/puppetlabs/puppet/pull/1090 $mystring = "first line\r\nsecondline" This blows up, with an "Unrecognised escape sequence" error. Looking at puppet/parser/lexer.rb somewhere in the neighborhood of line 500: def slurpstring(terminators,escapes=%w{ \\ $ ' " n t s }+["\n"],ignore_invalid_escapes=false) It'd be cool to be able to insert a literal CR into a string, since we write strings in binary mode on Windows and it's really really hard to make text editors intermix LF and CRLF linebreaks in the same file. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
