Skip to content
New issue

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

TypeError: r.getAllMarks #7

Open
channingwalton opened this issue Nov 11, 2021 · 12 comments
Open

TypeError: r.getAllMarks #7

channingwalton opened this issue Nov 11, 2021 · 12 comments
Labels

Comments

@channingwalton
Copy link

@channingwalton channingwalton commented Nov 11, 2021

Obisidian version v0.13.0

Uncaught TypeError: r.getAllMarks is not a function
    at eval (eval at <anonymous> (app.js:1), <anonymous>:367:59524)
    at Y8.withCodeMirrorEditor (eval at <anonymous> (app.js:1), <anonymous>:367:60241)
@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Nov 12, 2021

Thanks for reporting! I'll try to look into this later this week.

@kmaustral
Copy link

@kmaustral kmaustral commented Dec 1, 2021

Same here on v0.13.6
image

@vincentteoh
Copy link

@vincentteoh vincentteoh commented Dec 2, 2021

Same error message here.
image

@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Dec 2, 2021

Seems like the API has changed in v13.x. I'll have time to look at this next week. Thanks for reporting this!

@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Dec 9, 2021

I believe that once Obsidian 13 is officially released, it'll have a Legacy Editor option to support plugins that depend on features that haven't yet been made available to plugins in 13.x. I'll look for a proper fix, but at least the plugin will continue to work with the new option.

@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Dec 10, 2021

I've added a Troubleshooting section in the README on how to enable the Legacy Editor for now.

@rushikb
Copy link

@rushikb rushikb commented Dec 21, 2021

Hi Marcus! I'm a big fan of Vale— just wanted to check whether you still plan on supporting CM6 now that Obsidian 13 is officially released. This is such a phenomenal tool

@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Dec 22, 2021

Hey! I'm definitely planning to upgrade the plugin. I haven't had the chance to look into it yet, but AFAIK the new Editor API has yet to achieve feature parity with CM5, and doesn't support markers yet. If there's a way to grab the CM6 instance somewhere, that might also work. If anyone knows how, I'd be happy to prioritize this. Otherwise, I'll try and find some time for this in the coming weeks.

@chrisgrieser
Copy link

@chrisgrieser chrisgrieser commented Dec 22, 2021

yeah I came here to report the same thing – it seems the new editor is not supported :(

Screenshot 2021-12-22 21 23 53

@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Dec 23, 2021

@chrisgrieser Sorry 'bout that 🙏 I'll try and look into this next week.

@marcusolsson
Copy link
Owner

@marcusolsson marcusolsson commented Jan 9, 2022

Just to give an update. I've been reading up on how to migrate from CM5 to CM6, and unfortunately there doesn't seem to be an easy fix to this.

If anyone want to experiment, here's the best resources I've found so far:

Seems like we'd need to build a CodeMirror extension rather than calling methods for adding marks.

I haven't given up on this, but right now this seems to require more time than I have at the moment. Seems like I need to read the CodeMirror docs more closely before I give this another try.

Thanks for the patience! 🙏

@eleanorkonik
Copy link

@eleanorkonik eleanorkonik commented Jan 11, 2022

Thanks for including the experimentation tips! I'll include this in the Roundup :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants