We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
PID(s) should easily be identifiable on the system running spotlightify.
How it should look on Linux CLI
mark@DESKTOP-V5FN9GN:~$ ps -ef | grep "spotlightify" | grep -v grep mark 47 46 0 15:54 tty1 00:00:00 spotlightify
Having it like this will let you kill troublesome running sessions without unintentionally killing your IDE session, or the Python session.
Suggestion:
Use the os module, it has methods like os.getpid() to retrieve the PID.
The text was updated successfully, but these errors were encountered:
Identified that this process isn't not a straight cut one. For *nix based devices using this module, but this isn't cross platform like this.
@wllkle @petergmurphy what do you guys think?
Sorry, something went wrong.
No branches or pull requests
PID(s) should easily be identifiable on the system running spotlightify.
How it should look on Linux CLI
mark@DESKTOP-V5FN9GN:~$ ps -ef | grep "spotlightify" | grep -v grep mark 47 46 0 15:54 tty1 00:00:00 spotlightify
Having it like this will let you kill troublesome running sessions without unintentionally killing your IDE session, or the Python session.
Suggestion:
Use the os module, it has methods like os.getpid() to retrieve the PID.
The text was updated successfully, but these errors were encountered: