-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added an option to filter out system services #1
base: main
Are you sure you want to change the base?
Conversation
@tcptps: apparently you are assuming a certain macos version which works for your scenario; Apple states explicitly that the format generate by their tools like like On macos Ventura 13.0.1 your branch triggers an arrayIndex error because of string splitting on a separator that does not exist. For example, the output of
In any case, it's not clear what you want to achieve. There is a already a dropdown where you can select the launchd domain which includes |
@glowinthedark thx for the hint. I know that you arent supposed to parse the output but since it is pseudo parsed multiple times in the project anyways I didnt see any harm to add another function in the same spirit as the other ones.
I want to remove all jobs from the list that have |
With your last push there is still a Did you look through It might also be possible to filter the services indirectly via their path; according to the man page:
|
@glowinthedark I am sorry my bad, I simply missed the |
BTW I am unsure whether or not this is really a plist since afaik they are xml structured, even though I have heard of json like structured ones before I was never able to obtain a official documentation letalone a parser, I guess its an apple internal file format. |
the format is not a plist per se, ie, it's probably (just my guess) an unstable textual representation of internal structures such as If you look at
|
confirming that filtering works on ventura with latest push; there are still 4 indexed array index operations after split with no check for number of elements — could you please add checks for the length of the chunks to make sure it doesn't throw an index access error when preconditions fail? I'd also consider adding |
No description provided.