15-Jan-22: Logseq 0.5.8, Onboarding and Task videos, Feature Requests, Daily Note vs Page

This past week the Devs have worked hard to provide us with a new release and we have a couple of great videos which showcase a getting started / onboarding in Logseq and a task management overview. To also cheer things up slightly after Blue Monday, we had the UK Government providing us with some thought provoking parties, or should that be “meetings” and the Djokovic Australian visa saga. You really could not make this stuff up.

All in all, I would definitely say it was an entertaining week. I hope you also enjoy this weeks rendition of LogseqWeekly.



  • Apply text normalization to the whole app
    • NOTE: This is a BREAKING CHANGE, requires re-indexing
  • Reload custom.css when file changed
  • DWIM on paste in source block or admonition
  • Add CodeMirror options support
  • Nested and query issues and full-text search in nested queries
  • Fix some UI misplacement, calc result offset, position of new updates tip
  • Multi window check while re-indexing
  • Graph view hang due to duplicated node/edge
  • Separate references/queries collapse state from DB
  • Block expand/collapse not working under some scenario
  • Sometimes a page’s name is altered into lower letters
  • Right sidebar is not being cleared upon switching graphs
  • Clicking raw HTML links loads target URL in the desktop app
  • Remove orphaned Pages will delete namespace pages
  • Youtube timestamp does not work

You can download the latest version from here.

Logseq News / Events

  • @Ramses successfully carried out the Introduction to Networked Thinking Using Logseq. The onboarding sessions looked at:
    • 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!
  • Gabriel joined as a software engineer. “Hi y’all! My name is Gabriel Horner and I’m joining this week as a software engineer at Logseq. I’ve been using outliners for almost two decades so needless to say I’m excited! For fun, I like to organize my knowledge with linked data and schema.org, https://gist.github.com/cldwalker/442b412ba9e1d0fae06772d503b0a298. And yes, I like to Clojure”. Welcome Gabriel.

Logseq Mobile

  • Android (Download the latest .apk)
    • The Android version of the app seems to be updated together with the Desktop version. As it is not currently possible to update automatically, be sure to check GitHub for the latest version of the .apk to download.
  • iOS – Fill in this from to get access to TestFlight.

Logseq Workflows

  • @Sawhney presents us with a very good guide on task management in Logseq. The video is an introduction to task management with Logseq. Sawhney considers three fundamental stages of any task management system; input, resurfacing and the physical act of checking things off. Great video, buddy.
  • Do also check out @LarryK’s video on task management here. Not a specific Logseq video, but has great insight and content.
  • @Sawhney also kindly reminds us of how powerful the query table function in Logseq can be. Here is a brief image of its capabilities
  • A few users (new and old) seem to be having issues with Logseq only showing a white screen or the “Open” button in the top right hand corner not being visible when first opening Logseq. While the Devs are looking into fixing these, the temporary solution is
    • Windows
      • Close Logseq
      • Navigate to C:\Users\YOUR USER\.logseq in Windows explorer
      • Delete the Graph directory
      • Open Logseq
    • Apple / MacOS
      • Close Logseq
      • In the Terminal type: rm -r .logseq/graphs
      • Reopen Logseq
  • @Murf (ex-Roam and current Obsidian user) gives us some very good insight into Linked References and who Logseq could be improved to make these even more useful:
    • 1) Sort Linked References. Even if simply alphabetically would be nice to start. But preferably option to also sort by date created or modified. Especially just trying to sort my Daily Note Pages in order in linked references. Roam never implemented this either but Vargas’ extension filled the gap.
    • 2) Filtering of linked references. If I go to a [[client page]] or a [[project page]] I have tons of linked reference entries and TONS of related [[pages]]. Talking 50… 100… sometimes more unique page filter options. But there is no search/input box to filter down the list. I have to hunt & peck to try & find what I want which is almost impossible.
    • 3) Filtering operators. In Logseq the filtering is like an “OR” clause. If I filter [[Page A]] then it still leaves all other filter options available. If I then add [[page B]] as a filter, it now ADDs all matches to [[page B]] so I actually get more results. So now results are all blocks from linked references that have [[page A]] OR [[page B]]. My expectation in a filter would be that it continues to filter down more specific so that I would only see blocks in the linked references that match both [[page A]] AND [[page b]].
  • Aliases. Just as a reminder, to create an Alias of a page, you just need to add alias:: name.
    • This can be useful to set an acronym to a page. You can also use it to give a namespace a shorter name.
  • Unsure of where to start when taking notes? This is a common (and recurring) question about whether to start on a dedicated page of the Daily notes page. I agree with the comment made by @Red Castle “just dumping everything in Journals (if you don’t know what to do with it) makes sense, because not only do you have like a solid “One Place” where you learnt what you did today, you will always have an easy access to “Okay, so what were the things I needed to attend to”, and just go down your daily history and when you find it – figure out what to do with it then afterwards”
  • Logseq Sync – when this this be available? @Ramses provides us with an update:
    • We’ll update the community whenever we have more information, but it can easily take some more months as we’re figuring out some things.
    • There are still some performance issues to squash for local files before we can think about syncing. It’s high on our list, though. We have need for a good sync services ourselves as we use Logseq daily to collaborate with 9 people.
  • Wondering where your completed to-dos go? They remain in the blocks you originally wrote the task in. To get them all in one screen, use a query
    • {{{query (todo done)}}}
  • @nikkou_ru asks about how to get started with Logseq.
    • My approach is building an interconnected network of ideas and thoughts that come into my head randomly and that I pick up from others, across my private life, professional areas, skill development and understanding of the world.
    • If something feels like pertaining to a temporary work project, I put it to Trello. If it’s is a piece of specialized knowledge, I put it to Anki. If it feels like a piece of information that needs to be searchable but is not an idea and can not be connected to other ideas, I put it into a single plaintext feed outside of Logseq. Everything else goes into Logseq.
    • Logseq seems infinitely flexible but does this setup make sense to you and if it’s similar to whatever you use, what are the differences?
    • How do you handle notes that you don’t need anymore (eg because they are replaced by others)? My first instinct is to find and delete them occasionally but I want to reduce maintenance as much as possible. If you just leave them in the graph (linked or as orphans), doesn’t it get messy after a while? Do you know what notes are useful and what notes are not using indices?
    • More generally, any tips on constructing the network of notes in such a way that it wouldn’t require much maintenance?
    • If you have roughly the same approach to notetaking, how atomic your notes are and why? I’ve read a bit about Zettelkasten but the atomization didn’t click for me so far. My note titles currently are referring to concepts, questions or topics and their exploration inside the note can be pretty long and is definitely not atomic in the slightest.
  • @qwxlea responded with a great answer:
    • The way I read your questions is that you organise you data top-down: you arrange it in preconceived contexts & apps. Logseq works the other way around (by default, you can obviously do whatever you want) bottom-up:
      • Drop everything in your daily journal. Use (plenty of) links, tags, cards, and TODOs to make it simple to “collect” information that should be together, and find it in the future (backlinks)
      • If some note in your daily journal gets too big, upgrade it to it’s own page.
      • Old notes will just rest on some old journal page, you might never read them again, or you might unexpectedly use it in a new context.
      • The zettelkasten-part of your notes will always need maintenance, that’s not a bug, it’s by design. But as long as your notes are atomic and well-linked (and not over-engineered), you won’t have to “repair” you notes ever
      • An atomic note is nothing special: it’s just a short(ish) note about one subject, instead of a large note with many subjects.

Logseq Feature Requests

I have added a new section to LogseqWeekly, that I hope you find useful. Each week, I will extract what I consider to the most pertinent Feature Requests being made (in no particular order). This is of course subjective to my own thoughts, so to balance it out, I will also include the top 3 voted requests. You can check out the full list of FRs here.

Option to Open PDF in Directory4When viewing a PDF if would be great to have an easy way to locate it so that can be easily shared or printed without having to search for it.
Deep Linking or URL Scheme35 Allow linking to Logseq pages from outside the app
Basic UI Settings e.g. Font Size13Ability to easily change the font, font size etc. without having to tweak the css. Something nice and simple.
View as numbered List30View the outline as an ordered list. I for 1 am a sucker for sometimes seeing a nice numbered list. You can achieve this by adding 1., 2. etc. but I was something natively built in allowing me to change a list to a numbered list etc.
Support epub format ebooks34Think the title says it all.
PDF search28Add search functionality to Logseq PDF annotator.
Top Requests
Vim-mode Powerful Shortcuts107Vim-Mode shortcuts
Add support for customisable TODO keywords49Support user customisable keywords for TODO stages and the sequence in which they cycle. It should be noted this is marked as “on roadmap”.
Filters for note body, not just backlinks49Add persistent filters to the blocks in the main note body, not just the backlinks. For instance, marking a number of blocks #ignore should hide them with a filter
  • In the future, I will look to include the top voted requests for the week because if not I suspect the Top Requests of all time will be frequently repeated. Just need to work out how to do this in Discourse.
  • I may even look to throw in a curveball and have a couple of “random” feature requests included to mix things up a little.

Many thanks as always for reading and happy end to the weekend.

1 thought on “15-Jan-22: Logseq 0.5.8, Onboarding and Task videos, Feature Requests, Daily Note vs Page”

  1. I like to add for the starters: prefer creating pages around concepts than dumping related content through different daily pages. Concepts pages can then be revised, modified and upgraded as time passes. When you need to use some or all the content of a concept page in a daily page, use block reference.
    This way your information will be more organized as the years passes.

Comments are closed.