Switching from Budgie Desktop View to Nemo Desktop

Are there already plans to add nemo-nextcloud integration?

I was also missing the nextcloud extension "open in other terminal", but found that there is a better solution with nemo by configuring it with below command (for using alacritty)

gsettings set org.cinnamon.desktop.default-applications.terminal exec alacritty

palto42 add nemo-nextcloud integration?
Just found that the current nextcloud-client package just removes the nemo integration, so fix seems to be simple Will build it locally and try...

palto42 gsettings set org.cinnamon.desktop.default-applications.terminal exec alacritty

I used same command to switch to tilix

Just done the weekly update and have changed over to Nemo. Enjoying the experience so far, congratulations on your choice. Also another update to the kernel. You guys rock!
One silly thing I have noticed is that Ventoy (VentoyGUI.x86_64) does not want to run from Nemo. It will run by clicking on the file and then typing the password if I use Nautilus so I have installed both side by side for the moment as a workaround. Pretty sure that I have used Ventoy on Linux Mint, which also uses Nemo, without any problems.
Any suggestions would be much appreciated.

Hi,

How can we hide the desktop icons after switching to nemo ?

Cheers,
PY

BuzzPCSOS I'm going to answer my own question here to save anyone else wasting time on it.
To run Ventoy, Nemo must be running as root (right click in a folder and pick 'run as root' from the dropdown).
So simple, must have done that before and then forgot. Got so comfortable with Solus the way it was.
I hope this might be helpful for anyone else who might get caught by the different way root is handled by Nemo in some instances.

All good here, and pretty painless. Bookmarks, custom folder icons, etc., all were as before. Happily, it wasn't necessary to recreate any of that (I tend to rely on custom folder icons to help quickly navigate in the file manager, and have them all over the place).

All previous scripts continue to work fine, after a straight copy from ~/.local/share/nautilus/scripts to ~/.local/share/nemo/scripts.

Nice to have stuff back that was falling off nautilus, e.g. the gtkhash extension.

I like the pin/unpin facility in Nemo, that will let you pin a selection of files/folders to the top of the file listing, and retain it across sessions. Very likely that I'll use that a lot. (I don't remember Nautilus ever having that, even before it started to shrink in capabilities?)

And the Desktop is way more useful now

Great job, @EbonJaeger and anyone else involved!

Reading this thread has been a big relief. I am absolutely enjoying the Solus Mate life but will be back when the new budgie ISO comes.

Thanks for the long awaited option!

Solarmass It is funny how appimages will prompt for a root password but the Ventoy software will not when run on Nemo. Changing Nemo to root is very easy so all I have to worry about is not closing out of root when I have finished with Ventoy.

BuzzPCSOS

I don't remember how I run it last time on Nautilus, probably with root too. I just checked it asks for root in popup in Nautilus. You can bug-report it on Ventoy github..

BuzzPCSOS It is funny how appimages will prompt for a root password

the appimage peeps reccomend [per their official website] you change the permissions right after you download an appimage so it won't prompt you for sudo ever again.

BuzzPCSOS but the Ventoy software will not when run on Nemo.

I read this a few times and still don't know what you mean. The software doesn't' 'run' per se, it's a storage formatting program (maybe you are right) that you can either mount, open, and see your .isos. Or not? You are saying you need permission just to get Nemo to recognize Ventoy usb? Or to open it? And if that's true I wonder if its another permissions problem.

BuzzPCSOS How exactly do you run ventoy?
I tried it this way and it is working fine.