Pre-release 1.3 with plugin support is now available! (Updated 31/10/20)

tessus · 2020-10-25T19:30:42.103Z

What are you trying to say. You fixed it and created a PR?

laurent · 2020-10-25T21:41:07.894Z

I think he might be a bot since his posts make no sense.

benji300 · 2020-10-28T11:38:55.914Z

Okay... thanks for your answer.

benji300 · 2020-10-28T12:25:01.951Z

Sorry my bad... I should have read the spec better.

Regarding the panels layout...
What about a "dynamic" layout where users can drag&drop the panels to any location they want? Like most of the IDEs provide (e.g. Eclipse, Visual Studio, Visual Studio Code).
In this case it doesn't matter where a panel is created by default. One API to create a panel would be enough for the plugins.
But then Joplin needs to save the panels layout. Also for the plugins. I'm not sure if you want this.

Another question would be: Shall it be possible to "overlay" panels then? To have a "tabbed" view of panels like VS Code does for opened editors.

Here's a screenshot of what I am trying to say:

screenshot|75%1920×997 325 KB

Green: The area where the panels can be moved
Orange: Here panels can be dragged to
- Basically you can create new columns, lines and also cells within a column or line
This also includes that the note list and editor should be handled like all other panels
- In the screenshot the global search is handled as an own panel (just an idea...)

I totally agree that this would be a huge change for Joplin and might not match with your intention for a simple note taking app. But that's the only idea I have for a generic panel API.

laurent · 2020-10-29T13:28:03.821Z

1.3.10 is now available!

New: Api: Added service to access resource external editing
New: Plugins: Add the openNote, openFolder and openTag commands
Fixed: Regression: Keyboard shortcut would not save in some cases
Fixed: Regression: Restore "New sub-notebook" command
Fixed: Command Palette click did not work
Fixed: Fix slow Katex rendering when there are many global definitions (#3993)
Fixed: Fix syntax of imported resources when importing ENEX as HTML
Fixed: Fixed OneDrive authentication
Fixed: Fixed sync issue when importing ENEX files that contain new line characters in the source URL attribute (#3955)
Fixed: Handle gzipped CSS files when importing from clipper (#3986)
Fixed: Update highlight.js to fix freeze for certain code blocks (#3992)

GitHub

Release v1.3.10 · laurent22/joplin

New: Api: Added service to access resource external editing New: Plugins: Add the openNote, openFolder and openTag commands Fixed: Regression: Keyboard shortcut would not save in some cases Fixed: ...

wandern · 2020-10-29T17:43:55.996Z

I've run into various types of errors with 1.3.10 while importing various .enex files. Here are three examples. Most of them have been encountered more than once.

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at Object.stat (node:fs:1061:10)
    at Object.stat (/Users/someuser/.joplin-bin/lib/node_modules/joplin/node_modules/graceful-fs/polyfills.js:298:16)
    at isSrcSubdir (/Users/someuser/.joplin-bin/lib/node_modules/joplin/node_modules/fs-extra/lib/move/index.js:153:6)
    at Object.move (/Users/someuser/.joplin-bin/lib/node_modules/joplin/node_modules/fs-extra/lib/move/index.js:24:3)
    at /Users/someuser/.joplin-bin/lib/node_modules/joplin/node_modules/universalify/index.js:13:12
    at new Promise (<anonymous>)
    at Object.move (/Users/someuser/.joplin-bin/lib/node_modules/joplin/node_modules/universalify/index.js:7:14)
    at saveNoteResources (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/import-enex.js:183:12)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:93:5) {
  code: 'ERR_INVALID_ARG_TYPE'
}

...

[Error: ENOENT: no such file or directory, stat '/Users/someuser/.config/joplin/tmp/717f4e9cfd5d88b3fd8c040ccde840de.base64.decoded'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/Users/someuser/.config/joplin/tmp/717f4e9cfd5d88b3fd8c040ccde840de.base64.decoded'
}

...

Error: EISDIR: illegal operation on a directory, read

wandern · 2020-10-29T17:47:28.931Z

Regarding atomic database operations, etc. This is what happens to an import process when a 'joplin sync' is triggered in the background.

It's unclear whether the "ERROR" is actually an error, or if the import process is retrying, or if a DELETE is actually failing (and potentially leaving something inconsistent):

Error: Error: SQLITE_BUSY: database is locked: INSERT INTO `note_tags` (`note_id`, `tag_id`, `updated_time`, `user_updated_time`, `id`, `created_time`, `user_created_time`) VALUES (?, ?, ?, ?, ?, ?, ?): 65982470864b43d1ab2e0d034f44e649,864e84baa5ef4dfca7d47a86035eae3d,1603993373023,1603993373023,5e5e6d57862c4cd193fa965ac820129a,1603993373023,1603993373023
    at DatabaseDriverNode.sqliteErrorToJsError (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database-driver-node.js:21:18)
    at JoplinDatabase.sqliteErrorToJsError (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database.js:25:24)
    at JoplinDatabase.tryCall (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database.js:104:45)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)
    at async JoplinDatabase.transactionExecBatch (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database.js:161:4)
    at async Function.save (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/BaseModel.js:503:4)
    at async Function.addNote (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/models/Tag.js:64:18)
    at async saveNoteTags (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/import-enex.js:198:3)
    at async saveNoteToStorage (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/import-enex.js:225:22)
    at async processNotes (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/import-enex.js:345:21) {
  code: 'SQLITE_BUSY'
}
/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database-driver-node.js:21
        const output = new Error(msg.join(': '));
                       ^

Error: Error: SQLITE_BUSY: database is locked: DELETE FROM item_changes WHERE item_id = ?: 9896f891caef4ecc9a932985d0b191ee
    at DatabaseDriverNode.sqliteErrorToJsError (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database-driver-node.js:21:18)
    at JoplinDatabase.sqliteErrorToJsError (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database.js:25:24)
    at JoplinDatabase.tryCall (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database.js:104:45)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)
    at async JoplinDatabase.transactionExecBatch (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/database.js:173:5)
    at async Function.add (/Users/someuser/.joplin-bin/lib/node_modules/joplin/lib/models/ItemChange.js:25:4) {
  code: 'SQLITE_BUSY'
}

laurent · 2020-10-29T18:51:08.176Z

wandern:

I've run into various types of errors with 1.3.10 while importing various .enex files. Here are three examples. Most of them have been encountered more than once.

Please provide an ENEX file to replicate the issue.

wandern · 2020-10-29T19:20:15.298Z

laurent:

Please provide an ENEX file to replicate the issue.

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.

However, the information on debugging the command line app here: joplin/readme/debugging.md at master · laurent22/joplin · GitHub is not working as I would expect.

joplin --debug --log-level debug import filename.enex

is not adding any additional debug information in $HOME/.config/joplin/log.txt

I can't find anything in log-database.txt that lets me correlate the error to a specific note. Do you have any suggestions?

Thanks!

laurent · 2020-10-29T22:18:18.894Z

wandern:

is not adding any additional debug information in $HOME/.config/joplin/log.txt

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.

tessus · 2020-10-30T02:08:36.431Z

Some combinations of modifier keys can't be assigned via the UI keyboard shortcut editor:

e.g.:

Ctrl+Option+Shift+Cmd+[A-Z]
Ctrl+Option+Cmd+[A-Z]
Option+Shift+[A-Z]
Option+Cmd+[A-Z]
Option+Shift+Cmd+[A-Z]
Ctrl+Option+[A-Z]

You can use them in the json file, but not via the UI.

tessus · 2020-10-30T18:55:57.552Z

@laurent shall I open a gh issue for this ^^^ or is above post enough?

laurent · 2020-10-30T19:00:04.103Z

I don't know how to fix this to be honest as I don't understand why the Option key wouldn't work. Perhaps @anjulalk would know something?

anjulalk · 2020-10-30T19:25:25.435Z

tessus:

Some combinations of modifier keys can't be assigned via the UI keyboard shortcut editor:

e.g.:
Ctrl+Option+Shift+Cmd+[A-Z]
Ctrl+Option+Cmd+[A-Z]
Option+Shift+[A-Z]
Option+Cmd+[A-Z]
Option+Shift+Cmd+[A-Z]
Ctrl+Option+[A-Z]
You can use them in the json file, but not via the UI.

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.

laurent · 2020-10-30T22:48:21.740Z

No I think that's reasonable, I thought about something like this too, and the underlying component is made with that in mind. The layout in particular can be saved/loaded from JSON if needed.

The problem indeed is how to create a UI that can be developed relatively easily. Drag and drop is often messy to implement so I'd favour a solution without it but not sure what.

laurent · 2020-10-31T13:22:58.675Z

Version 1.3.11 is now available:

Improved: Make sure all commands appear in keymap editor
Fixed: Add history backward and forward commands to keymap and menus (#4010)
Fixed: Fixed handling of Option key for shortcuts in macOS
Security: Remove "link" and "meta" tags from notes to prevent XSS

GitHub

Release v1.3.11 · laurent22/joplin

Improved: Make sure all commands appear in keymap editor Fixed: Add history backward and forward commands to keymap and menus (#4010) Fixed: Fixed handling of Option key for shortcuts in macOS Secu...

benji300 · 2020-10-31T13:23:24.484Z

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.

laurent · 2020-10-31T13:23:30.601Z

dpoulton · 2020-10-31T15:48:11.479Z

laurent:

Version 1.3.11 is now available:

A little bit of beta-testing

Windows 10 Pro x64
Joplin 1.3.11 Portable

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?)

laurent · 2020-10-31T16:38:29.869Z

dpoulton:

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.

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:

plugins/(PLUGIN_ID).js

plugins/(PLUGIN_ID)/index.js

plugins/(PLUGIN_ID)/dist/index.js

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.