1-Jan-22: Logseq 0.5.6, Logseq Android and iOS Mobile Apps, Workflows and Plugins

Happy New Year!

Well, there we have it, we have said goodbye to 2021 and can now look forward to seeing what 2022 has in store for us. There has been an incredible amount of development in Logseq in the past year and I cannot wait to see what else the devs have for us.

We started the year with “#” as bullet points and copy and past complications. We then moved on to some fun(ky) undo and a bit of a mystery as to what would happen when you pressed undo – Ctrl+z became a bit of a taboo key press. Luckily the devs were quick off the mark and presented us with a Logseq Canary version of the app with sorted out the “#” formatting, and soon enough, we had a very reliable undo/redo function – how I missed you Ctrl+z. A few users encountered some data overwriting issues when using Logseq on multiple machines but these were soon resolved and controls put in place to avoid any data loss, including Git integration.

2021 was not all about fixing issues and bugs though. The devs presented us not only with a left hand sidebar (which is a stroke of genius) but also with SRS cards, Zotero integration and PDF annotation – what amazing features these are to have built into your notetaking app. A little later and BANG, Logseq Marketplace is introduced for themes and plugins.

To top the cake off, the devs made available the Android mobile app which was shortly followed by the iOS mobile.

What a year, and from the Roadmap, we are in for a treat in 2022. All I can say is thank you to the Devs!



  • Enhance block toggle feature
  • Fix empty block children is not clickable
  • Fix drop into insert mode after using journal shortcut
  • Add {{namespace [[page]]}} macro which can be used as a TOC
  • Docker image for Logseq web app and Guide Doc
  • Nodes in Graph View is unclickable, caused by the wrong pixi.js version introduced in v0.5.5
  • Click link and button behavior
  • Unsynced db between multiple windows, which will cause blank search result pages
  • Block expand/collapse all toggle (to activate, just right click on a bullet point)
  • Transition of the left sidebar when toggling
  • Development experience under Linux/Windows
  • And of course, Namespace Table of Contents:

Logseq News / Events

Just a reminder that @Ramses has set up an event which will take place on Tuesday 4th January 11:00 AM UTC and again on Thursday 6th January at 5:00 PM UTC:

  • An Introduction to Networked Thinking Using Logseq
    • Are you new to the idea of using an outliner like Logseq? Or are you a (former) user of Roam or Obsidian? We’re here to help you learn how to use Logseq!
    • In this hour-long workshop, you’ll learn all the fundamentals of Logseq to help you get most out of your notes.
    • We’ll not just look at Logseq’s features, but also how to build a system for Personal Knowledge Management. There will be room for questions and discussion.
    • Stop adding your notes to an idea graveyard and learn to turn them into a thriving garden of knowledge!

To join what sounds like a fantastic event, be sure to follow this link and click on Events to register your interest and join the session. A recording will be made so if you cannot join, do not worry, I will make the video link available.

  • Work is being done on the Logseq documentation and onboarding – when these are available I will be sure to post a link.

Logseq Mobile

  • We now have both the Android and iOS Logseq mobile apps available. To gain access:
  • The devs are trying to get the apps on the respective app stores to easily download and update the apps.

Logseq Workflows

  • The devs are working on an integration with https://snipd.com/ to take podcast notes and have these automatically integrated into our Logseq graph. If you have any thoughts about the export format please do add your comments.
  • @Danzu once again provides us with a fantastic flowchart of taking book notes with a very good write up available here. The link provides all the details needed to recreate the below, including templates and the structure.
  • Debugging / understanding Logseq queries – @houshuang provides a very good video on how he debugs/fixes an issue with Logseq queries (looking at source code, datalog generated etc). Video is available here.
  • @Latigo explains how they would like to see Logseq “Automatically retains the contents of deleted referenced blocks“. They explain (please do feel free to add your thoughts on the forum post):
    • I usually start by writing down the projects that need to be completed in the journal, then add the required information and a preliminary outline to the project page, after which I add block references to the project page in the journal page and assign them to tasks, specific days, priorities, etc.
    • After that, add and modify new contents in the project page while completing and adding tasks in the journal page. After the project is completed, a thorough review of the project is required for knowledge reusability. The original contents of the project page are modified and eventually a new structure is formed in that project page.
    • During this process, some of the old blocks are no longer needed, so they are removed. However, this would cause the tasks assigned in the previous journal page to become meaningless red characters. Therefore I cannot track my progress in completing this project by re-checking the journal page to which the project belongs.
    • I would therefore expect that if a referenced block is deleted completely, it should be preserved as it was originally supposed to be displayed before it was finally deleted.
  • Improved publish of a selection of notes. @kvistgaard explains that “currently, each page needs to be set as public or private individuals. It will be very helpful (and natural) to make a selected set of pages from All pages as private or public”. He has therefore created the Feature Request – if you agree/disagree, please do add your comments on the forum post.
  • @vicrerodriguez made what I think is a fantastic observation in regards to the resurfacing of notes. It is very easy to take and hoard notes but it is vital that we are able to recall the information as and when needed. He writes:
    • I’ve been struggling lately trying to resurface some notes in my “Evergreens”, and I wanted to know your thoughts on it:
    • The main search can’t find notes if the words you search are not consecutive in the note title. If the title is Logseq is a great tool and you search for “Logseq tool”, you won’t get that page as a result
    • If you are searching for pages, block results get a lot on the way and usually they are listed before what you are looking for. Not sure about your workflow but I have a lot of permanent notes as independent pages, so actually blocks gets things really noisy
    • You can use queries to pull back your page results but I find it pretty limiting since there is no specific Query section (like the search) to look for notes. You actually need to execute the query in an arbitrary note.
    • With queries you depend A LOT on properties, and page properties and block properties are not consistent. Also, depending on properties its not so easy, you need to be pretty consistent yourself, using always the same property and the same value all the time, one little typo and you might miss a note. there is no schema that enforces consistency on that
    • All the limitations on the query dsl can probably be workedaround using datalog queries, but I find them difficult to think of and probably not user friendly for anyone not familiar with it
      What do you think? How do you resurface information from your graph? For me its not enough to just collect notes and their mentions/reference. I very often find my self wanting to connect multiple information (to create new notes) that is not directly linked but Its pretty difficult.
    • I am very interested to see what the Devs do to overcome this potential issue, especially as more and more notes are made. Is it a case of a review of the search engine or something more in-depth that is needed?
  • Telegram <> Logseq. @devonzuegel provides us with a tutorial on how to connect Telegram to Logseq so that when you send a message to a particular Telegram channel, it will also appear in your Logseq notes.
  • Importing Notes to Logseq. For those that want to test Logseq or import notes from another app (excluding Roam where you can use the “Import JSON from Roam Research” function), here are some key steps I previously used:
    • 1 – Open Logseq and create / add a new graph. Top left hand corner – you should see a title with a little arrow, click the arrow and Add New Graph. Close Logseq.
    • 2 – Export the notes from the other app in .md (markdown) format into a temporary folder on your desktop or anywhere
    • 3 – Copy the .md files into the “Pages” folder of the newly created directory from number 1
    • 4 – Open Logseq and hopefully the notes will all be there (you many need to wait a while, and possible click re-index (top left drop down again)
    • If the above goes well – you can repeat steps 3 & 4 into your main graph – think it might be easiest to test in a new graph in case something goes wrong
  • @caraantonaccio used Logseq and the todo progress bar display to post what seems like a very interesting dissertation. I think the power of Logseq to have a birds-eye view of your intent and content and that these can be broken down into small chunks (click on the bullet point to enter focus mode) allows you to get things done as opposed to feeling overwhelmed by what needs to be done.
  • I am also really looking forward to the results of this experiment being carried out by @rcvd_io

Logseq Plugins / Themes

To activate the plugins, you need to

  1. Click the 3 dots in the righthand corner and go to settings,
  2. Got to advanced and enable Developer mode,
  3. Restart the app,
  4. Click 3 dots and go to Plugins, then Marketplace,
  5. Install the desired plugin(s).
  • Easy Publish – GitHub action that will do graph load/publish if there is a new commit being pushed. You can then configure a CD with Vercel/Netlify so that your public graph is automatically kept in sync without doing it manually, by @pengx17. Demo video here.

Before You Go

I am very interested in obtaining some feedback on the layout and content of my blog posts. If you have a second, could you please let me know in the comments below your preference on:

  1. You like the content as it is and enjoy that I extract what I consider to be the pertinent points of the workflows and plugins.
  2. It is a bit wordy and you would prefer less narrative and more links to posts / content.

As ever, thank you so much for taking the time to read the post and I hope that 2022 is an excellent year for you all.

6 thoughts on “1-Jan-22: Logseq 0.5.6, Logseq Android and iOS Mobile Apps, Workflows and Plugins”

  1. I like the contents so far. You can keep it as is. If you want to keep it short, leave out the long quotes (like a detailed post in the discourse forum), since you have link to the original source (maybe even easier to read, and have more context). I’m more interested in your take of the issue, and that I’m not missing out on interesting things happening in the discord/discourse forums.

  2. Hi Ed, I like the content as is, thanks for saving me going to each of the links unless I have further interest beyond your summary. Enjoying the screenshots as well.

Comments are closed.