Thanks, @laurent. Super helpful. This is what I deserve for not writing up my build notes from way back when when I figured out how to do these things the first go around. I will write something up for myself this time. As for not supported. Yeah, that is why never said anything in the past. It's a niche use case. If only I knew javascript better than I do ...
After a simple elimination method, I found that this problem only occurs after installing Joplin for the current user. . . JoplinPortable everything is normal
The modification of the attachment resource does not seem to take effect. I modified the text content in a txt attachment resource and clicked Sync, but the resource on OneDrive has not changed. Is there a way to know what step went wrong?
External editing is broken (at least in Typora). It open the editor, but does not detect (and discards) any editing changes done outside Joplin.
P.S. Sorry, I did not read all the thread - similar issue has already been reported above on a different editor
v1.4.11 is now available! This release is becoming massive, but other than maybe a few more bug fixes I think we're getting there. No plugin or API breaking changes in this new version, but two features marked as deprecated - see below for the full list.
Plugins: joplin.views.dialogs.open() now returns an object instead of the button ID that was clicked. So for example instead of getting just "ok", you will get { "id": "ok" }. This is to allow adding form data to that object.
Deprecated:
The following features are deprecated. It will still work for now but please update your code:
Plugins: All create() functions under joplin.views now take a viewId as a first parameter.
Plugins: MenuItemLocation.Context is deprecated and is now an alias for MenuItemLocation.NoteListContextMenu
Plugins: The app_min_version manifest property is now required. If not provided it will assume v14.
Plugins: The id manifest property is now required. If not set, it will be the plugin filename or directory.
Maybe I missed that info in the docs, but I was looking for it.
So how does the Install plugin button work? Do I have to select the dist directory? And how does the .jpl format look like? Is it a tar of the dist dir?
This button is only to install .jpl files, which will be the preferred distribution format. You can still drop a complete plugin directory in the "plugins" profile folder, and it should show up in the GUI.
And how does the .jpl format look like? Is it a tar of the dist dir?
Yes, a tar of the dist directory. It is built automatically if you use the Yeoman generator.
@rxliuli, I cannot replicate this issue, nor did I know there was a problem with it before. Does it show the orange banner on top when the file is being edited?
I tested VSCode and the results were the same. I suspect it is related to Joplin's file listener, but I did not conduct in-depth testing. I will enter the database level when I have time.
Regarding this point, I finally used the split screen of Windows to redisplay it. It shouldn't be the problem of Joplin itself. It may be that I accidentally moved the window out of the window or other invisible unknowns.