In the end I added this to my keymap-destop.json file and then imported it:
{
"command": "tabsSwitchLastActive",
"accelerator": "Ctrl+Tab"
}
Alt+Q works too.
3 Likes
It seems that clicking on a pinned tab clears the search box. This makes it more difficult to go through a search list and pin some tabs from it (at least if I double click).
Could you prevent clicking on tabs from clearing the search?
There are Pin Tab and UnPin Tab commands. Could you make option to Toggle Active Tab from one keyboard shortcut?
Yes I know that double clicking on a tab also opens it at the same time. However, the fact that this ends the search is due to the app itself. I can not influence that through the plugin.
But you know that you can select multiple notes in the search result (note list) and then add them directly as pinned tabs via drag&drop or the context menu? That would save you at least the double-click on the tabs.
1 Like
Do you really see the need to constantly pin a tab and unpin it again and again? Honestly, I think that the plugin already has enough commands. I don't want to overload it with commands unnecessarily.
I didn't know that. Thanks for the thoughtful tip!
In some cases that work around doesn't work though, as I often need to see the note determine if it qualifies to pin for later review and action. I'll have to remember to use the pin icon instead of double clicking.
I would use such feature, not constantly but it would be good ux.
I love this plugin, it is so useful when you keep switching back and forth between 2 or 3 notes!
Unfortunately, it dies every 2 or 3 days of Joplin use: the tabs stay visible but they become entirely unresponsive to clicks, keyboard shortcuts stop working, menu items don't do anything. At the same time Joplin keeps working normally. The only way to get the plugin to work again is to restart Joplin.
I was unable to find a particular event that triggers the bug and I don't see anything relevant in Joplin log file unfortunately.
This is Joplin 1.7.11, Note Tabs 1.2.0 on Ubuntu 20.10.
I'd be happy to open a github issue or to turn on more verbose logs if there's a way to do that.
And I thought that I was the only one experiencing this problem!
1 Like
Hm... I have never let Joplin or my PC run that long at a stretch. Might be difficult to find the root cause. But I could imagine that it has something to do with the following error: Infinite message loop? · Issue #36 · benji300/joplin-note-tabs · GitHub
I haven't had time to look at it yet but I want to look at it next.
If I would provide a Bugfix Release for the above issue, could you check on your side if this would fix your problem also? If not, I will take a closer look at the problem.
Yes of course, just let me know when it's ready and I'll set it up.
Note that I have not noticed the cpu being pegged when that bug happens so it may very well be a totally different issue.
1 Like
I just experienced this issue for the first time. I often leave Joplin open a few days at a time as well.
I don't know what triggered it, but the interesting thing might be that I had not interacted with the plugin's interface in a while. I had only one (unpinned) tab visible, and was just moving between various notes in Joplin. I noticed at one point that the tab title in the plugin's pane didn't match the note I had open, and then discovered it was unresponsive.
1 Like
@philippelr, @heviiguy and @mzguy: Does this behavior only occur with this particular plugin, or do other plugins behave this way as well? Possibly it is a problem in the plugin system. That is another point that we should check. But maybe not with a Plugin that was not written by me. 
Maybe with the "outline" plugin, it has a panel and you could check if after the time the links still work.
I'm currently not running any plugin other than note tabs but I just setup the "outline" one. We'll see what happens.
I run Windows 10 and typically only restart the PC once a week (use sleep mode overnight), and have Joplin running always. Haven't experienced this non-responsive note tabs issue yet, but will keep an eye out.
My instance of this plug-in just froze again. I had to quit the program and restart to regain functionality.
I had only had Joplin open for an hour or so when the tabs became completely unresponsive. Everything else, including the favourites tab as well as being able to navigate to notebooks and notes worked as expected.
Prior to crashing, I was cutting and pasting md table code from 50 or so individual notes in order to consolidate the individual tables into one note. I hadn't been making use of the Note Tabs feature during that time.
Joplin 1.7.11 on Mac OS 11
Note Tabs v 1.2.0
1 Like
It's been 2 days since the last restart and as is now expected, note tabs were unresponsive when I first looked at Joplin the morning. The "outline" plugin is still working normally. I had checked Joplin last thing on the previous evening and everything was normal then so I'm sure no user action triggered the freeze in my case.
It may or may not be related but I'm also noticing that Joplin with the note tabs plugin enabled and functional, there is a joplin process constantly using 10% of 1 cpu core while the app sits idle and that same process takes 1.5GB of memry (rss). After the plugin died this morning, joplin is back to 0% cpu usage and the fat process is gone.
If I restart joplin with note tabs disabled, there is no fat process either and cpu usage is 0%.
Immediately after I restart joplin with note tabs enabled (well, after I leave it a minute or two to settle down), there is again a joplin process at 10% cpu usage. No joplin process is using lots of memory yet but that could grow only over time.
Assuming the high cpu usage is related, maybe it's easier to debug since it happens as soon as Joplin is started. Could the plugin be constantly in a semi busy loop that leaks memory and that eventually leads to its death?
@benji300, if that can help debug the issue. If you open the app in dev mode while the plugin is running, it should show you in the console the messages that are being sent/received between the plugin and app, and you might find that it's sending too many of them.
1 Like
I've just noticed that I have the following Joplin process running:
- Joplin
- Joplin Helper (GPU)
- and 18 unique instances of Joplin Helper (Renderer) !
I've just published a new version of the plugin: v1.2.1 (Release on GitHub)
Fixed
- Issue that caused infinite message loop between plugin and app (#36)
I guess this should also fix the "unresponsive" issue which was reported here and on GitHub (#39).
@philippelr: Could you please check if this fix solves your problem too?
4 Likes