Closed NightRa closed 8 years ago
We should probably properly unescape everything in one location
Agree, and be platform agnostic from that point up
In this example, there wouldn't even be any need for platform specific
logic, as regular string unescaping would translate \n
and \\
correctly
2016-09-14 11:33 GMT+03:00 Tîng-Giān Luā notifications@github.com:
We should probably properly unescape everything in one location
Agree, and be platform agnostic from that point up
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/banacorn/agda-mode/pull/37#issuecomment-246943142, or mute the thread https://github.com/notifications/unsubscribe-auth/ACCrN-CvfVxRN9rp5PYWSKRlfQp_r9sEks5qp7FHgaJpZM4J8hKg .
For example, for the response
(agda2-info-action "*Scope Info*" "_+_ is in scope as\n * a defined name nat._+_ brought into scope by\n - the opening of nat at\n - its definition at C:\\Users\\Ilan\\Programming\\IAL\\nat.agda:36,1-4" nil)
, the\\nat
at the end would be treated as\~newline~at
.We should probably properly unescape everything in one location