Last Comment Bug 276943 - [FIX] I want to open ONLY composer
: [FIX] I want to open ONLY composer
: helpwanted
Product: SeaMonkey
Classification: Client Software
Component: Installer (show other bugs)
: unspecified
: x86 All
-- normal (vote)
: mozilla1.8beta1
Assigned To: Benjamin Smedberg [:bsmedberg]
: Henrik Gemal
Depends on: 272144
  Show dependency treegraph
Reported: 2005-01-03 17:49 PST by arinkleff
Modified: 2005-02-14 11:50 PST (History)
5 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

Package the JS commandline handler (2.26 KB, patch)
2005-01-30 16:19 PST, Benjamin Smedberg [:bsmedberg]
timeless: review+
Details | Diff | Splinter Review

Description User image arinkleff 2005-01-03 17:49:34 PST
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 User image Stefan Borggraefe 2005-01-03 18:01:55 PST
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
Comment 2 User image arinkleff 2005-01-03 18:16:33 PST
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 User image Mats Palmgren (:mats) 2005-01-03 23:43:27 PST
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 User image Stefan Borggraefe 2005-01-04 00:18:29 PST
(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 User image Mats Palmgren (:mats) 2005-01-04 01:28:15 PST
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
(into an empty directory) does not work.

-> Installer (for further triage)
Comment 6 User image Andrew Schultz 2005-01-04 09:06:24 PST
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 User image Benjamin Smedberg [:bsmedberg] 2005-01-04 09:12:04 PST
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 User image Benjamin Smedberg [:bsmedberg] 2005-01-30 16:19:03 PST
Created attachment 172917 [details] [diff] [review]
Package the JS commandline handler
Comment 9 User image 2005-01-30 16:31:54 PST
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 User image Benjamin Smedberg [:bsmedberg] 2005-02-07 05:22:54 PST
Fixed on trunk.

Note You need to log in before you can comment on or make changes to this bug.