Do not Mend the Nemo to the core of Linux Mint please

[OneOfLosers]

For me thunar does the thing, the Problem when I install Dolphin want to get rid of nemo, the whole Mint breaks !!!
That is not the idea behind the whole Linux thing! Do not misinterpret it, I found out... oh I need Nemo too cause Dolphin, Thunar and all the rest suck at finding my "WDExt2" NAS !!! So you see where it goes, one FM is not enough, but it must not be the "driver" of my whole Desktop bone!

This is my experience as awlays noob in Linux since 1998, and this person had his 2 years before:
https://www.reddit.com/r/linuxmint/comments/1bdmeie/today_i_learned_that_removing_nemo_removes_the/

THIS must not happen at all, specially in this great distro, and I am full Linux-Mint since 3 weeks after teesting all the other distros 2 months before that !!! and yes, NixOs is the future, when we get rid of their "now" developers or their "now" mindset ...

my 2 cents

[billyswong]

In Windows, explorer.exe handles not just the file explorer windows but also the desktop background. The desktop background where you can place files on and open those files from there, is also an instance of explorer.exe

Similarly, in Cinnamon, the desktop background where you can place files there and open files from, is an instance of Nemo. So removing Nemo breaks Cinnamon DE. Thus, if you run a Cinnamon edition of Linux Mint, you shouldn't remove Nemo.

Xfce let Thunar be optional because they explicitly try to make things as modular as possible. But if you remove Thunar, you will lose file icons on desktop (see https://docs.xfce.org/xfce/xfdesktop/start)

[Fantu]

Perhaps if Cinnamon were modified so as not to have problems with the parts integrated with Nemo, it could be set as recommended instead of dependency, but I don't think that's something the Mint team would like to do.
Furthermore, I suppose it would open the door to more demands from users who want greater integration with other file managers.
Cinnamon and its components have some integration specific to Nemo, just as Nemo has it for Cinnamon.
If you use other file managers, in fact, you'll have some features missing and settings that don't work or match because they're tied to the DE. Not only are Cinnamon settings tied to Nemo, but also the other file manager's settings tied to its DE.

[OneOfLosers]

The issue is that if I then make a *.txt file it first only open in the Nemo Editor (0 sized) even if i set kate as std editor. After it is written, it then can be opens in Kate! So this is the other issue this tieing also causes. And even in open-with-part, it does not function, so you can assume the test-pc hell i had before installing the NB-Mints... Very interestingly, on both NB same approach in one kate is opens as i wish, in other the above scenario.

Still thx for answers and time.

Do you think you can rise mint to NixOs base with (later other init) and the local user env version? So we get the most packages, have the core handleed in the decl and the user can have his imp part in his home ?

best regards

[billyswong]

You mean an empty new file is opened in Xed only and not your preferred Kate? This issue is NOT due to Nemo (nor is it due to Xed). The issue is due to now zero-sized files are taken as application/x-zerosize, unlike the old days where they are taken as text/plain. For Kate to open zero-sized files by default, you need to setup Kate to be the default editor of application/x-zerosize as well.

[billyswong]

Some more background information on this issue
linuxmint/mint22-beta#26

Wow. It's been 2 years since that ticket. Time flies.

[OneOfLosers]

Ahhh, that's the issue, even MIs couldn't solve it, but they have not that long memory of github. Wondered why setting it so often still did not made a solution.

Ok. Still seems too inconsistent, and I can try to help mayself, so looking it from an only user view, this either must change or they will someday look for another distro on search for a solution.

Thx and regards.

[billyswong]

Ultimately this is yet another behavioural difference between the GNOME/GTK ecosystem vs KDE/Qt ecosystem.

https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3053
https://unix.stackexchange.com/questions/806054/linux-make-xdg-mime-guess-file-type-by-extension-when-file-is-empty

In the beta ticket I linked in last post, you can see that Mint devs workaround this problem by telling Nemo to create new files with non-zero size. But this trick obviously won't work if you use other file managers to create new files. File managers and text editors written for KDE/Qt ecosystem obviously won't care the quirks of GNOME/GTK ecosystem.

[OneOfLosers]

thx for your informative replays. Hope they can find a solution. Still i stick to Mint, it works, stable if one is not good at NixOs :)

[Fantu]

I think you're confusing it with other programs, Nemo is not an editor but a file manager

you should rather see the problems and solve them but from the things you say it seems to me that you have difficulty providing clear information to help solve any bugs in Nemo (or other programs), unless they are due to unforeseen events caused by what you use

[OneOfLosers]

sry you are wrong, you view-scope is too small, cause you are too deep in the "problem" maybe not the solution as a "professional", if you get my point!?!

billyswong
3 days ago
Some more background information on this issue
linuxmint/mint22-beta#26