Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I went away for 10 days and during this time I had time to use both software (Commander One and Forklift, so what can I say. I think that Commander One surpasses Forklift with its seamless dual-pane interface, advanced file management features, and cloud integration. It provides a faster and more efficient file navigation experience. Perhaps everybody use software differently, and someone sees advantages from personal use that differ from the opinion of others
 
I haven't read through the entire thread, so I apologize if this has been brought up before. Marta is a free file manager for macOS that I just found. I thought maybe someone else would find it useful.
 
Marta has been brought up. Note that the search button (a loupe) on top of the screen has a popup that allows you to specifically search this thread without having to read through the entire thread before randomly posting your favorite software.
 
  • Like
Reactions: JustAnExpat
I tried Marta and found it to be unbearable to use. The fact that there is no GUI for the preferences alone makes it a non-starter for me. I'm sure it has many powerful features, but it's about as un-Mac-like as you can get.

Still, it's always good to have options, and Marta may fit the style of many users.
 
Is there a macro or some automated code that can kill Finder every time it restarts? Surely that can be possible.
Please review the information on the following links:



The command to kill the Finder is explained in these two posts, but you will probably have to create your own macro, maybe with Automator, to kill the Finder upon restart. (It isn't clear to me what happens on restart after you issue the "killall Finder" command.)
 
Last edited:
Please review the information on the following links:



The command to kill the Finder is explained in these two posts, but you will probably have to create your own macro, maybe with Automator, to kill the Finder upon restart. (It isn't clear to me what happens on restart after you issue the "killall Finder" command.)

I have some PM's from readers here with some ideas on how to keep the finder killed. I am going to try these UNIX commands to see if the Finder can be once and forever stopped from running.
 
Is there a macro or some automated code that can kill Finder every time it restarts?

Not a great idea. Just one example - without Finder apps won't be able to open files as there would be no finder dialogue.
 
I remember that Path Finder used to have an option to quit Finder. Path Finder provided the all the functionality that Finder would have.
 
I remember that Path Finder used to have an option to quit Finder. Path Finder provided the all the functionality that Finder would have.
Path Finder still allows you to Quit the Finder via the PF preferences. Forklift also will replace the Finder, but you have to use the Terminal to enter codes to do the same.

Not a great idea. Just one example - without Finder apps won't be able to open files as there would be no finder dialogue.
Quitting the Finder doesn't affect anything other than opening windows in the Finder. All other apps operate normally.
 
  • Like
Reactions: gregmac19
Quitting the Finder doesn't affect anything other than opening windows in the Finder.

When you quit the Finder it automatically respawns. How could you keep that from happening in order to test? I assume that the "file open" window used by applications is generated by Finder and if it isn't running ...
 
When you quit the Finder it automatically respawns. How could you keep that from happening in order to test? I assume that the "file open" window used by applications is generated by Finder and if it isn't running ...
I'm not sure why it "respawns" for you, but it doesn't for me. Never has. I have to click the Finder icon in the Dock to relaunch it.

In any case, the code used by these apps actually intercepts any call for Finder windows (or other related tasks) and re-directs them to the app. Some things don't work, like "Empty Trash" or seeing items on the Desktop (which is to be expected).
 
I'm not sure why it "respawns" for you, but it doesn't for me. Never has. I have to click the Finder icon in the Dock to relaunch it.

When you kill it the process is respawned. You can see it in Activity Monitor, the process PID will change. With the process running application file operations, I assume, proceed normally. When you click on the Finder icon that just starts a new Finder Window "instance", it does not affect the Finder process which is running in the background. Putting it another way Finder is sort of a background file management program. It also generates finder windows if you ask it to buy clicking on the Finder icon.
 
When you kill it the process is respawned. You can see it in Activity Monitor, the process PID will change. With the process running application file operations, I assume, proceed normally. When you click on the Finder icon that just starts a new Finder Window "instance", it does not affect the Finder process which is running in the background. Putting it another way Finder is sort of a background file management program. It also generates finder windows if you ask it to buy clicking on the Finder icon.

When I stop Finder from Activity Monitor, it does not start again. If I kill it from the Terminal with the "killall" command, it does.

Use the following at your own risk. You can actually tell launchd to not start Finder at all with

launchctl unload /System/Library/LaunchAgents/com.apple.Finder.plist

Logging out or rebooting will reverse that. If you add "-w" like so

launchctl unload -w /System/Library/LaunchAgents/com.apple.Finder.plist

then Finder will stay disabled across reboots and logins. The "load" command reverses the "unload".

Be aware that if you use the "-w" version, you'd better know how to launch Terminal without Finder if you want to reverse that change. Perhaps put it in the dock or use spotlight to launch it.
 
My Finder does NOT respawn. I understand what you're saying, but that's simply not the way it works (for me, anyway). Perhaps it's because I'm quitting the Finder, not Force Quitting and not using the Kill command in the Terminal. I have no idea, but I can open Activity Monitor, then quit the Finder (clicking on the desktop and hitting Command+Q) and it disappears from the Activity Monitor list and does not reappear until I click the Finder icon in the Dock to "relaunch" it.

The only thing I can think of is that I have Onyx installed and have the "Show Quit Finder" option turned on:

SCR-20230901-inum.png
 
  • Like
Reactions: it wasnt me
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.