Ivan Gretsky

@cb2004 , thanks for your suggestion. Did try [moving that line](https://github.com/processwire/processwire-issues/issues/1564#issuecomment-1119714653) from init() to ready(), but it didn't seem to help, @ryancramerdesign , do you have any ideas how we...

An option might be to leave markdown in the core and add TinyMCE with the new license as a plugin.

> I'm currently thinking the best way forward would be to fork the existing MIT code for our use, likely stripping things back as much as possible to reduce the...

I would propose consider leaving only one type of markup - markdown. And have all the extra markup as markdown plugins. Full conversion between modes doesn't work in all cases...

Thanks, @glenn2223! I've read about this option. It is kind of a hack, but until we have something like [this](https://github.com/microsoft/vscode/issues/15909) it is probably the only way to do it out...

> I'm not sure as I'm not familiar with this type of setup. However, You may be able to just create a NAME.code-workspace file in the hosted project with the...

I think we misunderstood each other... I was talking about not a global, but rather local live-sass-compiler settings file. So if it is present, no other settings apply at all....

Ah, ok. I just wanted to make sure my idea is clear. My thoughts were those configuration files are pretty common, so devs are used to have dedicated configs in...

Hey @glenn2223 ! I just thought of anther possible way to solve this. Could we trigger the compiler with a [VS Code tasks](https://code.visualstudio.com/docs/editor/tasks) sending in the params? Just maybe it...

That worked, thanks! Now I noticed those commands in the help list. But `./vendor/bin/migrate create -h` still shows this option: ``` -t, --type=TYPE Alternative template type [default: "default"] ``` Should...