22-Jan-22: Logseq 0.5.9, Office Hours, Shortcuts, Tasks, University Notes, Snipd, Plugins

So, over the past few weeks, it may appear that LogseqWeekly was having an identity crisis or some sort of wardrobe malfunction as I was playing around with the structure and format. I now (think) I am set on one so hopefully no more messing about and we can get down to business.



  • Refactored long page loading logic with lazy loading
  • Removing nil orphans in All pages
  • Some style enhancements to block-control
  • UI position of plugin readme page
  • Filename encoding and special chars
  • Missing padding in marker markup
  • Strategy of scrolling within the left sidebar
  • Misused ctrl and cmd in settings
  • Open links of external files with the default app
  • Only show “Add to dictionary” when misspelling
  • App stuck with loading caused by wrong graph cache
  • Not showing an open button, cannot open graph
  • Cursor location when clicking start of a second line
  • Flashcards num not update while switching graphs
  • Enhancement of marketplace
  • Notify when journals date format changes
  • Allow edit markup files with code editor
  • Enhance full-text search index
  • Reorder auto-complete items of pop-up
  • Enhancement of development process

As always, you can download the latest version from here.

Logseq News / Events

  • @Ramses has organised an Office Hours event for Thursday, January 27th. ​​​​This is a Q&A session, meaning that you bring your challenges and I show you some ways of turning it into a Logseq workflow. We’ll look at use cases for manual and automated workflows (using templates and plugins).​​​Please answer the questions as completely as possible when registering. The contents of this session will be answering the top challenges you have. Be sure to register for what sounds like a great event here.
  • Integration with the @snipd_app podcast app. Snipd uses AI to enable you to capture noteworthy moments from podcasts in 1 click—including transcripts! And now you can export your Snipds to Logseq. To get started:
  1. Download the Snipd app for iOS & Android at https://www.snipd.com/
  2. Create your highlights
  3. Go to “Account” –> “Export & sync” –> “Logseq”

Logseq Mobile

Just as a reminder, to access the mobile apps, please the the respective link for your OS below. Also, 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

  • @Danzu presents us with a wonderful mind maps about some key shortcuts in Logseq. This is a really helpful cheatsheet for anyone wanting to drop the reliance on the mouse.
  • Danzu also wows us with another mind map on “Starting to use @logseq for task management! Here is what you need to know. One shortcut and couple of commands”
  • Ever wanted to have the right bar show your pages horizontally instead of vertically like the below:

Through the power of CSS (and @Jimmy, thank you) this is possible. Just copy and paste the below in your custom.css file and voila.

/* vertical style of sidebar */
.sidebar-item.content.color-level.px-4.shadow-lg {
    min-width: 33vw;
    overflow-y: scroll;

.sidebar-item-list.flex-1.scrollbar-spacing {
    display: flex;
    padding-bottom: 0;

div#right-sidebar {
    width: 50%;

div#right-sidebar, .cp__right-sidebar-scrollable {
    height: calc(100vh - 48px);
    scroll: initial;
  • The Excalidraw integration is being prepped to be updated (link) – great news as should hopefully bring in a number of recent and useful features.
  • Capitalisation of letters – @RossLaird asks “I’ve seen various discussions in the Logseq community about capitalization, so I’m wondering if I should be more attentive to that. Is there a good reason to use lowercase instead of capitalized pages, and should my tags always be lowercase? Does it matter?” Simple response is “Does not matter as the file names are stored as lowercase” I capitalise my pages since I think that looks nicer and easier on the eyes.
  • Wanting to see all your to-dos on one page? @Squib writes “due to the nature of logseq there’s a few ways: if you have any todo’s just hit ctrl+k and type “todo” or you can search through your pages, or you can create the page by typing [[TODO]]”.
  • Looking to collapse and expand blocks on the fly? Remember you can use ctrl /cmd+ up / down arrow when in non edit mode (press esc) to collapse and expand blocks.
  • @Gianthobbit talks us through their use of tasks – I use the various task stages to mean different things:, now: do today, todo: do this next (this week), later: not a priority, waiting: on someone else to do,follow up, doing: reserved for sub task only, does not show up in any of my queries. I have custom queries on the today journal page that show now and to do. These hide any items that are scheduled or deadline for the future. Sorted by priority (A then B etc). I block reference items from now to add to the todays journal page and take notes as children underneath that. I have a waiting query that pulls in any overdue waiting task. Everything without a date is assumed to wait until I get a chance to talk to that person in the next meeting. Bbefore I meet with anyone I open up their page which has two queries, one for agenda ([[their name]] [[agenda]]) items as well as all waiting task. I block reference those into the meeting which is always on the journal page. I also have a Overdue custom query on the today page to catch things I did not do or reschedule.
  • @Josh gives us his take on “Getting Start with Logseq: The Perfect Digital Journal” in this excellent video which looks at getting started with Logseq as well as other very useful tips and hints. Thanks for the video, Josh!
  • @CCF asks us “Does anyone attempt to integrate personal- and work-related notes and pages without committing to a fully combined single graph? I want to keep personal and work stuff separate as much as possible, but I find myself often referencing the same stuff in both, like people I interact with, events or trips, reading materials that I may read for pleasure but that have some work application, etc. And right now, I seem to have to just duplicate all of those pages between personal and work graphs and therefore never have a consolidated picture.”. I personally find it much easier to have everything in one graph given the cross pollination of ideas in my work and personal life.
  • Just a reminder – if you want another instance / window of Logseq. you can press ctrl / cmd + n, or you can click you graph name in the top left, and then select New Window.
  • How do you use Logseq for university? (Reddit). “I am a university student that just got into using Logseq. I used to use Notion casually, and got pretty good at it; but the friction in Notion made it hard for me to use. I love how Logseq is made; but my technological illiteracy is making me operate at like 5% of Logseq’s capabilities. I was wondering if anyone use Logseq for lecture notes/class notes and could share how you structure your pages/notes. Do you type your notes in your journal or in a specialized page for the class?” @lessangrymoresaid responds with “I use it for university and love it. I use my journal to collect every note. I also use templates—I make one template for every class (i. e., statistics; geology, etc.) In the template, I make sure to include class name, start date, due date, and other info. I also tag them with #[[notes]], or #[[assignments]], or #[[structure]] (for syllabus and such.) For me, the tags are critical because I create a query page for each course, which I add to my favorites menu. On the query page, I keep two or three queries that sort my relevant journal entries into sections. This way I can see current assignments (I #[[assignment archive]] tag whatever I’m done with), class notes, lecture notes, or whatever I want to query for. If you’re good (and consistent) with tagging you can query up anything really quickly.” Lots more comments and content in the reddit post which are worth checking out.

Logseq Feature Requests

You can check out the full list of FRs here.

My Favourite Requests for this week:

  • Sawhney and hkgnp (Ben) Plugins Intro – Would be fantastic if @Sawhney and @hkgnp did a brief introduction and overview of how they got started with Logseq Plugins. A bit like a demonstration of the tools used, how they went about coding it and then publishing their plugin. Remember the more votes this gets, the more chances of Logseq having to implement this 😋
  • Calendar plugin – Should be improved and integrated into Logseq. Given that Logseq is fundamentally based on a Daily Notes page, I think the calendar plugin should be integrated and improved (keyboard shortcuts, go to today, go to last month, year, etc).
  • “Fit page width” option for pdf viewer – When open a pdf viewer in Logseq, I drag the divider between the pdf viewer and the main middle window to their appropriate width. I’d like to have a “fit page width” option that maximize the pdf zoom to fit the width of the pdf viewer (Using the Zoom in/out buttons usually overshoot/undershoot the magnification I need). We can set the default setting to fit the page width every time the divider is adjusted too.
  • Add date ranges – Being able to add date ranges would be very useful for ongoing events/tasks. This differs from deadlines and repeating deadlines in that it may not be a small task that must be done multiple times, but just one bigger task spread out over multiple days. e.g. adding something like [[July 17th, 2021 – July 27th, 2021]] and then having that in the linked references for all dates in between

Top Voted Favourite Requests from last week:

  • Incremental search in page with F3/Ctrl-F – Today Ctrl-Shift-K is used to search within a page; it pops up a popup window showing all the blocks containing the given text (I think it’s missing some sometimes, but that’s a separate issue). You can click on those to pop down the search window and go to that location in the document. I would much prefer a standard search like in browsers or Emacs: hit Ctrl-F or F3, enter some text, and it finds and highlights the next location of that text in the document. Repeating Ctrl-F goes to the next location. No popup (just a small search box to enter the text).
  • PDF annotation: add pin reference in addition to quote reference – Remnote has a neat feature where you can link back to highlighted text with a pin that acts as the link from your own summary back to the PDF. Currently logseq only supports copying the entire quote text. In the spirit of increasing the learning effect by summarizing texts in your own words, the pin would be a very welcome feature so to not clutter your own summary unnecessarily.
  • [Template] Selectable values in key-value pairs – When we use this template, we need to type in the value of status manually. If we have a prespecified status set (e.g., {one, two, three, four}), would it be better if we can create a template.

Logseq Plugins

  • Readwise – Readwise published their latest newsletter (link) where unfortunately there is no mention of the Logseq integration. I am hoping this is an oversight, but will try to find out more and report back.
  • Templater@Sawhney, yet again, surprises us with his many talents with a plugin that allows you to create a templater button, which on click, inserts the contents of the template you’ve specified, under the block. Definitely worth checking out.
  • Date NLP – This plugin by @hkgnp uses NLP (Natural Language Processing) to parse your content for dates and times so that they can be easily tracked through your journal pages.
  • Milestone – Allows you to see your milestones in the calendar.
  • OSMmaps@hkgnp gives us a great plugin to include a map in our Logseq. This plugin lets you create a map and plot a marker on a specific spot. A possible use case is to perhaps journal an event that happened somewhere memorable.
  • mark-map@Richard updated the mind map plugin to allow page traversing, you could stay on the mindmap longer if you wish.

I hope you enjoy this slightly more cohesive format and structure of the post and as always, thank you so much for reading. Happy weekend, everyone!