New CodeMirror 6 TiddlyWiki5 plugin

[Yaisog]

It puts a little squiggly line below trailing spaces to make them visible.

[BurningTreeC]

Hi @stobot

@stobot

Snippets: I didn’t see any instructions, but in Advanced search found an example one to learn from

• I’m assuming :default is limited to constant text, just confirming
• The trigger field value seems to have limitations on naming, I tried using a ? prefix but that didn’t work, will probably use _ for myself in the future - cool feature!

@stobot

Filter operator completions: Stuff like the all[ works fantastic!

• I can’t get the suffix ones to work, like search:
  • 
  • Might just be the emoji thing getting in the way

yes it was the emoji-picker, I’ve solved that

@stobot

Snippets: I didn’t see any instructions, but in Advanced search found an example one to learn from

• I’m assuming :default is limited to constant text, just confirming
• The trigger field value seems to have limitations on naming, I tried using a ? prefix but that didn’t work, will probably use _ for myself in the future - cool feature!

there’s a readme in the snippets plugin that shows how to do it

@stobot

The field/index completion is awesome! This will be very handy!

yes that’s definitely a highlight

@stobot

Looks like the [[Link]█] bug is still there just as reminder

that should be fixed now!

Thanks for your feedback and best wishes,
Simon

[BurningTreeC]

Hi @Yaisog

The plugin now has a “show trailing whitespace” toggle and a “remove trailing whitespace” button

[CodaCoder]

Bingo!

Not sure about the <!-- comment --> handling

[CodaCoder]

Simon, can you add matching/closing quotes support for:

	Description	Character	Named Entity	Numeric Entity	Unicode Code Point
1	Left double quote	“	“	“	U+201C
2	Right double quote	”	”	”	U+201D
3	Left single quote	‘	‘	‘	U+2018
4	Right single quote	’	’	’	U+2019

I only use 1 and 2 but 3 and 4 should be made available for completeness.

[CodaCoder]

Simon, not sure what you called this in the previous version – I’ll call it predictive text. The editor stored previously found words and offered them up as you typed. I’m a huge fan of how you made that work, and a huge for of predictive text, especially for lengthier words (I’m not a great typist! )

Do you plan to re-implement that in CM6new?

[Yaisog]

When writing filters, typing <variable> will add a closing tag </variable>. Is there a way to check if we’re inside a filter (after a not-yet-closed opening [) or if variable is a valid variable name, to then suppress the closing tag?

Also, if I start a word, close the autocomplete popup, and continue writing the word, the new autocomplete popup will show suggestions starting with the newly typed letters, not considering the beginning of the word, e.g. type titl, press ESC, type e to get suggestions starting with e, not with title.

[BurningTreeC]

Hi @CodaCoder

@CodaCoder

Simon, can you add matching/closing quotes support for:

	Description	Character	Named Entity	Numeric Entity	Unicode Code Point
1	Left double quote	“	“	“	U+201C
2	Right double quote	”	”	”	U+201D
3	Left single quote	‘	‘	‘	U+2018
4	Right single quote	’	’	’	U+2019

I only use 1 and 2 but 3 and 4 should be made available for completeness.

I’ve added something but could not test it, could you please test?

@CodaCoder

Simon, not sure what you called this in the previous version – I’ll call it predictive text. The editor stored previously found words and offered them up as you typed. I’m a huge fan of how you made that work, and a huge for of predictive text, especially for lengthier words (I’m not a great typist! )

Do you plan to re-implement that in CM6new?

already implemented but must be enabled in the ControlPanel > Settings > CodeMirror > Editor

Thank you for your ideas and best wishes!

[BurningTreeC]

@Yaisog

When writing filters, typing <variable> will add a closing tag </variable>. Is there a way to check if we’re inside a filter (after a not-yet-closed opening [) or if variable is a valid variable name, to then suppress the closing tag?

Hi @Yaisog that’s fixed now, thank you for reporting!

@Yaisog

Also, if I start a word, close the autocomplete popup, and continue writing the word, the new autocomplete popup will show suggestions starting with the newly typed letters, not considering the beginning of the word, e.g. type titl, press ESC, type e to get suggestions starting with e, not with title.

Oh wow, that’s very bad! I’ll have to dig into this. Also here, thanks for reporting!

[jeremyruston]

Congratulations @BurningTreeC, this is exceptionally impressive.

It fills such a yawning gap for so many users that I would be very interested in publishing it as an official plugin.

[BurningTreeC]

Thanks @jeremyruston and yes! let’s do that!

[BurningTreeC]

@Yaisog

Also, if I start a word, close the autocomplete popup, and continue writing the word, the new autocomplete popup will show suggestions starting with the newly typed letters, not considering the beginning of the word, e.g. type titl, press ESC, type e to get suggestions starting with e, not with title.

@Yaisog where does this bug happen? In which context? Within a filter, a macro, something else?

[Yaisog]

I just upgraded to v0.0.12 and cannot reproduce it anymore.

[CodaCoder]

That’s what I get when I hit my key macro. Here is CM6old:

[BurningTreeC]

Haha @CodaCoder - I messed with the inner workings of CodeMirror!

In the “old” CodeMirror plugin this works?

[CodaCoder]

The curly quotes? Sure.

[CodaCoder]

STOP. Your work is done

I can fix it myself, at the key macro generation (AHK). “ and ” are working just fine.

---

For anyone interested, save your AHK script as utf-8 with BOM

[CodaCoder]

Simon, thanks for the rapid updates. Much appreciated.

Line 1: The comment is preventing detection of an incomplete macro definition.

Line 4: name already defined in a child macro is not an error.

[BurningTreeC]

Hi @CodaCoder - that’s tricky to get right … first of all it’s the indentation that makes the second test-1() invalid. Then there are also nuances in parsing pragmas that I have to fix

EDIT: or is \define → indented valid TW syntax? I never questioned the opposite…

[CodaCoder]

@BurningTreeC

is \define → indented valid TW syntax?

It is. Has been since they were introduced.