12-Mar-22: Logseq 0.6.2 and 0.6.3, Using Logseq for Research, time tracking, GTD, new and updated plugins

So tomorrow looks like it is going to be the day that we finally make our way to see what the Expo is all about. With it being advertised constantly and people always talking about it, we thought we should make the effort to visit before it ends at the end of the month.

In other news, the Fifa Qatar World Cup tickets announcement went out – we came away with zilch. It was not like we just went for the opening and Final, we chose random games. Oh well, looks like will be watching it from the comfort of the sofa.

Now that the cushions have been plumped and we are sitting comfortably, here is this week’s Logseq Weekly post.


This week we have certainly been in for a treat. The devs have provided us with a couple of releases during the week which enhance and improve Logseq.


Some highlights:

  • Open links in search with keybinding(mod+o)
  • Shift-click a repo name to open it in new window
  • Support block-embed alias in org-mode
  • Remember right sidebar width after resizing
  • Shift-click a repo name to open it in new window
  • More natural electron context-menu
  • Add command to save graph to disk
  • Only run custom queries when not typing
  • Add develop instructions for Windows
  • Add a test runner command
  • Add timestamps for pages created from references and timestamps
  • Optimizing nested query rules for graph traversal
  • Persist widen mode state
  • Ignore logbook and default properties in unlinked reference
  • Support multiple file watchers for multiple windows
  • Collapsed state not persisted for blocks with properties
  • Change export to not depend on printing
  • Exit block edit mode when prompt
  • Can’t parse graphs because of links regular expressions
  • Set timestamp to correct editing block


Some highlights:

  • Flashcards random mode
  • Open file backups directory
  • Use query-dsl rules from advanced query
  • Syntax highlighting for nginx in docs
  • error while cycling todos
  • Refresh window causing file changes not synced to db
  • PDF toolbar covers top of scrollbar and page number bug
  • DSL query bugs
  • Return value of move block in plugin API
  • Only half of cards viewable
  • Collapse/expand in publishing

You can download the latest version, check here.

Logseq News / Events

  • This coming week, on the Wednesday 23 March at 3:00 PM, we have an exciting episode on How to Use Logseq for Research ft. Cara Antonaccio. ​Cara is a PhD candidate in the public health field and will look at covering how she uses Logseq (and related tools) to carry out her research. The talk with Ramses will cover the following:
    • What is Cara’s PKM story?
    • What are her current PKM use cases? •
    • What does her daily process and Journals structure look like?
    • ​How does she use Logseq to do research?
    • ​What other tools does she use besides Logseq? •
    • What are your top tips for researchers starting with Logseq?
  • Cannot wait to see what Cara has in store for us. To register please follow this link. A recording will be available after the session.
  • Update on Logseq Sync? @Ramses mentions: Yes, it’s currently in active development and we hope to start internal testing next month. The first step is simple sync, much like Github sync but with much better conflict resolving and much (non-tech) user friendly. The second step is to add real time collaboration, but this will take longer. However, Sync should already work much better than git
  • A very successful Intro to Making Logseq Plugins ft. @aryansawhney17 took place a week or so ago. Well done Aryan on taking us through what us quite a complex topic. Here is a copy of the video.

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

  • Edward Darrah is looking to hire a consultant to help me with transitioning to Logseq for both personal and business. If the person is also familiar with Obsidian, that would be an added plus. Feel free to direct message me or email at edward@darrah.io if you have any questions. Thanks! Do get in touch if this sounds like it could be something for you.
  • @OneStutteringMind posted a great couple of videos on Getting Things Done (GTD) including how to implement the GTD paradigm into your life, and how you might go about doing this in Logseq. Definitely worth a watch:
  • There is a handy new query feature in the nightly build – the ability to use any of these simple query rules, in an advanced query. Here is an example query . While the rules have the same names as the operators in simple queries, their arguments can be different. Examples of their arguments are at here.
  • How do you organize your notes to trigger new insights? @rroudt will show you the basics of networked thinking using the outlining tool @logseq at the Second Brain Summit. Sign up here for free: lu.ma/w4hmfp4d
  • @s0ren gives us a great insight into how they manage their PDF files. I basically use Zotero to keep all my references, attach the relevant PDFs to them, and then use those Zotero-linked PDFs as the basis for my highlighting in LT. I finally take more fleshed out, unified notes in a summary format using LT’s highlight view and new universal linking functionality the result is that i get succinct and clean notes in logseq on my readings – all linked to zotero using Logseq’s zotero plugin, making it a lot easier to find – and a much higher level of readability across different apps than if I just used Logseq’s PDF reader and block referencing capabilities the readability for me is key for future-proofing my notes as much as i’m able to and for interoperability across different apps.
  • @thomasgriffiths asks how to create contacts. Creating Contacts Hi all – curious as to successful workflows for creating/storing contacts. does anyone have a proven recommendation? I have simply been creating a page [[contact]] then tag #contact inline. I have been adding properties for metadata such as title::CEO email::CEO@company.com Phone:: 123,456 – not sure if this is a good use of properties or if simple child blocks would be better using tags such as #email #title etc…. any thoughts/opinions appreciated
  • @Nartaki and @omeganot discuss time tracking. I work on multiple projects at a time and run from meetings to meeting which can be on different project. Is there a way to calculate time on each project by the end of the day using Logseq. I take notes on all meetings using Logseq so I have the time stamp for each meeting? Personally for this, I use a combination of my calendar to know the meeting time for billing calculations as well as myhours.com for a simple time tracker. What would be nice is if I could take a link in LogSeq (either to another page, or a block or something) and put it into the time record in myhours.com (or wherever) so that if I clicked it I could open LogSeq, pull up a graph (if I have it) and go directly to that item.
  • Taking not on YouTube videos anyone? Hope this helps:
  • As a reminder for anyone thinking the same a @Keirnan, Wouldn’t you like if page links didn’t have the [[brackets]] when the block is not selected? A cleaner look. You can go to Go to settings\editor and disable ‘show bracket’.
  • Query Title-ing? Hey, I’m aware that with advanced queries you can assign a title. Is that also possible with simple queries? I don’t see myself using advanced queries anytime soon unless there will be a query builder. Not quite. You can add a simple query to the advanced query block and give it a title.{:title “something” :query (and (todo todo doing now) [[block]]) }
  • Some thoughts on perfection. Remember, just with starting you are halfway there.
  • logseq-table-resizer for custom.js / custom.css : adds ‘handles’ to resize columns width looking for advice on how to improve and optimize this (never used mutation observers before, it seems to add a lot of overhead ? how should I scope it / use it or replace it to be more efficient ?)
  • Is there a way to hide the card page, used in flashcards, in the graph- Now is shows all the connections, and it’s not really useful. For the time being, I do not think this is possible yet.

Logseq Feature Requests

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

  • Flashcards/SRS Improvements – Including, card random order in normal mode and preview mode, card review heatmap(plugin would be great if someone want to develop.), card suspension, setting daily card review limit, options to change keyboard shortcuts, timer for card review (automatic revealing of card also), revealing card line by line(or block by block) (use case : remembering poem or speech) Image Occlusion 2, Learning/Overview stats of card review
  • Simple Query title – I’m aware that with advanced queries you can assign a title. Is that also possible with simple queries? The default query code that shows up as the title in simple queries just looks plain ugly and worsens readability. I don’t see myself using advanced queries anytime soon unless there will be a query builder. Request: Please add Set Title functionality to simple queries.
  • Import image on excalidraw – I try to use shortcut number 9 and import PNG. But unfortunately, have an error message. I hope excalidraw in Logseq can import any image to make the annotation in front on the image.
  • Quick add on Mobile App – It would be great if the mobile app had this same option as the Anki and Ticktock app have. With the user deciding which page these quick adds would go to, like daily journal or an Inbox page.

Logseq Plugins

  • logseq-sliders-plugin – This simple plugin inserts a slider into your note to serve as a great visualisation tool! Type /Insert slider and that’s it! In order to customise the range of the slider, simply add a value to the end of the block where in the example below, 100 is the maximum range (default: 10).
  • Ordered Lists– Ordered lists, flat or nested, multiple formats ordered lists.
  • VIM Editor – New! Logseq VIM Editor v0.0.1 has been released! It’s a vim editor for editing blocks, the trigger is mod+shift+e
  • Reference Styles – Logseq Reference Styles is a new plugin to make Logseq beautiful. It lets you configure emoji and colors for block references that match patterns of your choice.
  • Random Note – Has been released (excellent fist plugin Alex. It also includes a small update – now supports opening a random page with keybindings.
  • VIM shortcuts – has been updated to 0.1.2. Mainly related to blocks sorting and reverse sorting.
  • Logtools – added a gallery mode (tag the parent block with #.v-gallery and put image links in separate children blocks) – added the like/dislike css (it replaces children bullets with + or - for visual pros/cons lists, plays nice with the #.v-kanban tag) – added #.v-self-border ; #.v-border-child ; #.v-self-border-child to add borders to blocks – fixed the priority matrix and kanban for latest logseq check out the templates in the github to get started
  • Time tracking in Logseq? Check this out

Many thanks as always for reading this latest edition of Logseq Weekly.