Benito Epominati 8 Posted March 27 Share Posted March 27 The recently introduced autoformatting of characters combinations like "->" to an arrow symbol seems to interfere with the content of codeblocks to the degree that the displayed code might no longer be valid in the strict sense. The content of codeblocks should remain unaltered. For instance, the following Julia code... filter(i -> iszero(i[2]) != true, dataset) becomes... which is unfortunate. Another example would be... select(df, 1 => "Date", :Country_code => "C-Code") is changed to Please fix. Thanks. Ben System info: Win 10 10.81.4-win-ddl-public (20240320152323) Editor: V 177.9.4 Service: V 1.97.1 Link to comment
Level 5* s2sailor 2,428 Posted March 28 Level 5* Share Posted March 28 58 minutes ago, Benito Epominati said: The recently introduced autoformatting of characters combinations like "->" to an arrow symbol seems to interfere with the content of codeblocks to the degree that the displayed code might no longer be valid in the strict sense. The content of codeblocks should remain unaltered Apparently work is being done on the code block so hopefully this will be removed. It has been reported that though this seems like it could be a problem, when copied back into an IDE it does render correctly and is not an issue. 2 Link to comment
Mike P 2,972 Posted March 28 Share Posted March 28 One "interesting" feature is that the code block and inline text converts <= and >= into the correct mathematical symbol but leaves it untouched in the main body of the note. This is exactly the opposite of the behaviour I would expect. My main use of EN code blocks is to store important snippets of code, and although it looks weird, it does always copy back to my IDE correctly. 2 Link to comment
Benito Epominati 8 Posted March 28 Author Share Posted March 28 I can confirm the above: When copied to and fro the snippets are always correct. Also, Evernote on iPhone displays no symbols in the codeblock (but I have not tested this extensively). So, this very likely a front end issue specific to the desktop client. Interestingly enough, in the codeblock more symbols get converted than in the text body: 3 Link to comment
Benito Epominati 8 Posted April 1 Author Share Posted April 1 Also, the choice of the font for code blocks is unfortunate in general, since it uses a non-coding style ampersand, while better options are already available from the font menu as shown below. 1 Link to comment
Benito Epominati 8 Posted April 18 Author Share Posted April 18 Not fixed in Evernote 10.84.3 Link to comment
Evernote Expert agsteele 3,059 Posted April 18 Evernote Expert Share Posted April 18 I believe that code blocks are getting some attention. Don't expect a piecemeal update. Link to comment
AlbertR 705 Posted April 19 Share Posted April 19 18 hours ago, agsteele said: I believe that code blocks are getting some attention. Your believe never failed 😉👍 1 Link to comment
Level 5 PinkElephant 8,785 Posted April 19 Level 5 Share Posted April 19 Sometimes believing is knowing … 😇 1 Link to comment
Benito Epominati 8 Posted April 19 Author Share Posted April 19 This naturally is not a top tier issue to clean up. However, I trust, that they do it at some point. They building up a good track record for cleaning things up and implementing new features at the same time. Makes a good argument for a premium subscription. 2 Link to comment
Solution Benito Epominati 8 Posted June 5 Author Solution Share Posted June 5 (edited) Fixed in Evernote 10.91.1* with the update that formats and highlights code blocks. Well done, Evernote! Now please add Julia to the list of supported languages. I mean, you already added Haskell... 🙂 * 10.91.1-win-ddl-public (20240604023825) Editor: V 178.10.0 Service: V 1.109.4 Update: Although the automatic reformatting of -> etc. has been removed, the font used, still causes minor issues. Namely, the ampersand symbol for e.g. && boolen operators etc. is set in a font that is typically only used for comments. See example below. Edited June 6 by Benito Epominati Updated Information about formatting Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now