12-Feb-22: New Logseq Product Designer, Intro to Plugins, Filtering Daily Note Pages, Pages or Blocks, Logseq Sync Update

With all this talk of tech and the new Samsung S22 being released, I thought I would try and bring the outdoors, indoors, for a moment as this week is also about the Club World Cup (CWC) being played in Abu Dhabi. I would talk about the Winter Olympics, but shock that people have already been caught doping so will pass on that. Anyway the CWC is a competition that is played every year in a different location between the winners of various prestigious competitions such as the Libertadores or Champions League. The final, which kicks off in a few hours, will be Palmeiras vs Chelsea.

Why is this of relevance, well depending on how the result goes I may be silenced by my better half who is an avid Palmeiras supporter being from Sao Paulo. Whereas I spent a considerable amount of time growing up in Fulham on Stamford Bridge’s doorstep. Nothing like a bit of “friendly” competition.

With the above being said, let’s kick off with this week’s LogseqWeekly.


  • Unfortunately for the third week running, there are no new releases to report on. However, the devs are back to work after the Spring Festival holiday so fingers crossed we will be presented with something new shortly.
  • To download the latest version, check here.

Logseq News / Events

  • Jakob (@DerScheinriese) has joined the Logseq Team as product designer. “Having spent the last two years exploring this category of tool both practically and academically, I’m immensely excited about the chance to help shape one of these productized visions of the future of knowledge work.” Looking forward to seeing what Jakob brings us.
  • Looks like we have an update on Logseq Sync @An commented “I’d say around 2-3 weeks! Hopefully not too much longer :p”
  • An Intro to Making Logseq Plugins ft. Sawhney is scheduled for Wednesday 16th February @ 13:00 GMT LINK. Prolific Logseq plugin creator @aryansawhney17 will join us to talk about his coding journey through Logseq plugin development. He taught himself just enough code in a single weekend so he could create his first plugin. If you’re interested in learning to code or want to get started with Logseq plugin development, this session is a must-attend.
  • An event with Dario (@OneStuttering) about how he uses Logseq is also being lined up. I will keep you updated when dates are set.
  • Ramses (@rroudt) is also looking for others to “plan live sessions so we can all learn from each other on how to use Logseq in different ways.”
  • @privacytoolsIO (Encryption Against Mass Surveillance) has added Logseq in their Digital Notebooks. Not encrypted, but the server will never store or analyze your private notes. Your data are plain text files.”
  • In case you missed the Logseq Office Hours on January 27th, here is the full recording including timestamps.

Logseq Mobile

To access the mobile apps, please the the respective link for your OS below. Also, please keep in mind that the mobile apps are relatively new releases so may have some performance issues. The devs are working hard to sort this out and squash as many bugs as possible.

  • iCloud still seems to be causing major issues with certain users and creating duplicate notes, not saving data correctly, or just not saving data. The issues seems to be on the iCloud side of things but hopefully the devs will be able to work their magic to make the syncing feature smooth for all users.

Logseq Workflows

  • For all you Tauri fans out there, @kanru was curious about how well Logseq can run with Tauri so created a branch and stubbed enough handler to be able to run the demo graph. The resulting binary size is 44MB stripped on Linux. Next he will try to implement the filesystem APIs. You can checkout the branch here.
  • A somewhat common issues that comes across the Discord is that the interface is a bit overwhelming and there are doubts about where to start. Thanks to @HDanzu, we have a clear image of what is going on and what everything does. A real masterpiece.
  • Staying with @HDanzu for a minute, we are presented with a very cool post of their Logseq set up. There might be a lot going on, but everything seem to have a place and fits nicely. Definitely going to be taking some inspiration (i.e. unshamefully stealing ideas) from this. Check this post out for the light version. Full write up included here.
  • Wanting to add sections to the Favourites area of Logseq. @Luhmann provides us with a workaround solution: “create and favorite pages that act as section markers, like >>GTD<< and >>Reference<<. You can move items up and down the Favorites list so you can put them between these pseudo folders to give some organization to your list.”
  • Print to PDF? While the devs work on a more official solution, @Paul provides us with the following: “Export graph as html (save on your desktop), open the index.html (double click/drag into the browser window). From there you can open the standard print view and select “Print as PDF”. Alternatively, you can also open Logseq via a browser (logseq.com) and then print from there. Or of course, “alternatively you can open the .md file in any markdown editor that prints to pdf (typora, mark text,…), but that won’t output embeds and block-refs properly.”
  • @brandontoner presents us with a genius trick regarding namespaces and the journal pages. Fascinated by this and it made me change my date format. Thanks a lot for posting this great tip Brandon.
  • Dario (@OneStuttering) launched his “Outline Your Mind with Logseq” course. The course aims to Unify all your note-taking workflows in one system, Facilitate clearer thinking and reflection, Become comfortable with designing and implementing your own workflow and more. I am do not usually include paid content in the newsletter but with all the great YouTube videos Dario has done over the past month, it deserves a mention. Be sure to check it out (not affiliate link).
  • For those in doubt / wanting to use Logseq and Obsidian side by side, this great analogy by @sscotty rings very true – If we go with the roommates analogy. . . They have agreed on the furniture (markdown and links), but they argue about everything else: Let’s have vinyl records! No, just digital music! Wired headphones! No, Bluetooth! Anything advanced will break. You have to choose.
  • @Devin asks “I use Teams. But typically the tel:<phonenumber> links work with it. The problem is Logseq is treating the link as a page name, probably due to a lack of recognition of tel: as a URI prefix.” Danzu provides a fix with [Dial: 15551234567](tel://15551234567). Who would have thought it would be possible to dial a number from within Logseq. Crazy stuff.
  • @Cannibalox comments on a point which I am sure will ring true to a good number of users “I index scenes, characters, themes, actors, framing, focal-length, …. Since my purpose is to quickly find similar cases in different movies (eg: quickly find multiple ways to shoot a #car-crash for instance) , I try to keep one page per movie with lots of tags and properties. I’m still debating what should be a property and what should be a tag though (currently, most technical info/imdb-metadata is in properties – budget, cast, director… and I create a separate bullet per scene/chapter with tags and screenshots… but I’m thinking of transforming tags into properties for the query table view – the drawback is properties in the graph view…).”
  • @qwxlea provides their take “Having gone back and forth about tags and properties: – properties look good, and don’t clutter up the interface, and can be used in all kinds of fancy queries – But, properties are awkward to add, and don’t naturally flow – tags can be easily added anywhere, but make the end result looks more messy – if you want to export a page you have ugly tags all over the place Personally I use virtually no properties, I use Logseq as a journal and second brain, not as a good looking database. It doesn’t have to look pretty, it should just be functional.
  • @ZelenaKrava provides their comments on a page vs block centric approach: “There are various thoughts on this. It depends if you are making your content more page centric or block centric. I tend to do it more page centric, and so the content within the page will contextually belong together. So I personally only use property tags on top of the page. Plus I came from org-mode and there it was only page related if I recall correctly. Then within the page sporadically I would use inline tags. This would typically be on a line which is a task. For example tagging a person who is to do the task. On the other hand, if you had more disparate content on your page, then having block properties might make sense. Having come from a programmatic background, I also have a tendency to use namespaces. To make things super simple, I use the built in logseq concept: I name the actual page using namespaces, like so: projects/outdoor/wood shed…. or equipment/heavy/excavator …. I also use it for people: people/family/joe …. or people/business/Sam … and then in page property tag I use alias, for example people/business/sam would be alias:: mechanic. This then gives me some structure, but I can also use the alias for easy tagging. I find these concepts work wonders for me and so far it is a good structure to use in queries too… One bonus to use the namespaces in the file name of the page is that logseq automatically parses it into a clickable hierarchy on the bottom of the page, which is just super duper helpful. So much functionality for free and without extra effort. That is what I love about logseq”

Logseq Feature Requests

You can check out the full list of Feature Requests here.

  • Native Task Management – A dedicated task management system for new users to use as a default would reduce the friction between users and their tasks. Currently if a user wants to add task management, they need to reference several FAQ pages, find the query they “think” might work, dig through countless posts on the Discord Datalog page, etc. All this and they could still accidentally delete their entire task management query or entire page. A simple page with a grid that shows tasks and a native UI filtering and sorting function would be a great start to solving this issue. Yes, queries are a possible solution, but they’re not a fully featured solution in they way that a native and dedicated page would provide. The fact that only a few people on Discord seem to always respond to the same recurring questions of “How do I show a query that shows my…?” is evidence that a basic and native system is needed by the community of current users and future users as well.
  • Changes saved to file indicator: much needed! – A while back, some people have discussed having a “confirmation” that a file was saved. At the time I was opposed to it (mostly because I was concerned about cluttering the interface.) After experiencing some dataloss this week, I reconsidered. I had a weird case (on iOS) where Logseq wasn’t writing the changes in the file on the file system. I tried to close the app, reopen it, make new changes. Nothing worked: the local file didn’t have the changes.
  • Generate documents from blocks and pages – With all my items, I would like to generate ‘documents’ (my word) from content in Logseq. Documents can be edited to include various blocks and/or pages. Then rendered to create a single document from the content inside the blocks. Make a change in a block and re-render the document to get a new file User Guides, Resume, Web pages, technical documentation and more. The documents generated can be md, html, pdf, etc.
  • Card groups, or cards grouped by block – Have multiple topics in my database, and find it better personally to review a certain set of flashcards by topic, instead of everything mixed together. For example, I would like to only review flashcards that relate to work topics like SQL queries, etc, and at another point review all the cards related to learning Greek. Or even, within the Greek learing “domain” to be able to specify which sub-topic’s cards I would like to review, for example, Verb Paradigms. In short, I think it would be great if you could have some form of card “folder” or “group” in which you can dump related cards, so you don’t ONLY have to review ALL your cards together and in random order.

Logseq Plugins

  • Logseq Anki Sync – @Lightink – New Update for Logseq Anki Sync (v1.1.0) Logseq Anki Sync plugin now has support for page embed. Also, multiline cards now include all sub-children blocks like logseq by default.
  • VIM shortcuts – @vipzhicheng – Logseq VIM Shortcuts v0.0.6 updates In this release, I added a VIM-like visual block mode, in this mode j, k, J, K have different behaviors. j and k are for selecting up and down, J and K are for moving up and down. use ctrl+v to toggle visual block mode.
  • Smartblocks @aryansawhney17 Major update to Logseq Smartblocks: v 2.50 feat: ability to define variables feat: ability to request user input You can now take inputs to a function to assign it to a variable and have those apply to all instances of the variable being called. It’s incredibly useful for a higher level of customization. You can do things like auto populate pages based on the specific input, manage CRMs, diary entries, appointment or meeting notes and a ton more with a lot less friction. It’s also got a lot of roam smartblock’s function and many of smartblocks that you find online can be directly ported by changing the syntax just a little bit.

Many thanks for reading this week’s LogseqWeekly episode.