/top/
/new/
/best/
/ask/
/show/
/job/
^
slacker news
login
about
←back to thread
CRLF is obsolete and should be abolished
(fossil-scm.org)
422 points
km
| 4 comments |
13 Oct 24 19:16 UTC
|
HN request time: 0s
|
source
Show context
Ekaros
◴[
13 Oct 24 20:19 UTC
]
No.
41831220
[source]
▶
>>41830717 (OP)
#
I think I can offer most reasonable compromise here. Decide upon on new UTF-8 code point. Have the use mandated and ignore and ban all end-points that do not use this code-point instead of CRLF or just LF alone.
replies(6):
>>41831264
#
>>41831281
#
>>41831818
#
>>41831843
#
>>41832264
#
>>41832462
#
1.
kps
◴[
13 Oct 24 21:33 UTC
]
No.
41831818
[source]
▶
>>41831220
#
You mean U+2028 LINE SEPARATOR?
replies(2):
>>41831844
#
>>41831854
#
ID:
GO
2.
Ekaros
◴[
13 Oct 24 21:36 UTC
]
No.
41831844
[source]
▶
>>41831818 (TP)
#
Perfect. So now we just need to start filing bug reports to any tool that does not support it instead of CRLF or LF alone.
replies(1):
>>41834208
#
3.
bear8642
◴[
13 Oct 24 21:37 UTC
]
No.
41831854
[source]
▶
>>41831818 (TP)
#
Oh, yet another option - first thought was U+0085 NEXT LINE as above
4.
◴[
14 Oct 24 04:32 UTC
]
No.
41834208
[source]
▶
>>41831844
#
↑