qtile VS vimwiki

Btw. if you're installing from pip anyway, I HIGHLY recommend using git master's version (pip install git+https://github.com/qtile/qtile). It's very stable and it contains a lot of improvements, features and - mostly important - bug fixes, especially because the fact that the last 0.22.1 release is almost one year old. The current master works fine with xcffib 1.4 and cairocffi 1.6 (the newest possible versions).

Yes, all the dependencies listed in qtile.org are installed.

I think yesterday qtile.org itself seemed to be working properly. Now it is also offline.

Did you see the changelog? https://github.com/qtile/qtile/blob/master/CHANGELOG

You need to have xcffib in version 1.3.0 and you probably have 1.4.0. You also need cairocffi 1.5.1 and you probably have 1.6.0, so it will fail as the next step. Install correct versions or wait until https://github.com/qtile/qtile/pull/4289 is merged.

Meanwhile users can still communicate and ask questions in the official Github discussion board: https://github.com/qtile/qtile/discussions or alternatively in IRC irc://irc.oftc.net:6667/qtile during the blackout time period.

Hello 👋, I use Gnome for my ThinkPad it works nice for me. But giving your ram I would suggest a window manager like Qtile which I prefer and I am about move from Gnome to it when I finish my configurations. But if you want something which will be usable out of the box Xfce is a nice choice too as people mentioned above. 😁😁 Here is the link to GitHub for Qtile if you want to give it a glance https://github.com/qtile/qtile

It's currently not supported on Wayland. There is an open issue for it: https://github.com/qtile/qtile/issues/4225

No, Neorg does not use the same markup as Org-mode. They use their own specification that is specifically designed to be different from Org-mode spec.

https://raw.githubusercontent.com/nvim-neorg/norg-specs/main...

Furthermore, each item you have listed as a benefit to Org-mode is in fact capable of being done in Markdown via plugins for neovim, and probably other markdown editors, like Loqseq, Roamresearch, or Obisidian, much in the same way you speak of plugins that interface with .org docs.

https://github.com/wthollingsworth/pomodoro.nvim

https://github.com/Myzel394/easytables.nvim

https://github.com/vimwiki/vimwiki

So, my suggestion is that before dismissing a comment regarding a plugin that is unfamiliar to you, is to read its spec, and then try to understand why people would be perhaps dismissive of that tool, especially when it chooses to conflict with existing, more popular choices.

you might want to look at how vimwiki does markdown tables https://github.com/vimwiki/vimwiki

I've been thinking of setting up a note taking enviroment in neovim. I've been searching around, and plugins as vimwiki, and nabla.nvim are great choices for me. I'm using Notion right now because of the great commands that brings that make the note taking pretty enjoyable. But the dividers, or putting background to text are features that I don't wanna lose, if possible.

I wrote a manuscript in vim a couple Novembers ago, for NaNoWrimo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim.

I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). Also, while the extra features afforded by Obsidian don't really make a difference during the writing process, I find they're really useful for outlines and other preliminary work, which is something of a point against a vim-only workflow unless you want to use vimwiki [2] or something.

Granted, Obsidian is still a markdown-based tool, so there's still some level of minimalism going on there, but by that point we're really discussing markup vs word processors, which is its own conversation—and to my mind, a much more important one. I much prefer working in markup than in a rich text editor, because plain text is easy to edit and process through the terminal, and because it lets me separate style choices from content.

I find that the markdown live preview that editors like Obsidian and Typora provide (and which vim doesn't) is a really nice compromise between a slick composing experience and the technical affordances of markup. Between that and Obsidian's hypertext features, I think I'll stick with Obsidian for the foreseeable future.

[1]: https://github.com/junegunn/goyo.vim

[2]: https://vimwiki.github.io/

I use vimwiki.

Hey folks, I have been using Neovim for the past 2 years, don't have any complaints, however, I really want to give Emacs an honest try but not really sure where to start. I want to do basic text editing, programming and something similar to vimwiki (https://github.com/vimwiki/vimwiki)

How about learning vim and using vimwiki ?

What, we're talking about wikis and vim, and not mentioning vimwiki?

https://github.com/vimwiki/vimwiki

I tried a whole bunch of personal wikis over the years (I see Zim has been mentioned, that's one of the ones I remember trying) and this is the only one that stuck.

I have created full on programs to systematically created screenshots with the game emulators with RetroArch. Also an automation tool to use a preexisting program named chdman that converts files into a needed format (also unpacking from archives). A little Python script to create a recents list of files for Vimwiki. I also created a program to access 🌈 emojis 🌈. I wrote my own GE Proton downloader and manager. Hell even the window manager I am using on Linux is written and configured in Python, Qtile. I wrote one or two plugins for it and the entire configuration is written in Python, meaning I can use functions, modules and every logic of Python to enhance it. It's Awesome.