I think you might be looking for these:
https://developer.mozilla.org/en/Command_Line_Options

But as far as -remote saveAs(...) goes that must of been removed a long time ago or never implemented in Firefox. Btw what does that command do? Download a file as soon as the browser opens? Seems like it would be easier to open Firefox, paste the link, then download the file rather than editing a command line to do that.

I used a make-like process of my own making to run the following commands for many manuals and for each section of my book

( http://www.qef.com/guide/pages/*.html )

     netscape -remote 'openURL(<url>)'  # load section
     sleep 5 # give netscape time to load pages
     netscape -remote 'saveAs(<file>,PostScript)' # dump url as postscript

I then could easily manipluate the PS files to add page numbers, modify the TOC and the keyword index to use those numbers. I just said:

      qef Proof

and poof -- we have a book ready for printing.

I guess it's my fault as I chose to use the browser to produce the book and expected features to stay in place.

Note: I did not write it in html!!! -- but that's another story (an Irma la Douce / Moustache reference).

Doing this manually is a way more irritating, error, and boredom prone interaction than my 10 character command.

All I want is a non-interactive way to dump the current url with the current geometry (yes I did have to set page size, but that's just a single shell command -- no interaction or mousing around) to a postscript file -- something that is easily supported given that the conversion of the current page to postscript is inherent in the print command.

Any suggestions?

-- david (sometimes identified by his mustache see

   http://www.qef.com/html/washington.html )

P.S.: I have used the same process to produce all sorts of manuals, until some bright-light decided that saveAs wasn't necessary.

Looks like it is handled in this part of the source code (no mention of safeAs):

• http://mxr.mozilla.org/mozilla-central/source/browser/components/nsBrowserContentHandler.js

Looks like I'm out of luck.

-- david