We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
test/example_files/ecma-48.txt says: The start of the file MUST begin with an ECMA-48 escape sequence.
Could not find the requirement in standard (http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-048.pdf)
Moreover, if the file does not begin with an escape sequence, there is no way to view it coloured in RetroTxt.
Steps to reproduce: erase the first �[0; from test/example_files/ecma-48.txt and see the ugly unformatted text.
Correct behaviour: There should be some way to force ECMA-48 coloring of the file that does not begin with an escape sequence.
The text was updated successfully, but these errors were encountered:
Hi the ecma-48 text stating that requirement is incorrect. There is actually a bug with the ECMA-48 detection.
Line 283 in functions.js has whitespace that shouldn't be there.
functions.js
c = s.indexOf(`${String.fromCharCode(27)} ${String.fromCharCode(91)} `)
needs to be
c = s.indexOf(`${String.fromCharCode(27)}${String.fromCharCode(91)}`)
Sorry, something went wrong.
Version 2.1.7
afee633
Fixed issue #38, ECMA-48 detection issue.
@regentov Thanks for letting me know about this bug! It has been fixed and submitted to the Chrome store.
bengarrett
No branches or pull requests
test/example_files/ecma-48.txt says:
The start of the file MUST begin with an ECMA-48 escape sequence.
Could not find the requirement in standard (http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-048.pdf)
Moreover, if the file does not begin with an escape sequence, there is no way to view it coloured in RetroTxt.
Steps to reproduce: erase the first �[0; from test/example_files/ecma-48.txt and see the ugly unformatted text.
Correct behaviour: There should be some way to force ECMA-48 coloring of the file that does not begin with an escape sequence.
The text was updated successfully, but these errors were encountered: