276943 - [FIX] I want to open ONLY composer

Status: RESOLVED FIXED

(SeaMonkey :: Installer, defect)

Description

[arinkleff]

I want to use composer without opening mozilla -- I do not like having the same
document open twice, its annoying to have to close it twice.

Comment 1

[Stefan Borggraefe]

You can either use the -editor command line switch or use the option in the
Appearance pane of the Preferences dialog. Marking WORKSFORME.

Please read http://www.mozilla.org/quality/bug-writing-guidelines.html

Comment 2

[arinkleff]

command line switch??????????? The option in the appearance pane doesn't work --
i have it set to only open composer, but it opens mozilla anyways (and doesn't
open composer).  

Comment 3

[Mats Palmgren (inactive)]

Confirming bug, 2005-01-02-06 trunk Linux.
"mozilla -editor" opens a Navigator window.
Appearance pref. "Composer"  => Navigator window (only)
Appearance pref. "Composer+Navigator" => Navigator window (only)

Comment 4

[Stefan Borggraefe]

(In reply to comment #3)
> Confirming bug, 2005-01-02-06 trunk Linux.
> "mozilla -editor" opens a Navigator window.
> Appearance pref. "Composer"  => Navigator window (only)
> Appearance pref. "Composer+Navigator" => Navigator window (only)

All these things WFM with the exact same build, with the latest gtk2 nightly
2005010311 and with my self-compiled gtk2 build from yesterday.

Please make sure you don't add a -P command line switch when testing this,
because then you run into Bug 58523.

Comment 5

[Mats Palmgren (inactive)]

I did not use -P when testing.
I can confirm that the 2005-01-03-11 gtk2+xft nightly is working fine.
I retested 2005-01-02-06 with a completely empty HOME, e.g:

mkdir /tmp/bla
HOME=/tmp/bla /usr/local/mozilla/mozilla -editor

still does not work.
Now, here's the funny thing - if I install 2005-01-02-06 from the
"mozilla-i686-pc-linux-gnu.tar.gz" and retry the above it does work!
However, an installation (complete) from the
"mozilla-i686-pc-linux-gnu-full-installer.tar.gz"
(into an empty directory) does not work.

-> Installer (for further triage)

Comment 6

[Andrew Schultz]

this regressed between linux trunk 2004102906 and 2004103005, which is the
landing of bug 237745. But I don't know/why how that would single out the
intsaller build.

Comment 7

[Benjamin Smedberg]

I do. The composer command line handler was turned into a JS component, and that
needs to be packaged in the installer manifests.

Comment 8

[Benjamin Smedberg]

Attachment: Package the JS commandline handler

Comment 9

[[e-mail]]

Comment on attachment 172917 [details] [diff] [review]
Package the JS commandline handler

Sorry, this is way out of my area. I don't even know if the package lists
should be grouped in any way (list the .js file near composer.dll perhaps?)

Comment 10

[Benjamin Smedberg]

Fixed on trunk.