On 9/11/11 9:17 AM, Larry wrote:
> David E. Ross wrote:
>> On 9/8/11 1:49 PM, Larry wrote:
>>> David E. Ross wrote:
>>>> On 9/8/11 11:37 AM, Larry wrote:
>>>>> Just upgraded from 2.0.14 to 2.3.3. It went very well, and more quickly
>>>>> than I'd expected. Did have to adjust some link behavior to suit my way
>>>>> of doing things.
>>>>>
>>>>> Surprise--Based on comments in this group, I'd expected to have to
>>>>> retrieve my bookmarks. Was surprised to find my previous home page
>>>>> (bookmarks.html) was right there, ready to use!
>>>>>
>>>>> Frustration--Said home page now has all entries hard against the left
>>>>> margin, usable but not comfortable to read.
>>>>>
>>>>> Problem?--On the bookmark page, the links "Recently Bookmarked" and
>>>>> "Recent Tags" fail with the message "place is not a registered protocol".
>>>>>
>>>>> Any suggestions or observations would be appreciated.
>>>>>
>>>>> Larry
>>>>
>>>> Do you want your home page to be your bookmarks file (as I do)? Let me
>>>> know here, and I will give you the steps to make it look nice and to
>>>> keep it current.
>>>>
>>> Yes, I'd appreciate that!
>>>
>>> Larry
>>
>> Actual bookmarks are now contained in the SQLite database places.sqlite.
>>
>> First, keep your bookmarks file current. Set the preference variable
>> browser.bookmarks.autoExportHTML to "true". This will cause SeaMonkey
>> to export your bookmarks from places.sqlite into file bookmarks.html
>> every time SeaMonkey terminates.
>>
>> You can do this by entering about:config in the address area of
>> SeaMonkey and entering browser.bookmarks in the Filter area. If you see
>> the complete preference variable with the value "false", double-click on
>> it to toggle it to "true". If you don't see it, right-click in the
>> window and select [New> Boolean] in the pull-down context menu. Then
>> enter browser.bookmarks.autoExportHTML and then true in the popup
>> dialogues.
>>
>> I prefer to set preference variables in file user.js in my profiles
>> (doing it in each profile). Locate your profile folder. If there is no
>> file named user.js create it as a text file. Edit it in an ASCII
>> editor, inserting
>> user_pref("browser.bookmarks.autoExportHTML", true);
>> // automatically export bookmarks into an HTML file
>> Note the semi-colon (;) at the end of the first line. The double slash
>> at the beginning of the second line indicates this is a comment, which
>> is why I prefer doing this in user.js -- I can annotate why I did it.
>> For changes in user.js to become effective, you must terminate and then
>> restart SeaMonkey.
>>
>> In any case, when you use Bookmarks Manager to update your bookmarks,
>> you can export your bookmarks. On the Bookmarks Manager menubar, select
>> [Tools> Export HTML]. That gives you the opportunity to export to any
>> HTML file (not merely bookmarks.html) in any directory (not merely your
>> profile), so be careful.
>>
>>
>>
>> Now we must deal with the appearance of the bookmarks as a home page.
>> In your profile, locate and open the folder named chrome; no, this is
>> not the same as the folder with that name in the SeaMonkey root
>> directory. If that folder does not already contain a file named
>> userContent.css, copy the file named userContent-example.css and rename
>> the copy to be userContent.css. Using an ASCII editor, insert the
>> following into file userContent.css:
>> /* Indent folders */
>> @-moz-document
>> url("file:///C:/xxx")
>> { body { margin-left: 2em !important}
>> h3 + dl { margin-left: 2em !important } }
>>
>> The first line is merely a comment. Change the xxx in the third line to
>> the path to your bookmarks.html file. Note that, in the fourth and
>> fifth lines, there are "curly" braces and not parentheses. This will
>> indent all bookmarks in your home page by 2em with additional
>> indentations for folders and subfolders within your bookmarks.
>>
>>
>> Finally, there are the unwanted (at least for me) entries for Recent
>> Bookmarks and Recent Tags and entries within Bookmarks Toolbar. Open
>> the Bookmarks Manager and simply delete them.
>>
> David . . .
>
> Thank you for the helpful advice. I've done the first part, but now have
> a question. You said:
>
> "copy the file named userContent-example.css and rename
> the copy to be userContent.css. Using an ASCII editor, insert the
> following into file userContent.css":
>
> I've copied and renamed it. Do I remove all the general advice that got
> copied from the example, or do I just insert your recommended language
> in the file ahead of (or after?) the advice language? Should it have the
> left margin as in your message? Then, do I just close out notepad, then
> the chrome folder, etc., or do I do something else to finish the job.
> Finally, will the change then be in effect,or do I restart?
>
> Sorry for all the questions and my minimal knowledge about this stuff!
>
> Larry
The general advise is merely a set of two comments that have no effect
on the use of the file. You may leave them or delete them.
A comment in a CSS file -- including userContent.css -- begins with /*
and ends with */. I'm not sure about leaving spaces between these
delimiters and the text of the comments, but I always leave such spaces
for the sake of readability. The asterisks at the beginning of each
line are not functional; they only serve make clear that the line is
part of a comment.
Comments are good! That is, they are good for us humans. They remind
us of what we did and why. That is why I prefer to make changes to
preference variables in user.js instead of going to about:config --
because I can insert comments in user.js. However, my first priority is
to use the Preferences user interface since that might include some
housekeeping about which I am not aware.
--
David E. Ross
<http://www.rossde.com/>
On occasion, I might filter and ignore all newsgroup messages
posted through GoogleGroups via Google's G2/1.0 user agent
because of spam from that source.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
