tabist VS Fennel

I have a extension that does that almost pretty identically to what you are looking for... it does list out every page you have but doesn't list the url. there is an unreleased version that I use that has a tab dumping to json that I use for just that session restore reason.

Maybe I'll finish the updated version and release it soon.

feel free to check it out: https://github.com/fiveNinePlusR/tabist

https://addons.mozilla.org/en-US/firefox/addon/tabist/

https://chrome.google.com/webstore/detail/tabist/hdjegjggiog...

I wrote a little webext to help me find tabs in a visual way grouped by window. middle click closes the tab and left click brings the tab you click on to the forefront. It's simple but something I use many times every day.

feel free to try it out:

https://addons.mozilla.org/en-US/firefox/addon/tabist/

https://chrome.google.com/webstore/detail/tabist/hdjegjggiog...

https://github.com/fiveNinePlusR/tabist

for a lot of people you search for something to solve a problem. for instance debugging an issue. you middle click on a bunch of promising tabs and then go through them. if there is some useful information on that page you leave it open but it's rare that it's the only thing you need to know to solve your problem. another use is some API you need to use so you'd open up a bunch of tabs on the functions you are exploring how you need to use them.

I also separate the issue by window too and also use tabs and windows as temporary bookmarks really. not worthy of a full bookmark but not finished with.

I created an webextension to deal with handling those tabs because having a bunch of tabs across a bunch of windows is not the most ergonomic without one. might be useful for someone here I suppose: https://github.com/fiveNinePlusR/tabist

https://chrome.google.com/webstore/detail/tabist/hdjegjggiog...

https://addons.mozilla.org/en-US/firefox/addon/tabist/

I am like your friend... basically tabs are a "working memory" that you don't want to store permanently in bookmarks. each window or sets of windows is typically a different topic that is being research on with a bunch of middle clicks to open tabs. I have so many open that I wrote a small webext for it that shows a page of all your tabs that you can click on to navigate to that tab with a click. just a nicer interface to see all the windows open and all the tabs. https://github.com/fiveNinePlusR/tabist

It's interesting: minimal software is out there, but folks don't tend to choose it. I spend a fair amount of time thinking about how to be conservative in my dependencies, and this encourages a lightweight stack that tends to perform pretty well. These days, I'm favoring tools like Lua, SQLite, Fennel[0], Althttpd[1], Fossil[2], and the Mako Server[3] and find that great, lightweight, stable, efficient software is to be had, for free, but you have to go a bit off the beaten path. This isn't stuff you hear about on Stack Overflow.

In terms of frontend, which the post focuses on (Google Docs and a 30MB doc), I guess I'm conflicted. While I tend to favor native apps + web pages, I'm also a daily Tiddlywiki user, and I really think web apps have their place (heck, one idea I'm working on is a lightweight local server that lets you run web apps like Tiddlywiki). But without a doubt, Tiddlywiki is more resource intensive than Emacs (my go-to for notetaking when I'm not on TW). My tab for a 6MB Tiddlywiki file uses 155MB of RAM, and my (heavily customized, dozens of open buffers) Emacs session uses 88MB. So I do think the author has a good point.

[0]: https://fennel-lang.org/

Eh it's not just luajit and luajit didn't create that problem either. It's a symptom of lua actually succeeding at its design goal of being easily embedded as an extension language. A significant number of incompatible runtimes are more popular than the most recent puc lua, including I believe the older official lua 5.2 released in 2011.

I've done a fair bit of professional lua development and I don't think I've ever written standalone up-to-date puc lua except maybe for some tooling & scripts. It's such a small language and used in such a way that the runtime, distribution method, and available APIs have much more impact on your use (and compatibility) than the version.

Virtually everyone shipping a lua environment is also shipping changes to it that make it a unique target, if only extensions to the standard library. This is why I think syntax layer-only approach like fennel's is the correct choice for improving on lua. It mirrors lua's runtime semantics exactly, and allows you to access the implementation peculiars on their own terms and so can just be run on time of any lua system.

https://fennel-lang.org

Just learned about https://fennel-lang.org/ , could have probably used that as well to avoid Lua.

> I’m positive that there is a Lispy language out there (actually in existence, or the aether) that is appropriate for embedded work, but the constraints of the target make it difficult to envision.

Perhaps Fennel* fits the bill?

* https://fennel-lang.org/

I've also seen neovim plugins written in fennel [0], so if you want something lispy, that's possible now.

[0]: a Lisp that compiles to Lua, https://github.com/bakpakin/Fennel

Something similar: Fennel (https://fennel-lang.org/) is a lisp that compiles into Lua, which nvim can use as plugins, so you can write nvim plugins in a lisp. Aniseed (https://github.com/Olical/aniseed) makes this really easy.

If you want a more FP language on the Lua runtime, you might be interested in Fennel. I wrote a post about adding Fennel compiler to a hslua interpreter a while back, which might be useful for you.