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
Is there a way to disable embedded elisp replacement in template files?
It tries to replace below minified JavaScript code (from highlight.js):
function(e){return{sL:"xml",c:[{cN:"meta",b:"^__(END|DATA)__$"},{b:"^\\s*%{1,2}={0,2}",e:"$",sL:"perl"},{b:"<%{1,2}={0,2}",e:"={0,1}%>",sL:"perl",eB:!0,eE:!0}]}});
__(END|DATA)__ doesn't need replacement. It is also kind of dangerous to try to replace blindly.
__(END|DATA)__
The replacement will cause error:
Error: (void-function END|DATA) replace-regexp-in-string: Wrong type argument: stringp, nil
The text was updated successfully, but these errors were encountered:
Add embedded elisp evaluation per-template option
5bb8ee4
In same js file "highlight.js", it contains a lot keywords like "__NAME__", "__DATE__" etc, which are not supposed to be replaced.
__NAME__
__DATE__
It will be great to be able to turn off replacement completely for certain files.
Any idea on possible solutions?
Sorry, something went wrong.
Tried to add template configuration(:skip-file) to skip certain files from string replacement.
Detail can be found in tendant@1c3e640
It solve this problem by skipping problematic files. This issue is also related to another pull request: #39.
Please advice what's the best way to incorporate it in master branch.
No branches or pull requests
Is there a way to disable embedded elisp replacement in template files?
It tries to replace below minified JavaScript code (from highlight.js):
function(e){return{sL:"xml",c:[{cN:"meta",b:"^__(END|DATA)__$"},{b:"^\\s*%{1,2}={0,2}",e:"$",sL:"perl"},{b:"<%{1,2}={0,2}",e:"={0,1}%>",sL:"perl",eB:!0,eE:!0}]}});
__(END|DATA)__
doesn't need replacement. It is also kind of dangerous to try to replace blindly.The replacement will cause error:
Error: (void-function END|DATA) replace-regexp-in-string: Wrong type argument: stringp, nil
The text was updated successfully, but these errors were encountered: