Felix Miata wrote:
I suggest expanded description of use of -safe-mode in Linux, essentially as 
follows:

--- old 2017-07-31 02:45:13.000000000 -0400
+++ new 2017-07-31 23:16:29.478433887 -0400
@@ -327,9 +327,10 @@
     appearance, degraded performance, etc, you may be suffering from Extension
     or Theme trouble.
     Restart SeaMonkey in Safe Mode. On Windows, start using the "Safe Mode"
-    shortcut created in your Start menu or by running
-    <code>seamonkey.exe -safe-mode</code>. On Linux, start with
-    <code>./seamonkey -safe-mode</code> and on Mac&nbsp;OS&nbsp;X, run:
+    shortcut created in your Start menu or by running <code>seamonkey.exe 
-safe-mode</code>.
+    On Linux, start with <code>/path-to-seamonkey/seamonkey -safe-mode</code> 
or first
+    change to the SeaMonkey installation directory and start with <code>./seamonkey 
-safe-mode</code>,
+    and on Mac&nbsp;OS&nbsp;X, run:
     <p><code>
        cd /Applications/SeaMonkey.app/Contents/MacOS/<br>
        ./seamonkey-bin -safe-mode

WDYT?

Just a few thoughts...

Why not just include a link to <http://kb.mozillazine.org/Safe_Mode#Starting_Safe_Mode> for instructions on starting safe mode, rather than duplicating them in the release notes every release?

Since expecting people to read release notes often seems to be asking a bit much, perhaps expecting them to follow a link from the release notes is asking the impossible ;o) So...

If it's going to be in the release notes, it may be better to keep it short and simple. Just describe one way - either using the full path /or/ cd and then ./seamonkey - not both. And whichever way is shown, show the equivalent for Mac. The mozillazine page above uses the full paths, so perhaps go with that for consistency. Perhaps also put Linux and Mac in separate sentences, rather than running them together in a single sentence.

--
Mark.

_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to