5-Mar-22: Logseq Hiring, iOS sync workaround, Details workflow, Importing, Todo and task management, new and updated plugins

Apologies this is a day later than planned, unfortunately yesterday was a lovely day out at the dentist and it took slightly longer than expected due to delays and whatnots. To hopefully cheer everyone up on this Sunday morning (or afternoon), here is a picture…of the skyline at sunset.

Bet you thought it was going to be of a dentist chair 😉 Anyway, now that the chair has been put back in the upright position we can get down to business.


No new release to report on this week as the devs are hard at work on getting the Logseq Sync solution prepared for us and ensure that new releases are as flawless as possible.

As a reminder, you can download the latest version, check here. If you are feeling adventurous, you can download the Nightly build, but please treat with care and back up your data if doing so.

Logseq News / Events

  • I reported last week that the Logseq team expect to start internal testing of the sync service. We are anxiously waiting to hear how the internal testing went (if it was possible) and any updates as to when the service will makes its public appearance. I will keep you updated with any developments.
  • During the past week Logseq was trending on GitHub and gained something like 800 stars, in a week!!. Logseq stands at a cool 11.4k stars today. Great going by the devs.

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

  • @DaneilTomasz gives a temporary workaround for those on iOS and have a copy with Sync. For those like me who are on ios and have a copy with sync, I think I found a temporary solution (Working copy app https://workingcopyapp.com/ – a git client for ios) ; Use working copy to link your git repo with icloud logseq folder: Working copy has a new feature called «Link repository to Folder» which can be found in the share sheet for the repository. Basically 0) Apply for free working copy features if you are a student https://education.github.com/pack 1) Put your logseq database as private repo on github or gitlab 2) Use working copy to clone it to your ipad 3) Create an empty folder inside Logseq folder on icloud (the one with Logseq icon) that has the same name as your logseq database 4) Open your database in working copy and sync use «Link repository to Folder» from the share menu and choose folder in Logseq data folder on icloud 5) You could open the repository in logseq and use Working Copy to manage it as git repository.
  • This guide on @Luhmann workflow is definitely worth a read. Looks at daily journal, pages, reading notes and much more. There is definitely something for everyone in this fantastic guide. Thanks Luhmann!
  • Importing ‘traditional’ flat Markdown files into Logseq. I’ve been itching to try the Logseq approach to note-taking but I already have a significant amount of notes written in ‘flat’ Markdown files where one could argue that the ‘indentation levels’ are denoted by the Markdown heading. Thus I’m wondering: is there a way to import flat markdown files and have them automatically converted to outlines based on the level of the heading? Unfortunately it is not as easy due to the difficulty in interpreting what should be a block and what should not. When I opened a flat MD file in Logseq it’d translate every new line as a block so I guess it doesn’t technically need the dash but my issue was that it was ignoring the headings which, at least to me, clearly indicate a logical indentation eg in the same way Obsidian would create an outline for a flat note based on the heading levels While I really enjoy the flexibility this per-block concept offers I imagine a lot of people had old flat notes that now have to be converted by hand which just raises the barrier to entry.
  • Difference between [[]] and #? There is no difference, and a slight aside: there is also #[[]], which can act as a tag for a string of words. Thus #[[Northwest Bird Populations]] renders as a tag #Northwest Bird Populations. In essence, use the one you like the best as the end result is the same.
  • Workflow question with work (consulting) vs personal. Currently I have one graph for all my documentation. This includes personal stuff like my home network, daily journals etc. I’ve just started doing some consulting work and I’ve found putting my notes, pdf annotations, etc in logseq has been a game changer. I simply created a new document for my client (ClientA) and away I went. However, I was thinking that it might make more sense to create a new graph (folder) specifically called ClientA where I store everything for that contract. Then when contract is over i don’t have to worry about their data mixing with my personal or other Client data – Almost like archiving. Solution seems to make use of namespaces.
  • @pbernardo touches up structure in their point: Whether it is PARA, Johnny Decimal, Dewey … etc The thing is with more hierarchical apps it seems easy to implement it in your note-taking app, while in Logseq or Roam, I am not so sure if you are then breaking part of the “magic” of working on a graph. What are your thoughts on this? Can namespaces allow you to easily implement something like PARA?
  • @Ryan Dejaegher, @virtualprocessor and @qwxlea had a fantastic to and fro on task management. The responses and thoughts are extensive and I will not do it justice by copying it here, so if you have some spare time and are interested in the subject, please do read the posts from here.
  • Wondering if you can do mathematical equations in Logseq? Yes, you can. Make sure you check out the Query Table Functions here.
  • @Luhmann gives us an idea to ponder. “I’m re-thinking how I use Readwise. It takes up half of my graph, but I rarely access most of the pages, even via search. I’m thinking it is better to just import notes manually when I am working on an article. I might even consider just setting up a separate Obsidian (or Logseq) graph just for storing my Readwise notes and copy them over on a case-by-case basis. (This too may be unnecessary when I get access to the Readwise app…)” @Alex responds with “Services like readwise make it easy to fall into the [[collectors fallacy]] that you copy/paste lots of stuff in your graph without properly incorporating it into your system. Sometimes it’s bad when things are too convenient”.
  • Students (and others) who are new to Logseq and wanting to put notes in folders and subfolders, check this video out before you do – hopefully give you some tool for thought.

Logseq Feature Requests

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

  • Favorite Blocks on left sidebar – I was surprised to find out i couldn’t favorite a particular block, only pages; Given how outlining is the main structure, how we can focus/zoom-in even with breadcrumbs it creates this expectation that blocks are treated as pages/contents themselves. Not being able to straight favorite a block broke the illusion so to speak, bringing forward the need/necessity to think in files instead of outlining
  • Define and display hierarchies – Browsing through a hierarchy can be very insightful. Defining and browsing hierarchies should be made more flexible and powerful
  • Dedicated search for tasks only – A “quick search” feature that only fuzzy-searches tasks. Eg: Hit Ctrl-T and it will bring up a search window to search all tasks.
  • Different plugins for each graph – Which plugins I use is very much dependent on how I use a graph and I would like to be able to load different plugins (and perhaps even themes) depending on which graph I am using. Obsidian already does this.
  • Improvement #1: Change current left-click behavior of a reference to a block – Logseq doesn’t have an anchor link functionality (presently and to my knowledge). This is understandable because Logseq is not a mature product, yet. Right now, in Logseq, left-clicking in the block dot and left-clicking on a block reference elicits the same behavior: that same block is presented, alone, replacing the current view. This never made sense to me. Since day 1.

Logseq Plugins

  • Agenda by @haydenull. A plugin for logseq to show agenda
  • Parse CSV by @hkgnp. This simple plugin lets you import a CSV file and converts it to an inline table in Logseq!
  • VIM shortcuts by @vipzhicheng has been updated to 0.1.0. This is a big release – it now supports VIM-like command mode! This opens a lot possibilities for the future of this plugin. I already prepared about 20+ commands or aliases in this release about page redirection, marks management and string substitution and so on.
  • Chart Render by @hkgnp has been updated to 1.10.0. Now supports multiple series in line, bar and stacked bar charts
  • Media-ts by @Sethyuan. This plugin can generate timestamps for video, audio and Bilibili video, it takes you to the corresponding video/audio position when clicked.
  • logtools by @cannibalox include a variation of the kanban css tool to make image galleries. It will release shortly.
  • @Sawhney teases us with an upcoming plugin:

For Fun

After a great question by on personal Logseq mottos, here is a list of the ones we have received so far – If you have anymore, please feel free to add them here:

  • “Everything starts in the journal”
  • “Start writing and let the structure grow, as opposed to defining a workflow before you even start”
  • “Tag anything you might want to come back to later”
  • “Stop trying so hard”
  • “Read with purpose”
  • “Write once, tag twice, and think thrice.” 

Many thanks for reading this week’s edition of LogseqWeekly episode.