I plan on doing that, but since I have personal information in the large .enex files, I'm trying to determine the specific notes that are triggering the issue, allowing me to create an .enex containing only those notes.
The error you've posted above is already good enough, but it's even better if I can replicate with an ENEX, then it's much easier to find a fix. So indeed if you can narrow it down to a few notes that you can share that would be perfect. You can also send them by PM if you prefer.
This is very strange. I have thoroughly tested the editor in macOS, and it worked fine. However it was a virtualized instance, and I used the accessibility keyboard for sending key presses as I don't have access to a Mac.
Let me look into this issue. I don't know what's causing the issue at the moment, but I'll try to give a fix as soon as possible.
That would be great. I didn't think you thought so, too.
I understand the drag and drop problem.
Initially, you could let users edit the layout directly in the JSON file. So Joplin would read this "layout-desktop.json" only once at startup. This is not for "standard" users, but if they can currently install a plugin, they should also be able to edit the JSON file.
Later it might be possible to implement an UI (whatever that might look like) in the options view to define the layout graphically. From which the JSON file is written then.
Placing a plugin in a plugins folder in the profile directory (\plugins\SideBarToggle.js) works.
Moving the plugin to a sub-directory of the plugins folder in the profile directory (\plugins\SideBarToggle\SideBarToggle.js) does not. Previous post indicates that the plugin in the sub-directory should be loaded.
Joplin was restarted after every change.
Keyboard shortcuts settings page appears to have two entries for rename (Rename Folder & Rename Tag?)
Right, the doc wasn't clear. If it's in a sub-directory, Joplin expects a certain structure, as built by the yo plugin command, but if it's a single JS file it can be name anything. So the rule is actually:
The plugin service will look at the following locations:
Any directory or file that starts with "_" will be excluded (convenient to quickly disable a plugin)
PLUGIN_ID can be any string but it must be unique.
Unfortunately the fix (using the KeyCode) had a side effect, which makes it even less usable now.
If you press
option+cmd the following appears in the field: Option+Cmd+[
Cmd+Left (for the history back operation), the following appears in the field: Cmd+%
The are not only shown like this, they are registered a such. So Cmd+Left wouldn't do anything. To use the shortvut to go back I have to press Cmd+Shift+5 (shift 5 is % on the US keyboard)
Some other keys can't be assigned anymore. e.g. the backtick.
I'm trying to debug this, but there's no debug output in that code, so it's hard....
I think I found a way to make this work. The problem is that fromCharCode returns incorrect characters.
I know how to fix this, but it will take a while to get it right. I have a few other things to do this weekend, but I should be able to get it done.
I'm going back to previous posts to see what plugin features could be implemented, and I haven't answered this one. I believe that should already be possible using the data API, by setting the order property of the note. Then you could create two commands that grabs the currently selected note and move it up or down.
And finally you would associate these commands with menu items, which will allow you to se a keyboard shortcut. If you decide to give it a try and need some info, let me know.