Colas.Nahaboo.net - browser

Save these Firefox tabs for later

2026-04-13T00:00:00+00:00

I often look for some concept out of curiority, and end up with tens of browser tabs opened on the subject, and realize that I have no time now to pursue this rabbit into his hole, end up with tons of Firefox windows with tens of tabs gathering dust (and eating RAM) on my desktop. Up to now I just created Foswiki pages or Trello tasks as reminders to tackle these projects later on, but it required enough manual work to often postpone doing it and either losing the info or be swamped in thousands of tabs. And saving them as Firefox bookmarks was cumbersome and required lots of manual management.

What I decided to do is a simple way to save all these tabs offline, and be able to re-open the window simply. I bundle them into what I call .ffst files (for FireFox Saved Tabs), simple text files of one url per line, into a ~/firefox-savedtabs/</code> directory.

Saving a set of tabs: Select the tabs (click on the first one, shift-click on the last one)</li> Open the right-mouse-button menu on a tab, and select Copy URLs</code></li> Create a new file (e.g: some-name.ffst</code>) in the ~/firefox-savedtabs/</code> directory with your favorite editor,</li> Paste the tabs into it,</li> Save.</li> </ul> </li> Restoring the tabs into a new window: either by: running the script below firefox-savedtabs-restore</code> without arguments, and choosing which file to restore.</li> running the script with the ffst file as argument: firefox-savedtabs-restore some-name.ffst</code></li> Browsing the directory ~/firefox-savedtabs/</code> in a file explorer window, and choosing to open the .ffst file with Firefox SavedTabs restore</code> once you have created the ~/.local/share/applications/firefox-savedtabs.desktop</code> file below</li> </ul> </li> </ul> I can thus just mention the .ffstr file in my various "todo" places (TODO lists, TODO files, pinboard, wikis, trello, ...) Note that you can adapt this to any browser, and choose whatever directory name and file extension you want. Updating the tabs is just re-copying the urls and re-pasting in the file. The two scripts are:🔗</a></h2> /usr/local/bin/firefox-savedtabs-restore🔗</a></h3> Note that you can modify in it the restore</code> function to use with another browser. #!/bin/bash # shellcheck disable=SC1090,SC2155,SC2046 # source files, declare&assign # restore saved tabs bundles (text files of urls, one per line) dir="$HOME/firefox-savedtabs/" restore(){ mapfile -t urls <"$1" firefox --new-window "${urls[@]}" exit 0 } if [[ $# == 0 ]]; then # Without args, list the saves, most recent first, and prompt to restore echo "In ~/.firefox-savedtabs/" cd "$dir" || exit 1 select i in $(find . -type f -name \*.ffst \ -printf '%TY-%Tm-%Td.%THh%TM:%TS %h/%f\n' | \ sed -e 's| [.]/|_|' | sort -r | \ sed -re 's/:[0-9]{2}[.][0-9]*//'); do restore "${i#*_}" done else # with a file name or path, restore the window file="$1" if [[ -e "$file" ]]; then restore "$file" elif ! [[ -e "$file" ]] && [[ -e "$dir/$file" ]]; then file="$dir/$file" restore "$file" else echo "***Error: file not found: \"$file\" in $dir" exit 1 fi fi</code></pre>~/.local/share/applications/firefox-savedtabs.desktop🔗</a></h3> [Desktop Entry] Name=Firefox SavedTabs restore # update-desktop-database ~/.local/share/applications/ Exec=/usr/local/bin/firefox-savedtabs-restore %u Type=Application Terminal=false MimeType=x-scheme-handler/x-firefox-savedtabs;</code></pre>

Browser-history 2008-03-21T00:00:00+00:00 Browser-history started on February 15, 1996, out of a desire to overcome a Netscape bug: at the time, there was no global history. [Nowadays, in 2026, all browsers have one, of course.] Back then, if you closed a window, its entire history was lost. For people visiting many sites, the ability to track where they had been meant they didn't have to clutter their bookmarks file. If you weren't sure a site was worth saving, you didn't have to bookmark it; if you needed it later, you could just browse your history files. Later, it occurred to me that this could also be a valuable add-on for people developing experimental browsers [a lot at the time], sparing them from having to build the functionality themselves. Browser-history was a small, efficient daemon written in C. Real user services could be built on top of its log files to provide more advanced features, such as graphical representations, advanced search, or collective histories. While it could be seen as a "quick-and-dirty hack" compared to the general solution of using a personal proxy for housekeeping, it was easy to use and it worked. I created this legacy page to help people find the archived version of the project, specifically the latest version of 2000-07-20</a>. The code archive itself is browser-history-2.8.tgz</a> Here is a screenshot of the page: Enjoy! </a> The manual page🔗</a></h2> NAME🔗</a></h3> browser-history - external history of web browsers, such as netscape SYNOPSIS🔗</a></h3> browser-history [ options ] DESCRIPTION🔗</a></h3> Browser-History is a client-side X daemon maintaining a browser-independent global history of all the web sites you visited .Its usage is very simple, just put the following line in your .xinitrc or your X start-up script: browser-history & </blockquote> And open the file ~/.browser-history/history-log.html and bookmark it. Browser-history came from the will to overcome a Netscape bug: there was no global history, and if you close a window, its whole history is lost. For people browsing lots of sites, having a possibility to track back where one has been before means that you dont have to put everything in your bookmarks file. If you are not sure if a site may be worth remebering, don't add it in your bookmarks. If you need it later, just browse your history files. Later, it came to our minds that this also could be a valuable add-on to people writing experimental browsers, so they dont have to add this functionality to their browser itself. Browser-history is a small and efficient daemon. Real user services could be built on top of the log files it maintains for more possibilities (graphical representation, advanced search options, collective histories). It can be seen as a quick-and-dirty hack wrt to the general solution of using a personal proxy to provide this history and housekeeping facilities. But in the meantime, it is easy to use and it works. IMPLEMENTATION🔗</a></h3> Browser-History spies your web browser and logs in ~/.browser-history/history-log.html</code> all the URLs you went through. You can then browse the log under Netscape or other browsers via the URL: file:~/.browser-history/history-log.html (replace the ~ by your home directory). It tracks automagically all already present browser windows, and all new ones created in the future. This program has no user interface. It just appens information to a log file in html format so you can browse it through a web browser. If more that one hour has passed since last entry, it draws an horizontal lines, and adds H1 headers to delimit new days. Each week (sunday mornings), it archives the week history, compresses it by gzip (that you must have in your path), and starts a new history with links to the older ones. To make room you can just remove the obsolete history files. You can search files for string XXX in shell via: zgrep XXX ~/.browser-history/* </blockquote> This version (2.6) works with Netscape, Arena and Amaya. URLs can be excluded from logging by putting them, one per line in the file ~/.browser-history/history-log.exclude , then, if an URL begins with a line from this file, it is not logged. In this file, empty lines or lines beginning by # are comments This file is read once at startup, and re-read when receiving the signal 1. e.g: # We exclude local files file: # Exclude search engines... http://home.netscape.com http://guide.infoseek.com </blockquote> When browser-history is run, it looks if another one is running, and by default it kills the previous one if it is an older version. Otherwise, it the new one is the same version number or older, it just aborts. OPTIONS🔗</a></h3> All options can be given by their first letter: you can specify either -verbose or -v, but you cannot group options, e.g. you must say -v -k , but not -vk -display display_name Specifies X display, otherwise contents of $DISPLAY is used -verbose outputs information on what it is doing. useful for debug. -Version prints version number and exit. -logdir directory which directory to store files into? defaults to ~/.browser-history -gzip gzip_filename the complete path to the gzip compressor. Defaults to "gzip". E.g: -gzip /usr/gnu/bin/gzip -seconds delay if two entries are made are more than delay seconds apart, an horizontal rule will separate them, else just a simple line break. Defaults to one hour (3600). -replace If there is an already running browser-history on the display, aborts. Default is to replace it only if the version is older than ours. -noreplace If there is an already running browser-history on the display, aborts. Default is to replace it only if the version is older than ours. -kill If there is an already running browser-history on the display, kills it, then terminates immediately in all cases..TP -DontGrab Never Grab the X Server, which might cause deadlocks while debugging, when browser-history or gdb tries to print on the grabbed xterm or emacs. LOG FILE FORMAT🔗</a></h3> A log file can have some decorative HTML to represent days, but each entry has the form: (on a single line since version 2.4) separator name <a href="URL">URL</a> YYYY/MM/DD-HH:MN:SS windowid</code></pre></blockquote> where the following items are: separator: either or name: the name of the document (window title) URL: its URL YYYY/MM/DD-HH:MN:SS: year, month number, day number, hour, minutes, seconds. (2-digit numbers) windowid: the X window ID of the browser window, in hexadecimal </blockquote> Note Before version 2.4, the 4 sub-parts were separated by newlines, but since 2.4, they are only blank-separated to ease searching for URL in log files via "grep". Note Before version 2.5, the year was stored in 2 digits. Now it is stored in 4 (or more :-) digits, to fix this Y2K bug HOME🔗</a></h3> The latest version of browser-history can be found at: ftp://koala.inria.fr/pub/browser-history </blockquote> and its WWW home page, with full technical documentation is at: http://koala.ilog.fr/colas/browser-history </blockquote> AUTHOR🔗</a></h3> Colas Nahaboo, http://koala.ilog.fr/colas COPYRIGHT🔗</a></h3> browser-history bears the same license as the X Window System: you can do everything with this code (selling it, modifying it), except suing me or using my name in your advertisements, or expecting any kind of support or guarantee.