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

RESOLVED FIXED

Status

()

Core
X-remote
P3
minor
RESOLVED FIXED
17 years ago
16 years ago

People

(Reporter: blizzard, Assigned: blizzard)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

17 years ago
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.
(Assignee)

Comment 1

17 years ago
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

Comment 3

17 years ago
a=tor

Comment 4

17 years ago
sorry, been having SERA issues - I could have sworn I sr=alecf'ed this twice
already, guess it never went through :(
(Assignee)

Comment 5

17 years ago
Nope, I never heard a peep.  Thanks!
(Assignee)

Comment 6

17 years ago
Fix checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Updated

16 years ago
Component: XP Miscellany → X-remote
You need to log in before you can comment on or make changes to this bug.