@@ -42,34 +42,34 @@ + (NSError*)warnUserIfLaunchdHangInTaskResult:(NSInteger)result
42
42
if ((result != 0 ) && ([error code ] == SSYShellTaskerErrorTimedOut)) {
43
43
/*
44
44
This method was changed in BookMacster 1.14.4. I've had a couple
45
- reports from Mac OS X 10.8 users, and I saw this happen once myself,
46
- but unlike the restart that was necessary to fix it in Mac OS X 10.7,
45
+ reports from macOS 10.8 users, and I saw this happen once myself,
46
+ but unlike the restart that was necessary to fix it in macOS 10.7,
47
47
it now seems to fix itself. So Apple didn't really fix it, but they
48
48
made it enough better that we don't want to annoy the user with the
49
49
warning any more.
50
50
*/
51
51
NSTimeInterval timeout = [[[error userInfo ] objectForKey: constKeySSYShellTaskerTimeout] doubleValue ] ;
52
52
NSLog (@" Warning 516-7625 launchctl timed out at %0.1f secs." , timeout) ;
53
- NSString * reason = @" The launchd process of Mac OS X is not responding." ;
53
+ NSString * reason = @" The launchd process of macOS is not responding." ;
54
54
NSString * suggestion = @" You should restart your Mac at the next opportunity. "
55
55
@" This bug has reportedly been fixed by Apple in Mac OS 10.8 (Mountain Lion)." ;
56
56
error = [error errorByAddingLocalizedFailureReason: reason] ;
57
57
error = [error errorByAddingLocalizedRecoverySuggestion: suggestion] ;
58
58
59
59
if (NSAppKitVersionNumber < 1187.370000 ) {
60
60
// The above condition was added in BookMacster 1.14.4.
61
- // The above number is for Mac OS X 10.8.3. I'd like to use the
61
+ // The above number is for macOS 10.8.3. I'd like to use the
62
62
// number for 10.8.0, but can't find that. It doesn't matter that
63
63
// much, oh well.
64
64
// The reason for the condition now, is that this launchd thing
65
- // seems to fix itself after some time in Mac OS X 10.8. It no
65
+ // seems to fix itself after some time in macOS 10.8. It no
66
66
// requires a restart
67
67
NSString * message = [NSString stringWithFormat: @" %@ \n\n %@ " ,
68
68
reason,
69
69
suggestion] ;
70
70
71
71
NSString * windowTitle = [NSString stringWithFormat:
72
- @" %@ : Problem with Mac OS X " ,
72
+ @" %@ : Problem with macOS " ,
73
73
[[NSProcessInfo processInfo ] processName ]] ;
74
74
CFUserNotificationDisplayNotice (
75
75
60 , // timeout
@@ -90,7 +90,7 @@ + (NSError*)warnUserIfLaunchdHangInTaskResult:(NSInteger)result
90
90
91
91
// launchctl itself has a built-in timeout of 25 seconds (Mac OS 10.6.6).
92
92
// So, anything over 25 seconds will act like 25 seconds. However, on
93
- // 20120428 launchctl got into some weird state in Mac OS X 10.7.3.
93
+ // 20120428 launchctl got into some weird state in macOS 10.7.3.
94
94
// Whenever I gave it a command to load or unload a job, it would hang
95
95
// indefinitely. So I reduced this in BookMacster 1.11 from 180.0 to
96
96
// 35.0 seconds.
@@ -471,7 +471,7 @@ + (pid_t)pidIfRunningLabel:(NSString*)label {
471
471
NSString * trimmedResponse = [response stringByTrimmingCharactersInSet: [NSCharacterSet whitespaceAndNewlineCharacterSet ]] ;
472
472
/*
473
473
The following line was fixed in BookMacster 1.17 so that it works
474
- if fields are separated by tabs (as they are in Mac OS X 10.8)
474
+ if fields are separated by tabs (as they are in macOS 10.8)
475
475
instead of spaces. Maybe they were spaces in an earlier OS X
476
476
version? Anyhow, we handle either now.
477
477
*/
@@ -827,4 +827,4 @@ + (BOOL)tryAgentLoad:(BOOL)load
827
827
}
828
828
829
829
830
- @end
830
+ @end
0 commit comments