[opcon]

I've been half-heartedly looking for something exactly like this for a while, thank you for posting it!

Instead of using Uppity, which appears to be abandoned (?), I found Navigate Up WE (https://addons.mozilla.org/en-US/firefox/addon/navigate-up-w...), which performs essentially the same functionality and appears to be maintained.

Thanks again, this will be very useful!

[a3n]

And thanks for the bug report on github. :)

I have noticed a warning with uppity due to Mozilla's redesign of their extension support, but it's still working for me. Thanks for the tip to Navigate Up.

Not related to the bug, I'm curious what text editor you use. I use Vim, and the reason why I suggest writing links in your source files ending in .rst or .md is so that I can go from source to source in Vim, by putting the cursor over the filename and then gf. That, and then ctrl-o to go back, is very useful to me.

As rst and md are human readable, with a good editor like Vim, you could treat your source files as the wiki and never generate. Not that I would, but you could.

Do you use a different editor with similar capability?

[opcon]

I mainly use Vim, and have tried using both Vimwiki and Org-mode as personal wikis in the past, but they were never quite what I was looking for.

I like writing the wiki content in Vim, but for viewing it I think I prefer it as a webpage.

Following file links in Vim is really useful though, I should use it more often!

[a3n]

I also write in Vim and prefer the webpage view.

File links in Vim are really handy in your Miki when you're writing a couple of pages in a topic and you want to jump back and forth.

Of course in that scenario you can also ':e .' to edit the directory, or use the vim-included netrw, or install nerdtree.

[mhd]

jwz' bookmarklet from 2003 still seems to work, too.

https://www.jwz.org/hacks/bookmarklets.html