| 1 |
On Fri, Apr 13, 2012 at 08:03:53PM -0500, »Q« wrote: |
| 2 |
> On Fri, 13 Apr 2012 20:06:01 +0000 (UTC) |
| 3 |
> James <wireless@×××××××××××.com> wrote: |
| 4 |
> |
| 5 |
> > […] |
| 6 |
> > What I'm after is manually coping the bookmarks |
| 7 |
> > for seamonkey to another (kde)workstation. |
| 8 |
> |
| 9 |
> As pk says, the bookmarks are now stored in an sqlite database, along |
| 10 |
> with browser history. The best way to port them to another machine is |
| 11 |
> to use the bookmarks manager (ctrl+b) to make a backup (within the |
| 12 |
> manager, that's Tools » Backup), then use the restore option in the new |
| 13 |
> SeaMonkey. |
| 14 |
> |
| 15 |
> It's also possible to use export/import instead of backup/restore, but |
| 16 |
> backup/restore creates and uses a json file, whereas export/import |
| 17 |
> creates and uses an html file. Less info is lost with the json |
| 18 |
> file. But note that using restore will overwrite existing bookmarks. |
| 19 |
|
| 20 |
There’s nothting wrong in copying places.sqlite itself. That way, you can |
| 21 |
also backup your entire history. Of course, the file is also a bit bigger |
| 22 |
because of that. |
| 23 |
-- |
| 24 |
Gruß | Greetings | Qapla' |
| 25 |
Please do not use my email addresses within any Facebook service. |
| 26 |
|
| 27 |
GNU jokes are not Unix jokes. |
Archives