26-Feb-22: Logseq Tasks, Tags and Links, Logseq as a CRM, New Plugins

This week, there is not much to say apart from that my thoughts and prayers go out to everyone and anyone who is caught up in the conflicts (not only in Ukraine but in other parts of the world too) that are unfolding before our eyes.

We certainly live is crazy times and who knows what is in store for us next.


We have been so accustomed to weekly (or more frequent) releases that when there is no new release it feels like we are missing out. However, I prefer a slightly slower release schedule but with more fixes and more testing being done in advance of the releases to ensure that there are no major issues or breaking bugs being introduced. Data integrity is critical, so anything that can be done to ensure this, should be top of the agenda.

Rest assured though that the devs are hard at work on a number of fronts to ensure we are given a tool that helps us in our day to day lives.

  • To download the latest version, check here.

Logseq News / Events

  • If you are using multiple Logseq Windows, please be aware that there is a bug which can lead to data loss. The devs are aware of it and are implementing a fix. It is recommended that for the time being, avoid using the multiple windows feature.
  • The Logseq team expect to start internal testing of the sync service in the next few days, and a few weeks later it should launch in beta. The devs are still deciding whether it will be an open or closed beta, but more info will follow when it’s about to ship.
  • Unfortunately due to unforeseen circumstances, the “How to Use Logseq for Research ft. Cara Antonaccio“, had to be postponed. As soon as a new date is organised, I will be publish it here and on Twitter.
  • The updated documentation is now live (thanks @Ramses). Check it out here and please do feel free to get in touch with the team about how this can be amended / improved / any areas where you want the documentation to go into more detail etc..
  • I had a chat with @Jakob (product designer) and all I can say is that I am very excited about what he is building and the ideas he has to take Logseq to the next level. Not to give anything away, but lots of Quality of Life improvements should be with us in due course.

Logseq Mobile

To access the mobile apps, please the the respective link for your OS below. 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.

Logseq Workflows

  • @Gianthobbit asks Having a hard time wrapping my head around the best workflow for tasks that you don’t finish all at once. I like to use daily notes for everything. Sometimes though a task requires more than one day. That would my partial notes (in this case partially finished research) is on a previous day. That creates a lot of issues since I really just want to pick up where I left off vs migrating things to the newest day and block reference – very messy! I see 3 possible solutions 1. Block reference so that all new notes are always tied to the day they were created, ie embrace the friction of the problem outlined above (this feels like way too much work) 2. Create a page to house all working notes and page reference it on the daily page, maybe with a brief summary (feels overkill to create a page for a task) 3. Block reference the task, take all notes on the original task, on the daily page (where reference lives) leave brief summary of work you did. A tricky conundrum indeed, with the potentially most useful option is to create a DOING task.
  • Looking to get the perfect workflow integrated before you start? @s0ren gives their take: “I think the utility of Logseq becomes more apparent when you’ve been taking consistent notes on topics, papers, and using backlinks as you note-take. You end up building a repository of information that you can draw on quite intuitively when you need to take notes on a specific topic/question“. Completely agree, get started by writing and let it build from there.
  • Staying with @s0ren, they provide a very useful and concise explanation of some key terminology in Logseq:
    • aliasing (at the beginning of a page/block just type alias:: then a list of terms/phrases separated by commas, e.g. alias:: attribute, synonym one, look at this another synonym
    • zotero plugin (godsend if you have lots of papers – logseq also automatically incorporates any pdfs you’ve linked to your zotero library)
    • sethyuan’s TOC generator plugin (needs slight customisation but payoff’s good) – block references (a more fine-grained version of backlinks that use (()) referring individual blocks)
    • block embeds (quite useful once you get the hang of storing. central/core information in backlinked [[]] pages – you can use block embeds to feature core definitions in different pages without re-typing information. it also creates another linked reference for the main concept listed in the backlink [[]])
  • @Russ asksI have started using Logseq to run a daily log (journal) of my work efforts and I create TODOs for tasks I need to do or tasks owed to me (someone else is doing the work and needs to provide their work to me). I also want to be able to track these TODOs by other values. I am open to using anything – tags, properties, the “tag:: [[tag]]” combination, to whatever solves this challenge for me – and open to a suggested indentation strategy, or anything else that makes this work. As I envision it, this would enable to me to meet with a coworker and quickly find work I owe them and work they owe me. I would also be able to see TODOs by Project, or by Effort (a subgroup of a project), by Priority, or whether the TODO is something I would want to consider reporting to management (milestones). Ideally, I’d be able to quickly find combinations of these things – TODOS that are not done, by priority, for a specific project, or TODOs that were done within the past 7 days along with those that haven’t been done which I owe to a coworker or that they owe me. Kind of like a fancy filter, but since that isn’t a thing yet, I’m comfortable tweaking queries to accomplish my needs – but I’m not having success writing these queries myself. To complicate things, I’d like to be able to have multiple values for a single “property” in this setup – I might have two (or more) people I need to inform when I complete a substantial effort or milestone, or more than one person who owes me a task that I might want to mention as I meet with just one of the people in that group (and properties doesn’t seem to support multiple values for the same property, except for the “tags::” property; maybe Tags can do it?). I’m just totally lost and I’ve built seven different databases trying to solve this – it’s driving my crazy! Check out the Discord for possible solutions if you also face this problem.
  • @ Ashish comments “PDF management has also become a critical part of my workflow. Logseq is the best so far, only missing searching within the pdf“. To get started with the inbuilt PDF annotation tool, just drag and drop a PDF file into Logseq and start annotating.
  • @Nhan provides us with “so how I set up my Logseq x Zotero is to set everything to the Logseq assets folder, and in the pdf annotation page (the hls page) in Logseq I delete the 1st block that has the absolute path for the pdf file. Without the absolute path in the pdf annotation page (the hls page), Logseq will default to look for the pdf in the asset folder. I don’t use Mac or another PC, but I think my solution will solve this issue.” Very useful tip.
  • Point on #link and [[link]] – @gestaltist comments “Personally, I feel that creating things that function almost the same but are subtly different is bad design. The vast majority of users of anything doesn’t go very deep and they expect consistent behavior from the thing they use. The kind of difference between inline tags and the tag property you describe is basically a trap. You intuitively think things should work a certain way and then they don’t, and you have to invest in a PhD in the tool to PrOpErLy use it. For me, the subtle differences between how #link and [[link]] behaves are already a source of friction.” What are your thoughts on this?
  • @Andrea asks I’m looking for some help implementing the CRM structure described in this article: https://jakobgreenfeld.com/stay-in-touch and I’m looking for suggestion in how to implement it in Logseq. More precisely, a contact would have its own page and a tag (e.g. #[[Every two weeks]]) and I would reference it from journal pages. How would one build a query, to fetch all pages with the tag #[[Every two weeks]] that have not been referenced in the past two weeks? @Hulbazizi may have the solution for us:

Logseq Feature Requests

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

  • Better docs for plugin api – While there is technically a set of api docs 2, there is nothing explaining the purpose and proper use of the apis or the mentality behind the api’s design. While I greatly appreciate that such a fabulous tool as Logseq is free and open source, except for the api docs and Plugins 101 2 its extensibility is for all intents and purposes undocumented. It whets the appetite but it’s basically the first 2 chapters of a 10 chapter book. Rather it requires one to infer the design (the other 8 chapters) by reverse engineering existing plugins and the sample plugins.
  • Hierarchy in the Graph view – I wanted to suggest adding a bit more hierarchy in the graph view. I mean that if for example, I am learning ‘Japanese’, it would be great if there is a big circle that has inside other topics belonging to it such as grammar, vocabulary, etc. And if you zoom in, more details about what is inside grammar and vocabulary appear. So, it is a bit more organized.
  • Ability to edit Logbook times – I accidentally left one of my DOING on overnight. If you hover over the time, you can see the timestamps in the logbook, but currently there is no way to edit the time.
  • Open in sidebar on middle click – I’d like to be able to middle-click on the things that normally react to a shift-click action and open in the sidebar.

Logseq Plugins

  • Music Notation by @benjaffe introduces music to our Logseq. Shame I cannot read music and have no sense in taste but this does look pretty cool.
  • Diagrams as Code by @npgrosser. A plugin that lets us create diagrams from textual representation (aka ‘Diagrams as Code’) within Logseq.
  • Style Carousel by @mlanza. This plugin is designed to provide one or more buttons which cycle through predefined styles. By default it is preconfigured with a button providing the following behavior: Toggles the visibility of completed and canceled to-dos.
  • Logseq Anki Sync by @Lightink updated to v1.2.0. This fixes some of the issues with the new renderer introduces in v1.0.0..
  • Calendars Plugin by @Sawhney has been updated to v2.0.0. It now uses the new beautiful native settings GUI in logseq released in version 0.6.0
  • Periodic Notes by @brendonscript. I just wanted to let you guys know that I have released a very early version of my version of Periodic Notes for Logseq. This adds support for weekly, monthly, and yearly notes. This is currently very early stages but I would love any suggestions, or bug reports

Many thanks for reading this week’s LogseqWeekly episode.