w3m VS vimwiki

Get the w3m sources: git clone https://github.com/tats/w3m

nvi2 [0]: I got to like the simplicity of nvi when installing Void Linux on my laptop, but it had some annoying bugs that made me switch to nvi2. In general, it feels like `good' software; powerful enough by virtue of being a 1:1 vi clone with a few crucial improvements (multibyte, multi-undo, etc.), but simple enough to hack on if I miss some feature. Though no autocomplete means it's not suitable for more verbose languages, like Java.

QuickJS [1]: qjscalc is my go-to scientific calculator, and qjs my go-to JavaScript implementation for simple programs. The C interface is very nice to use, too. All in all, it feels very much like a "complete" engine, even if not quite as fast as one with JIT.

w3m [2]: Somewhat lacking as a web browser, but a very good pager. Would take it over less any day. Also has the best table display of any text-mode browser, supports inline images, and is rather extensible.

Wine [3]: It's gotten so good that I no longer have to dual boot Windows. Still not perfect, but definitely on my list of "good software".

[0]: https://github.com/lichray/nvi2

[1]: https://bellard.org/quickjs/

[2]: https://github.com/tats/w3m

[3]: https://www.winehq.org/

newer https://github.com/tats/w3m

I liked w3m a lot back when I had a job were rando browsing was discouraged. https://github.com/tats/w3m

> I've been noodling about the implementation of adding functionality to w3m and lynx so there is a separate fetch-page func but report a different User-Agent header (eg, "Mozilla"). I've encountered many pages that don't allow access until I change the "lynx-*" header (bastards).

Wouldn't this feature suffice? https://github.com/tats/w3m/blob/master/doc/README.siteconf

The first result, ffs: https://github.com/tats/w3m

But the problem is that a lot of the code isn't commented to explain what they're doing and there isn't a lot of documentation online to use the software effectively. (In order to not make my question vague, I'm trying to build a front end Gtk GUI to w3m. But I don't need explanation to the code or steps to do this. even though I didn't understand it and I don't know the steps I need. What I'm looking for is a method to effectively study the code of an open source project that didn't take into consideration that you'll study it, therefor they didn't document well the structure of their codebase and how the project was build and the different parts of making it).

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.