4 ms·
Seems like you could just put the files that already exist under version control? Chrome just uses a JSON file it seems, as an example. On mac: ~/Library/Appli
by bpicolo 10y ago
Seems like you could just put the files that already exist under version control? Chrome just uses a JSON file it seems, as an example.
On mac:
~/Library/Application\ Support/Google/Chrome/Default/Bookmarks.bak
Separate, re-writeable interface for search is cool though :)
- dotancohen 10y agoThe Firefox files are SQLite files, and I believe but haven't checked recently that the Chrome files have no newlines (0x0A) in the files. The whole JSON string is on one line, so Git will rewrite the whole file on each change.
- slim 10y agoGit always rewrites the whole file
- EvilTerran 10y agoSure, technically - but if a file's sensibly broken up into lines on semantic boundaries, "git diff" will at least let you think of it like it only rewrites the bits that actually changed. If you're versioning a file with no linebreaks, the diffs would be meaningless ("minus everything, plus everything"), which is an unfortunate loss of functionality.
- dom0 10y agoI guess you could just smudge/clean it through a JSON linter. You probably don't even need smudge, since Chrome likely has no problems parsing indented JSON.
- bpicolo 10y agoLooked to be pretty printed on my computer.