Closed Bug 60865 Opened 24 years ago Closed 24 years ago

xremote should return a different error code for window not found vs. error

Categories

(Core Graveyard :: X-remote, defect, P3)

x86
Linux

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: blizzard, Assigned: blizzard)

Details

When you use mozilla -remote there's no way to tell if it was because the window
was not found or if it was because there was an error on the server.  To build a
decent launcher script I need this functionality.
Index: nsAppRunner.cpp
===================================================================
RCS file: /cvsroot/mozilla/xpfe/bootstrap/nsAppRunner.cpp,v
retrieving revision 1.250
diff -u -r1.250 nsAppRunner.cpp
--- nsAppRunner.cpp     2000/11/07 08:04:06     1.250
+++ nsAppRunner.cpp     2000/11/22 23:09:35
@@ -1099,7 +1099,7 @@
       // was there a window not running?
       if (!success) {
         PR_fprintf(PR_STDERR, "No running window found.\n");
-        return 1;
+        return 2;
       }
       client->Shutdown();
       // success
Status: NEW → ASSIGNED
a=tor
sorry, been having SERA issues - I could have sworn I sr=alecf'ed this twice
already, guess it never went through :(
Nope, I never heard a peep.  Thanks!
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Component: XP Miscellany → X-remote
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.