![]() |
Solved: Terminal Blocking Flexibility - Printable Version +- FocusMe Community (https://community.focusme.com) +-- Forum: Categories (https://community.focusme.com/forumdisplay.php?fid=1) +--- Forum: Suggestions and Feedback (https://community.focusme.com/forumdisplay.php?fid=4) +--- Thread: Solved: Terminal Blocking Flexibility (/showthread.php?tid=6) |
Solved: Terminal Blocking Flexibility - Lazuli - 06-18-2018 I've been using FocusMe for a few months now, and I've run into a consistent problem. I do simulations and programming work for my job and, while I don't use Terminal too often in my day-to-day, I do need to have it available on a moment's notice. I certainly can't afford to have it locked away behind the stringent requirement that all my plans be inactive - at least not if I expect them to be at all useful. The problem, of course, is that killing a process from the command line is super easy. That's something you definitely can't "fix" directly. What I think you could possibly do, however, is allow blocking of Terminal as part of a plan (as part of applications? or separately). Even just being able to pause Terminal blocking would be valuable for me. Of course, if I allow myself any access to the Terminal at any point, I will be able to kill FocusMe regardless, but if anyone knows the value of artificially increasing complexity as a defense against procrastination, it's your team. RE: Terminal Blocking Flexibility - jon - 06-18-2018 (06-18-2018, 06:00 AM)Lazuli Wrote: I've been using FocusMe for a few months now, and I've run into a consistent problem. I do simulations and programming work for my job and, while I don't use Terminal too often in my day-to-day, I do need to have it available on a moment's notice. I certainly can't afford to have it locked away behind the stringent requirement that all my plans be inactive - at least not if I expect them to be at all useful. Hi Lazuli! You can certainly block Terminal as part of a plan, instead of using the general setting to block when any plan is active. Simply disable the global Block Terminal setting and in a new plan add an application block for Process name = Terminal You can then set a deterrent on this plan such as a long random password, but you will be able to stop it if you really need to access terminal for your work. Hope this helps ![]() |