Logseq is a highly efficient note-taking and knowledge management app with decent Markdown support.
While using Logseq, one thing to keep in mind is that the text formatting isn't pure Markdown. This is because Logseq uses bullet blocks as the basic unit of content and also supports Org-mode.
Whenever you start a new document or press Enter after a sentence, a new block is created — and this block can be referenced from anywhere within Logseq. That’s part of what makes Logseq so powerful.
Still, formatting your notes clearly is just as important. In this article, we’ll take a closer look at how text formatting works in Logseq.
Basic Markdown syntax
As I said above, since Logseq supports Markdown, all the basic Markdown syntax will work here.
You remember the Markdown syntax, right?
Description
Markdown Syntax
Six Levels of Heading
# Level One
## Level Two
### Level Three
#### Level Four
##### Level Five
###### Level Six
Second, since Logseq has Org-mode support, you can create a quote block using the syntax:
#+BEGIN_QUOTE
Your Quote text here
#+END_QUOTE
You can access this by pressing < key and then typing Quote and enter.
🚧
If you are using the quotes with a preceding > syntax, then every markdown renderer will render the document properly. The org-mode syntax won't work in all environments.
0:00
/0:15
Adding Quotes in Logseq
Add an admonition block
Admonition blocks or callouts come in handy for highlighting particular piece of information in your notes, like a tip or a warning.
The warning below is the best example here.
🚧
These admonition blocks are a feature of Logseq app. You cannot expect this to work properly in other apps. So, plain text markdown users should take care in this scenario.
The usual Org-mode syntax for these blocks is:
#+BEGIN_<BLOCK NAME>
Your Block Text
#+END_<BLOCK NAME>
For example, a simple tip block syntax looks like:
#+BEGIN_TIP
This is a tip block
#+END_TIP
Let's take a look at some other interesting syntax names:
BLOCK NAME
NOTE
TIP
IMPORTANT
CAUTION
PINNED
Admonition Blocks in Logseq.
You can access this by typing the < key and then searching for the required block.
0:00
/0:27
Admonition blocks in Logseq.
Conclusion
The ability to add a call out box makes your notes more useful, in my opinion. At least it does for me as I can highlight important information in my notes. I am a fan of them and you can see plenty of them in my articles on It's FOSS as well.
Stay tuned with me in this series as I'll share about adding references in Logseq in the next part.
Desktop Linux is mostly neglected by the industry but loved by the community. For the past 12 years, It's FOSS has been helping people use Linux on their personal computers. And we are now facing the existential threat from AI models stealing our content.
If you like what we do and would love to support our work, please become It's FOSS Plus member. It costs $24 a year (less than the cost of a burger meal each month) and you get an ad-free reading experience with the satisfaction of helping the desktop Linux community.
How sharp is your Git knowledge? Our latest crossword will test your knowledge.
💡 Quick Handy Tip
In Firefox, you can delete temporary browsing data using the "Forget" button. First, right-click on the toolbar and select "Customize Toolbar".
Now, from the list, drag and drop the "Forget" button to the toolbar. If you click on it, you will be asked to clear 5 min, 2 hrs, and 24 hrs of browsing data, pick any one of them and click on "Forget!".
🤣 Meme of the Week
The glow up is real with this one. 🤭
🗓️ Tech Trivia
On April 7, 1964, IBM introduced the System/360, the first family of computers designed to be fully compatible with each other. Unlike earlier systems, where each model had its own unique software and hardware.
While it covers the basics of note-taking, it also doubles down as a powerful task manager and journaling tool.
Logseq Desktop
What sets Logseq apart from traditional note-taking apps is its unique organization system, which forgoes hierarchical folder structures in favor of interconnected, block-based notes. This makes it an excellent choice for users seeking granular control and flexibility over their information.
In this article, we’ll explore how to install Logseq on Linux distributions.
Use the official AppImage
For Linux systems, Logseq officially provides an AppImage. You can head over to the downloads page and grab the AppImage file.
It is advised to use tools like AppImageLauncher (hasn't seen a new release for a while, but it is active) or GearLever to create a desktop integration for Logseq.
Fret not, if you would rather not use a third-party tool, you can do it yourself as well.
First, create a folder in your home directory to store all the AppImages. Next, move the Logseq AppImage to this location and give the file execution permission.
Go to AppImage properties
Right-click on the AppImage file and go to the file properties. Here, in the Permissions tab, select "Allow Executing as a Program" or "Executable as Program" depending on the distro, but it has the same meaning.
Here's how it looks on a distribution with GNOME desktop:
Toggle Execution permission
Once done, you can double-click to open Logseq app.
🚧
If you are using Ubuntu 24.04 and above, you won't be able to open the AppImage of Logseq due to a change in the apparmour policy. You can either use other sources like Flatpak or take a look at a less secure alternative.
Alternatively, use the 'semi-official' Flatpak
Logseq has a Flatpak version available. This is not an official offering from the Logseq team, but is provided by a developer who also contributes to Logseq.
First, make sure your system has Flatpak support. If not, enable Flatpak support and add Flathub repository by following our guide:
Now, install Logseq either from a Flatpak supported software center like GNOME Software:
Install Logseq from GNOME Software
Or install it using the terminal with the following command:
flatpak install flathub com.logseq.Logseq
Other methods
For Ubuntu users and those who have Snap setup, there is an unofficial Logseq client in the Snap store. You can go with that if you prefer.
There are also packages available in the AUR for Logseq desktop clients. Arch Linux users can take a look at these packages and get it installed via the terminal using Pamac package manager.
Post Installation
Once you have installed Logseq, open it. This will bring you to the temporary journal page.
You need to open a local folder for Logseq to start your work to avoid potential data loss. For this, click on the "Add a graph" button on the top-right, as shown in the screenshot below.
Click on "Add a graph"
On the resulting page, click on "Choose a folder" button.
Click "Choose a folder"
From the file chooser, either create a new directory or select an existing directory and click "Open".
Select a location
That's it. You can start using Logseq now. And I'll help you with that. I'll be sharing regular tutorials on using Logseq for the next few days/weeks here. Stay tuned.
There was a time when coding meant painstakingly writing every line, debugging cryptic errors at 3 AM, and pretending to understand regex. But in 2025? Coding has evolved, or rather, it has vibed into something entirely new.
Enter Vibe Coding, a phenomenon where instead of manually structuring functions and loops, you simply tell AI what you want, and it does the hard work for you.
This approach has taken over modern software development. Tools like Cursor and Windsurf, AI-powered code editors built specifically for this new workflow, are helping developers create entire applications without in-depth coding knowledge.
Gone are the days of memorizing syntax. Now, you can describe an app idea in plain English, and AI will generate, debug, and even refactor the code for you.
At first, it sounded too good to be true. But then people started launching SaaS businesses with nothing but Vibe Coding, using AI to write everything from landing pages to backend logic.
We thought, since the future of coding is AI-assisted, you’ll need the right tools to make the most of it.
So, here’s a handpicked list of the best code editors for vibe coding in 2025, designed to help you turn your wildest ideas into real projects, fast. 💨
🚧
NON-FOSS Warning: Not all the editors mentioned in this article are open source. While some are, many of the AI-powered features provided by these tools rely on cloud services that often include a free tier, but are not entirely free to use. AI compute isn't cheap! When local LLM support is available, I've made sure to mention it specifically. Always check the official documentation or pricing page before diving in.
1. Zed
If VS Code feels sluggish and Cursor is a bit too heavy on the vibes, then Zed might just be your new favorite playground.
Written entirely in Rust, Zed is built for blazing fast speed. It’s designed to utilize multiple CPU cores and your GPU, making every scroll, search, and keystroke snappy as heck.
And while it's still a relatively new player in the editor world, the Zed team is laser-focused on building the fastest, most seamless AI-native code editor out there.
You get full AI interaction built right into the editor, thanks to the Assistant Panel and inline assistants that let you refactor, generate, and edit code using natural language, without leaving your flow.
Want to use Claude 3.5, a self-hosted LLM via Ollama, or something else? Zed’s open API lets you plug in what works for you.
Key Features:
✅ Built entirely in Rust for extreme performance and low latency.
✅ Native AI support with inline edits, slash commands, and fast refactoring.
✅ Assistant Panel for controlling AI interactions and inspecting suggestions.
✅ Plug-and-play LLM support, including Ollama and Claude via API.
✅ Workflow Commands to automate complex tasks across multiple files.
✅ Custom Slash Commands with WebAssembly or JSON for tailored AI workflows.
Flexpilot IDE joins the growing league of open-source, AI-native code editors that prioritize developer control and privacy.
Forked from VS Code, it's designed to be fully customizable, letting you bring your own API keys or run local LLMs (like via Ollama) for a more private and cost-effective AI experience.
Much like Zed, it takes a developer-first approach: no locked-in services, no mysterious backend calls. Just a clean, modern editor that plays nice with whatever AI setup you prefer.
Key Features
✅ AI-powered autocomplete with context-aware suggestions
✅ Simultaneously edit multiple files in real-time with AI assistance
✅ Ask code-specific questions in a side panel for instant guidance
✅ Refactor, explain, or improve code directly in your files
✅ Get instant AI help with a keyboard shortcut, no interruptions
✅ Talk to your editor and get code suggestions instantly
✅ Run commands and debug with AI assistance inside your terminal
✅ Reference code elements and editor data precisely
✅ AI-powered renaming of variables, functions, and classes
✅ Generate commit messages and PR descriptions in a click
✅ Track token consumption across AI interactions
✅ Use any LLM: OpenAI, Claude, Mistral, or local Ollama
✅ Compatible with GitHub Copilot and other VSCode extensions
While GitHub Copilot isn’t a standalone code editor, it’s deeply integrated into Visual Studio Code, which makes sense since Microsoft owns both GitHub and VS Code.
As one of the most widely used AI coding assistants, Copilot provides real-time AI-powered code suggestions that adapt to your project’s context.
Whether you’re writing Python scripts, JavaScript functions, or even Go routines, Copilot speeds up development by generating entire functions, automating repetitive tasks, and even debugging your code.
Key Features:
✅ AI-driven code suggestions in real-time.
✅ Supports multiple languages, including Python, JavaScript, and Go.
✅ Seamless integration with VS Code, Neovim, and JetBrains IDEs.
✅ Free for students and open-source developers.
Pear AI is a fork of VSCode, built with AI-first development in mind. It’s kinda like Cursor or Windsurf, but with a twist, you can plug in your own AI server, run local models via Ollama (which is probably the easiest route), or just use theirs.
It has autocomplete, context-aware chat, and a few other handy features.
Now, full transparency, it's still a bit rough around the edges. Not as polished, a bit slow at times, and the updates? Eh, not super frequent.
The setup can feel a little over-engineered if you’re just trying to get rolling. But… I see potential here. If the right devs get their hands on it, this could shape up into something big.
Key Features
✅ VSCode-based editor with a clean UI and familiar feel
✅ "Knows your code" – context-aware chat that actually understands your project
✅ Works with remote APIs or local LLMs (Ollama integration is the easiest)
✅ Built-in AI code generation tools curated into a neat catalog
✅ Autocomplete and inline code suggestions, powered by your model of choice
✅ Ideal for devs experimenting with custom AI backends or local AI setups
If you've ever written Java, Python, or even Kotlin, chances are you’ve used or at least heard of JetBrains IDEs like IntelliJ IDEA, PyCharm, or WebStorm.
JetBrains has long been the gold standard for feature-rich developer environments.
Now, they're stepping into the future of coding with Fleet, a modern, lightweight, and AI-powered code editor designed to simplify your workflow while keeping JetBrains' signature intelligence baked in.
Fleet isn’t trying to replace IntelliJ, it’s carving a space of its own: minimal UI, fast startup, real-time collaboration, and enough built-in tools to support full-stack projects out of the box.
And with JetBrains’ new AI assistant baked in, you're getting contextual help, code generation, and terminal chat, all without leaving your editor.
Key Features
✅ Designed for fast startup and low memory usage without sacrificing features
✅ Full-Stack Language Support- Java, Kotlin, JavaScript, TypeScript, Python, Go, and more
✅ Real-Time Collaboration.
✅ Integrated Git Tools like Diff viewer, branch management, and seamless commits
✅ Use individual or shared terminals in collaborative sessions
✅ Auto-generate code, fix bugs, or chat with your terminal
✅ Docker & Kubernetes Support - Manage containers right inside your IDE
✅ Preview, format, and edit Markdown files with live previews
✅ Custom themes, keymaps, and future language/tech support via plugins
Cursor is a heavily modified fork of VSCode with deep AI integration. It supports multi-file editing, inline chat, autocomplete for code, markdown, and even JSON.
It’s fast, responsive, and great for quickly shipping out tutorials or apps. You also get terminal autocompletion and contextual AI interactions right in your editor.
Key Features
✅ Auto-imports and suggestions optimized for TypeScript and Python
✅ Generate entire app components or structures with a single command
✅ Context-gathering assistant that can interact with your terminal
✅ Drag & drop folders for AI-powered explanations and refactoring
✅ Process natural language commands inside the terminal
✅ AI detects issues in your code and suggests fixes
✅ Choose from GPT-4o, Claude 3.5 Sonnet, o1, and more
Windsurf takes things further with an agentic approach, it can autonomously run scripts, check outputs, and continue building based on the results until it fulfills your request.
Though it’s relatively new, Windsurf shows massive promise with smooth performance and smart automation packed into a familiar development interface.
Built on (you guessed it) VS Code, Windsurf is crafted by Codeium and introduces features like Supercomplete and Cascade, focusing on deep workspace understanding and intelligent, real-time code generation.
Key Features
✅ SuperComplete for context-aware, full-block code suggestions across your entire project
✅ Real-time chat assistant for debugging, refactoring, and coding help across languages
✅ Command Palette with custom commands.
✅ Cascade feature for syncing project context and iterative problem-solving
✅ Flow tech for automatic workspace updates and intelligent context awareness
✅ Supports top-tier models like GPT-4o, Claude 3.5 Sonnet, LLaMA 3.1 70B & 405B
It’s still new but shows a lot of promise with smooth performance and advanced automation capabilities baked right in.
I’ve personally used GitHub Copilot’s free tier quite a bit, and recently gave Zed AI a spin and I totally get why the internet is buzzing with excitement.
There’s something oddly satisfying about typing a few lines of instruction and then just... letting your editor take over while you lean back.
That said, I’ve also spent hours untangling some hilariously off-mark Copilot-generated bugs. So yeah, it’s powerful, but far from perfect.
If you’re just stepping into the AI coding world, don’t dive in blind. Take time to learn the basics, experiment with different editors and assistants, and figure out which one actually helps you ship code your way.
And if you're already using an AI editor you swear by, let us know in the comments. Always curious to hear what other devs are using.
It's been a tradition of sort to prank readers on 1st of April with a humorous article. Since we are already past the 1st April in all time zones, let me share this year's April Fool article with you. I hope you find it as amusing as I did while writing it 😄
And other Linux news, tips, and, of course, memes!
This edition of FOSS Weekly is supported byTypesense.
❇️ Typesense: Open Source Search Engine
Typesense is the free, open-source search engine for forward-looking devs. Make it easy on people: Tpyos? Typesense knows we mean typos, and they happen. With ML-powered typo tolerance and semantic search, Typesense helps your customers find what they’re looking for—fast.
In KDE Plasma, you can edit copied texts in the Clipboard. First, launch the clipboard using the shortcut CTRL+V. Now, click on the Edit button, which looks like a pencil.
Then, edit the contents and click on Save to store it as a new clipboard item.
🤣 Meme of the Week
Such a nice vanity plate. 😮
🗓️ Tech Trivia
On March 31, 1939, Harvard and IBM signed an agreement to build the Mark I, also known as the IBM Automatic Sequence Controlled Calculator (ASCC).
This pioneering electromechanical computer, conceived by Howard Aiken, interpreted instructions from paper tape and data from punch cards, playing a significant role in World War II calculations.
