Logseq 0.10.1 - Lot's of small fixes, time to upgrade
Вставка
- Опубліковано 9 лип 2024
- Going through the changelog and talking about new features, bugs fixed and overall giving thoughts on 0.10.1
Thanks for all the likes and love, going to see if I can keep up with the Logseq changelogs. :D
Table of contents
00:00 - Start
00:22 - New Search Fixed Issues
01:06 - Cross-platform shortcuts
01:55 - Default search length
02:35 - No search results in folded blocks
03:36 - Filter whiteboard search
04:15 - Accent Color Fixes
04:31 - Block UUID in recents
05:05 - Android Menu See through
05:31 - Fix AND / OR Simple Query
06:37 - Graph Lines not showing
07:32 - Translation Fixes
==== 👋 Contact 👋 ====
Website - toolsontech.com/
Twitter - / toolsontech - Фільми й анімація
Thanks for the walkthrough Bas. Seems like more and more parts are falling into place. i am really exited how logseq is going to evolve.
Yeah, really looking forward to the DB branch, the UI, Properties and speed improvements are things that would make my day to day work so much better.
@@toolsontech Are there any Videos out there where i can get a handle on what the DB branch is? total rookie here...
@@gedankenbalance The short version is that Logseq is working on a system to allow database backends next to markdown. This allows for more information per block making the system more flexible and fast. It's still going to be a while before we can enjoy the full benefits as it's a major overhaul of the core system. I'm currently working on a video about it.
omg i struggled so much with queries and now i know why.. i followed several tutorials and none of them mentioned the functionality was simply broken.
Yeah, had the same issue with some queries I build. With the day to day usage I sometimes forget that it is still marked as alpha code and things sometimes don't work. Any queries you got that didn't work and started working now?
Hi, Is there a way of not getting duplicates in assets folder. If we add a pdf manually into the assets folder and then try to upload the asset from the logseq it creates its own reference with some kind of stamp. Is there a way to avoid this ? Thank you for the time to upload all the tuts.
I usually avoid adding things to the assets folder by hand and instead drag the file straight into Logseq, resulting it being copied to the assets folder and a combination of the file and a page to hold notes on that file being created. While Logseq could take the assumption that the files with the same name are equal it currently doesn't act on it. Though I think a simple md5 sum database of the files might be a good idea to avoid this duplication issue.
Do let me know if switching to dragging straight into Logseq works, if not then we might need to dive into it a bit further.
@@toolsontech yeah dragging does work. It would be nice if Logseq just uses the same name as in assets folder. Thank you
How do you check the current version of your Logseq? How to update after downloading the new version? Do you uninstall the old version before installing new version?
Windows - I have auto updating on and that installs the new version in the background so I just need to restart.
Linux - Use the excellent community made flatpack and run flatpack update
Android - Manually download the .apk and that will ask to upgrade.
No uninstalling the old version
If I want to demo the old version side by side then I'll fetch the AppImage for Linux and run that at the same time. Think the portable version would work for windows.