diff options
| author | foswret <foswret@posteo.com> | 2026-04-05 16:57:21 -0500 |
|---|---|---|
| committer | foswret <foswret@posteo.com> | 2026-04-05 16:57:21 -0500 |
| commit | c02bbdba289e3a48fbfdf2a39972ee436d079121 (patch) | |
| tree | a7f7a10ab938fd04005e1b54f253b68dd2677141 | |
| parent | 06e39ee847cb3a06cd6f5926f00f2b0a1864ea77 (diff) | |
fix README.md
| -rw-r--r-- | README.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -4,17 +4,17 @@ jumper.sh: A roundabout way of managing and launching bookmarks I sometimes feel like a bookmark hoarder. I have hundreds of bookmarks of random odds and ends, but they are beholden to whatever browser im using. They cannot be easily shared, must be exported/imported, and are hard to navigate. `jumper.sh` attempts to be a tool to wrangle your bookmarks in a simpler fashion. In terms of speed, this script isn't that much better than the autofill results in your browser, but it has 3 main advantages. -1. Plaintext Storage +- 1. Plaintext Storage - To import/export Chrome or Firefox bookmarks, you need to do so in `.html` or `.json` format. - `jumper.sh` simply takes in plaintext files that are readable by themselves. -2. Scriptable +- 2. Scriptable - Because `jumper.sh` works in the terminal, the data it outputs can be chopped, analyzed, or used however one likes. - Ex. Share list of websites on the internet, curl them, open whichever one you like, etc. -3. Browser Agnostic +- 3. Browser Agnostic - You can launch the same exact bookmarks in chrome, firefox, `w3m(1)`, `lynx(1)`, etc. without much hassle. # Install -- Note: There is probably a better way to install than this way. +- Note: There is probably a better way to install than this way than copying the whole script to `$PATH`. ```shell git clone https://git.foswret.com/jumper cd jumper |