New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linefeed without a previous carrage return #499

Open
Eckspert opened this Issue Jul 23, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@Eckspert

Eckspert commented Jul 23, 2018

This issue is not relevant in Penn as its parser strips out all linefeed data. On Rhost the issue is presented when you use regexp to split/remove a carriage return, but the linefeed is still present. This is an issue of Rhost separating CRLF and potato not being able to handle it.

A good example to reproduce this is...
@emit Test[mid(%r,0,1)]Test2 - LF
@emit Test[mid(%r,1,1)]Test2 - CR

Using the code you provided me earlier...
/eval [winover] dump "sel.first -1 line linestart" "sel.last +1 line lineend"

Return (630): tagon margins 1002.0 text {Ashen-Shugar types -=> @emit Test[mid(%r,0,1)]Test2} 1002.0 tagoff margins 1002.51 tagon timestamp 1002.51 text 1532313947 1002.51 tagoff timestamp 1002.61 text { } 1002.61 tagon sel 1003.0 mark insert 1003.0 tagon margins 1003.0 text {Test Test2} 1003.0 tagoff margins 1003.10 tagon timestamp 1003.10 text 1532313948 1003.10 tagoff timestamp 1003.20 tagoff sel 1003.20 mark tk::anchor10 1003.20 text { } 1003.20 tagon margins 1004.0 text Ashen 1004.0 mark current 1004.5 text {-Shugar types -=> @emit Test[mid(%r,1,1)]Test2} 1004.5 tagoff margins 1004.51 tagon timestamp 1004.51 text 1532313951 1004.51

@talvo

This comment has been minimized.

Collaborator

talvo commented Jul 23, 2018

I suggest you tell Ash to fix Rhost so that can't happen, but I'll look into it in the meantime.

@Eckspert

This comment has been minimized.

Eckspert commented Jul 23, 2018

A work around for this is to wrap the output in Rhost with strip(output,mid(%r,0,1))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment