On 1/18/17 at 4:11 PM, [email protected] (Bill Kochman) wrote:
Thanks Patrick. I have used \r quite a bit before, but never
\n. Isn’t the latter more Unix-oriented? It’s been a long
time since I have looked into this kind of stuff.
In brief, \r ordinarily stands for a carriage return (CR:
decimal 13/hex 0D) and \n for a line feed (LF: decimal 10/hex
0A) but to maintain maximum compatibility for stored patterns
BBEdit treats each of these special characters as a 'hard' line break.
(As an aside for anyone who does need to match literal carriage
returns or line feeds, you can do so by using the 'hex escape'
form: \x{NN} where NN is the hex value of the desired character.)
At any rate, so I appear to have three options: option-return, \r and \n.
Actually, yes, I do want the hard returns so it physically
looks like what I have in other documents. :)
Fair 'nuff then. :-)
Regards,
Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com/>
--
This is the BBEdit Talk public discussion group. If you have a
feature request or would like to report a problem, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
---
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/bbedit.
