4-June-22 – Logseq 0.7.1, Town Hall Meeting, Using Templates, Workflows, New Feature Requests and Plugins.

Firstly, my apologies for slacking over the past few weeks. I was travelling and managed to catch the dreaded Covid bug which made it all the more fun. Glad to say after three days of not really feeling myself the bug passed and I am getting back on my toes. Luckily I seem to have caught the Covid light version. On the positive side, it is only 204 days to Christmas.

Anyway, my sob story aside, lets get down to business as we have a lot to cover in this slightly longer than usual post.


Although there have been quite a few releases in the past weeks, below is the latest version (0.7.1):

  • Features
    • Copy & Paste with rich-text formats, Use Cmd+shift+v or Ctrl+shift+v for copying/pasting without formatting
    • Onboarding Quick tour, more friendly UI guide
  • Enhancement
    • Fully translated in Portuguese (BR) and Italian
    • Added Italian tutorial and dummy notes
    • Slash command UX
    • Improved float numbers formatting for calculator
    • Use separate export.css instead of custom.css for export
    • Improve record timer implementation
    • Refine App menu, add About and Document menu entry
    • Disable left menu button when pdf view active
  • User Contributions
    • Fix theme switching bugs – Yue Yang
    • Italian tutorial and dummy notes – ntotao
    • Calendar icon in toolbar not rearranging(for mobile devices) – sawhney17
    • Fully translated in Portuguese (BR) and Italian – Taylor Hoffmann
    • Improved float numbers formatting for calculator- Jonas Diemer
    • Use separate export.css instead of custom.css for export – Alex]
    • Update Turkish translation – queeup
  • Fixed issues
    • Save mode when switching themes
    • Block can’t be deleted if backspace at the block beginning
    • Page title position when in editing mode
    • Startup runtime error under some Windows platforms

Remember you can download the latest version of Logseq from here.

Logseq News / Events

  • On Wednesday, June 8th 16:00 BST, Logseq is hosting a public town hall meeting. Come along with any questions and suggestions so that the Logseq team can make this a learning event for everyone. Logseq want to hear how they can improve both the product and the community processes around it. Do you think that asking for new plugins or reporting bugs is a hassle? Logseq want to hear from you how to make your life easier! Event will take place in the Discord Auditorium.

  • Missed the recent Workflow Wednesday “How to Write a Curated Newsletter with Logseq?” Recording is available here. In this episode, Ramses shows how he use Logseq to write the weekly Logseq newsletter. From collecting useful resources to publishing a 1,000-word piece, in this session he showed every step of the process. ​The core of Ramses’ processes are templates and queries. If you’ve been wondering how to run processes using Logseq queries, this session will be a great inspiration. The following steps are demoed:
    • ​Collecting resources (videos, articles, scripts), ​
    • Organizing blocks and branches using templates
    • Retrieving blocks and branches uses queries
    • Writing long-form in Logseq
    • Publishing from Logseq to Ghost
  • A reminded that there is an Official Logseq Newsletter. You can sign up here to get a weekly dose of good news and inspiration related to Logseq.
  • Logseq want to hear of your workflows to help them craft better educational materials and make features that supercharge your workflows.
  • Update on Logseq Sync (hopefully it will be called LogSync). “We’re building it right now! We’ll probably be ready for closed beta early summer, and we’ll most likely start with our backers and sponsors as a test group. If you have knowledge with testing software, we’re all ears!”

Logseq Mobile

To access the mobile apps, please use the respective link for your OS below.

Logseq iOS app 0.7.1 is out. You can download or update it on App Store.

  • Features
    • Added gestures support on block. Check out https://www.loom.com/share/2dddfc5983294afa90011a0d3219fe9c
    • Allowed editing block while recording audio. Check out https://www.loom.com/share/1b4b9b785676448d8eaa63aa2815ce60
    • Enabled custom.js
  • Enhancement
    • Big UI Changes
    • Changed indent and outdent icons in toolbar
    • Responsive audio component width
  • Bugfixes
    • Footer floating issue on Zoom Display mode
    • Recorded audio embed fails in breadcrumb page
    • Calendar icon in toolbar not rearranging
    • Block can’t be deleted or merged if backspace at the block beginning
    • Auto suggestion not working when backspace
    • iPad left and right sidebar can’t scroll to bottom when keyboard shows

Logseq Workflows

Interested in “Logseq and the Rise of the Integrated Thinking Environment”, then this is a must read from the great Dario. In this great article we are taught of the importance of having a thinking environment and the impact on creativity of having scattered data. It concludes by showing how Logseq can help you become more creative using outlines and links.

@Stephen opens up a whole new world for us by using Python inside a Logseq plugin written in Javascript, and the outcome could be very powerful indeed. The video showcases nlp to summarise long text into a limited set of bullets. More info available here.

I think the point made by Pvazevedo will resonate with a number of readers: “What hinders me the most besides perfectionism that makes me waste several minutes or hours on ridiculous things is also the organization. Organization and how to deal with unforeseen tasks. These are the two things that mess up the most and distance me from being able to maintain a certain frequency doing this as a college student.”

@doulos05, provided a fantastic response:

Well, a couple things here.

  1. Of course it’s hard if you’re just starting. You’re just starting, it isn’t habitual yet. You have to work with any system for a bit before it becomes automatic.
  2. The point is that your notes are not perfect. Notes aren’t meant to be perfect. What would perfect notes look like? Every time you look at them, the definition for perfect is going to change.

The goal of note taking systems is not to get perfect notes, but to get useful notes. Useful notes are notes which can be searched easily, read easily, and linked together easily.

One thing I found on Tiago Forte’s page is the concept of closing every note a little bit better than it was when you opened it. So my first notes on a concept are an absolute mess, generally the only thing I try to make sure I do is link out to existing topics. Everything else is basically stream of consciousness. Then, the next time I open those notes, I go through and organize them so the obvious common points are grouped into their own headers, maybe linking out to other concepts I missed the first time. The next time, I might tighten the language around a specific point. The next time, I might pull a whole heading out into its own note and leave a backlink.

The benefits are threefold: 1) I never don’t capture something because I’m worried I won’t have time to clean up the notes. Everything goes in the system, regardless of how messy it ends up being. 2) The parts of my system which I actually need end up being the easiest to work with because they’re the places I’ve spent the most time. 3) Every time I return to a note, I have to actually think about that note, reinforcing my recall of those ideas because I’ve engaged with them.

Interested in learning how to share Logseq pages. @Ben provides the perfect walkthrough on how to achieve it. In summary: “I have a node server always running that does a few things in the house. Masumi and I both have our Logseq directory in Dropbox, and they are both available via the node server. The server watches and syncs changes between them, so we’re not technically sharing pages… we’re just syncing them really fast.

Question on how people handle todos from the journal pages. So if I put a task like “TODO #errands Pick up dry cleaning” in todays journal and I then go to my [[errands]] page I usually cut it from the journal reference and paste it back to the top of the page. But now I’m thinking it might make more sense “Copy Block ref” so I can see when I look later when that task came up. But then again that starts to get messy with lots of tasks and time. Thoughts?

Response: For personal stuff I just work in backlinks and don’t see the need to copy/move anything to the tag page (a task may have more than one tag anyway). but if the tag is like a project and I need to organize the tasks into some structure, then I do copy ref for the exact reason you suggested. and if the structure you desire to have in the project page are simple enough to be summarized as “breaking tasks into sub-groups based on metadata (properties drawer) or other tags a task has” , then I will just use a few queries on that page instead of manually linking because ((ref)) makes things messy.

@Schwalb asks: Is there any way to create visible subfolders? I love Logseq workflow, how it handles TODOs and journaling. Graph view isn’t perfect, but that is ore visual than practical. But folders? I have a bunch of stuff that needs structure and MOCs are not enough (plus they add another level of maintenance). Do I really have to use Obsidian for that, or is there any way to have proper structure within the Logseq? Hierarchical notes are not perfect either – when I’m referring to “Note A” I don’t want to link to “Example/Note A”.

Responses: @Sawhney One suggestion I’d recommend is using aliases to link to the references but what you’re asking isn’t quite there. https://aryansawhney.com/pages/the-ultimate-guide-to-aliases-in-logseq/

Yurii Piskun – use folder:: Folder-one, folder:: Folder-two…. then create page for each, like “Folder-one” with query {{query (page-property folder “Folder-one”)}} and add them to Favorites

Great template showcase by Cara:

Interesting point by Muhammad: Logseq lets the notefiles reside in a tool agnostic state. A commendable feature. My only concern is on note handling capacity. I’ve been keeping notes in markdown for 6 years now. I hope the capacity limits does not constrain my note-taking habits. Concern of many but the devs have long term performance as a priority.

@itsgregormay: I am a bit confused right now. Can someone explain me, what the best approach would be for using 2 LogSeq Vaults on 3 Computers (2x Mac, 1x Windows) and one Android Phone? Google Drive does not work properly i suppose, but OneDrive and Dropbox do not sound better?

Response: @Cannibalox: Syncthing is what I use (multiple vaults over 3 windows pc, 1 synology nas, 1 android phone, 1 tablet). or you can also wait for the devs to release the official logseq sync service

@Acacius asks: Hey everyone I’ve been using Logseq for about 4 months now, and I’ve decided that it’s time to step up my game up in regards to finding better information capturing workflows. Specifically – look at some workflows that truly emphasize on Zettelkasten methodology and being able to easily retrieve information that’s important to me in the times I need to retrieve it.

Alex, as always steps up with a perfect response: This is my wip workflow: https://qwxlea.github.io/#/page/wf%2Fnote%20taking%20workflow it looks like this:

Staying with Alex, he shows us a brilliant image on his note taking process / flow:

An interesting article on switching from Roam to Logseq. Unfortunately it is undated but it shows a screenshot from mid-May 2022 so quite recent. Just keep in mind (as concluded in the article) “Whether you decide to migrate from Roam to Logseq or stick with using Roam, it is not the tool you use but how you use it to shape your thinking”

Zotero anyone? Since there’s been a lot a talk recently about Zotero referencing in Logseq, @necessaryillusions42 shares their current method to solve this till the Zotero (version 6) integration is again solved in Logseq.

First, let me preface what this workflow accomplishes for the impatient:

  • Zotero entries importer
  • Customizable properties template
  • Annotations import
  • Updating all imported entries
  • Preserve manual edits done to existing entries when updating all entries
  • Leverage colour highlights custom tagging or automatic task creation

Secondly, I could only achieve this by using a plugin for Obsidian (sadly). Nevertheless, since I installed Obsidian with Flatpak I removed its permissions for network access. The plugin used is the following: https://github.com/stefanopagliari/bibnotes

Check out the link for the steps of configuring the plugin to work nicely with Logseq.

Interested in creating a block alias in Logseq? @Josh provides us this video:

A great question from a new Logseq user:

I’ve been using Obsidian as my PKM (study, meeting notes, etc) and Workflowy as my outliner for tasks and projects. I’m getting a bit fed up with Workflowy because of the glacial speed of development… new features appear in apps like Obsidian and Logseq very frequently, whilst with Workflowy nothing happens for like 6 months. Also it appeals to me to integrate my outlining and PKM… why have two systems when you can have one?

I’ve had a “play” with Logseq so know it is based on outlining and markdown files with links. Which brings me to my question… do all files in logseq essentially have to be outlines/bullet-points? In Obsidian you can have a markdown file that is all bullet-points and hierarchy, or it can just be regular text with headings, or a mixture of both. [Sorry if this is a “dumb question”].

Templates: @doulos05 helps us out:

  • Step 1: on a separate page (I call mine “Templates”) build out what you want to see on each daily page under a top level block that I like to call “daily skeleton”
  • Step 2: right click the circle in front of the daily skeleton block and select Make Template (call it daily skeleton). Switch off Include parent.
  • Step 3: click the 3 dots in the top-right corner, select settings, and edit your config.edn file
  • Step 4: look for :default templates around line 20 if you’ve made no changes and replace the “” inside the {} next to journal with "daily skeleton

For Japanese users of Logseq, be sure to check this post out by the prolific and ever insightful Sangmin:

To finish this section off, I leave you with a quality video from Dario.

Logseq Feature Requests

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

  • More flexibility in page layout (e.g. linked references on top) – This is perhaps my biggest painpoint with Logseq as of now. I’ll start by explaining what I mean by “flexibility in page layout”. So a logseq page can have these components (as shown in the following screenshot): Title, Page properties (e.g. alias), Page content, Linked references, Hierarchy, Unlinked references
  • Url Scheme (deep link) on Mobile platform is desperately wanted – I’m very grateful that the URL scheme (deep link) feature has been implemented on the desktop platform, yet I’ve been waiting for it to be added to the mobile platform (for me, iOS). In a sense, I believe the URL scheme would be more widely used on a phone. For example, a URL scheme can build meaningful links between apps like Trello or Things or Reminders and Logseq to complement its very poor notification and visualization system. I’m wondering if the mobile URL scheme feature is on the roadmap and how prior it is? Many thanks. Reponse: Should be available soon.
  • Zotero enhancement by including citations, references and related papers – Further enhancing the capability of the Zotero integration in LogSeq would be crucial, at least for the academic use of LogSeq. The current version of the ZoteroRoam plugin of Roam Research has a brilliant feature. Each imported Zotero item has an on-page menu. The menu shows the records of the item in scite.ai, Connected papers, Semantic Scholar, Google Scholar, and also lists the references, citing papers, and related items in the Zotero library.
  • Separate query result sorting logic from result transform – I have a custom query for showing tasks sorted by priority, for example, but when I provide the :result-transform function I lose the beautiful and useful grouping + breadcrumbs added by the default result transformation. I would love to have the sorting function separated from :result-transform, so that I can sort the results of my query without losing the default formatting that I get from Logseq.
  • Add blocks on top of page not bottom option in pdf-annotating – is there any option to switch for add blocks on top of page and not bottom of page? this is important choice for long-pages and especially for long-pages on right panel because of recurring very annoying option on bottom of page to show more. in case of me, I’m tired of that in the middle of book-pdf annotating.

And my favourite(s):

Logseq Plugins

  • If you are interested in seeing all of the Logseq Plugins available in the Marketplace with a brief demo, please do check out this link. You will find a brief description of the plugin, the creator, a link to GitHub and creator profile, where possible a demo video / image and a last updated column.
  • logseq-quick-add-plugin – Use custom keyboard shortcuts to: Add a parent block to the end of the current page, Add a sibling block before or after the current block, Add a child block to the current block (only works if the current block has 1+ child blocks), Duplicate one block or multiple blocks
  • logseq-web-parser – A simple plugin to parse the contents of a website and insert it under a block
  • logseq-classy – Facilitates otherwise impossible custom stylesheets by applying classes to blocks identified in custom queries. A great complement to Style Carousel.
  • Update to Logseq Calendars Plugin – Fixed a bug with recurring events in google calendar – You can now set as many calendars as you want via JSON if you desire
  • Markmap support Logseq admonitions syntax now
  • @logseq-helium-plugin (v.2.0.0) NEW: – keyboard shortcuts to play/pause and skip forward/backward in videos (currently only work w/ youtube and local videos) – local videos can be resized link. Demo Video:

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