Re: Efficient searching Seamonkey -- reoganizing tool?

2019-05-12 Thread Hartmut Figge
Richard Owlett: >I'm looking for a solution [short of a time machine] to properly >organize my bookmarks. Well, you have one solution for this directly before your nose. *fg* Export your bookmarks as HTML, make a backup, import them in the composer of SM, manipulate them e.g. by moving with

Re: Efficient searching Seamonkey -- reoganizing tool?

2019-05-12 Thread Richard Owlett
On 05/12/2019 01:26 PM, Hartmut Figge wrote: EE: Use folders to categorize your bookmarks. That makes them easier to find. The point is finding those folders when searching. Hartmut ( *ROFL* ) ** [Avogadro's number)**(6.23*10**23);/ ! I agree with everyone so far. I'm looking for a

Re: Efficient searching Seamonkey -- reoganizing tool?

2019-05-12 Thread Hartmut Figge
EE: >Use folders to categorize your bookmarks. That makes them easier to find. The point is finding those folders when searching. Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org

Re: Efficient searching Seamonkey -- reoganizing tool?

2019-05-12 Thread EE
Richard Owlett wrote: Over the last decade bookmarks.html has grown to >1.8MB [When examined via ^U - it has ~6k lines] SeaMonkey can search for sub-string(s) in a bookmark. *BUT* it does not return any information about (sub)heading it is under making it difficult to locate logically related

Re: Efficient searching Seamonkey -- reoganizing tool?

2019-05-12 Thread Paul B. Gallagher
Richard Owlett wrote: Over the last decade bookmarks.html has grown to >1.8MB [When examined via ^U - it has ~6k lines] SeaMonkey can search for sub-string(s) in a bookmark. *BUT* it does not return any information about (sub)heading it is under making it difficult to locate logically related

Efficient searching Seamonkey -- reoganizing tool?

2019-05-12 Thread Richard Owlett
Over the last decade bookmarks.html has grown to >1.8MB [When examined via ^U - it has ~6k lines] SeaMonkey can search for sub-string(s) in a bookmark. *BUT* it does not return any information about (sub)heading it is under making it difficult to locate logically related material. Has anyone