asimov icon indicating copy to clipboard operation
asimov copied to clipboard

installation location for .plist

Open ajoslin103 opened this issue 4 years ago • 2 comments

Shouldn't the .plist file be copied to ~/Library/LaunchAgents and then be loaded from there?

I know that it technically works when it's loaded from within the project folder, but doing so goes against the grain -- and may be silently disallowed by Apple at some point in the future.

ajoslin103 avatar Oct 13 '19 19:10 ajoslin103

That's a very good question, and definitely worth looking into.

Anyone have more experience with .plist files and care to weigh in?

stevegrunwell avatar Oct 16 '19 14:10 stevegrunwell

I use Lingon X (a very nice app for working with Launch Daemons and other automated processes)

When I asked him why Lingon didn’t see Asimov, he replied:

Well probably... I haven’t tried installing it by I can see that there is a launchd job included in it. While it is technically possible to run it from places where Lingon doesn’t see it, it is quite uncommon.

The apple docs say that the launchd startup process reads only from those locations

I don’t restart often but maybe asimov doesn’t restart it’s daily check because of this?

https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html

It loads the parameters for each launch-on-demand user agent from the property list files found in /System/Library/LaunchAgents, /Library/LaunchAgents, and the user’s individual Library/LaunchAgents directory.

btw: thanks for asimov - it saves me tons of space from my years of projects !!

ajoslin103 avatar Oct 16 '19 14:10 ajoslin103