Ubuntu-Mate 24.04, handle of files via caja on a external HDD-Drive, NTFS
A double-click of e.g.: mp4 (mkv)-files will open the respective video player of my choice.
Something like that I expect, if I open a txt-file (file-extension "txt").
But all ways I will asked what to do : Execute,
As if it is a "executable script".
Also the context menu entry does not exist : "open with pluma"
My mount-options e.g.:
mount -l
/dev/sda1 on /media/mnt/Samsung_2T_Ext type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [Samsung_2T_Ext]
Is it configurable, that txt-files will be opened like video-files, directly via double-click ?
Linux an Windows file permissions are somewhat different. When UM mounts an NTFS drive NTFS file permissions are mapped into Linux file permissions. As the result, every text file on the NTFS drive is considered to be an executable one.
And Caja treats text executable files (aka scripts) differently from legacy text files. And yes, you can configure what has to be done with such the files in Caja preferences.
Every file (mkv, mp3, ods, ...) get the executable flag on a NTFS system.
But all files will be automatically opened with the respective application (Vlc, Libre-Office-Calc a.s.o.), except txt-files.
@pavlos_kairis, obviously you can not imagine that a OS "have this association" via the respective setting, but it does neither give the "open with pluma" context entry, nor the expected behaviour via double click.
Is that so difficult to understand ?
I did upload a screenrecord with the respective file operation, first context menu, then via double click.
First in my home directory, then in the ext. NTFS drive.
I did check it, part of the file :
...
message/rfc822=evolution.desktop
inode/directory=caja-folder-handler.desktop
text/plain=pluma.desktop
audio/mpeg=rhythmbox.desktop
audio/x-mpegurl=rhythmbox.desktop
audio/x-scpls=rhythmbox.desktop
...
Perhaps, I will have again a "special" system (Asus Vivo Book with AMD, by my opinion a good Laptop).
Whether my system is a special or not, another user with an old USB drive, format it as NTFS, and check if the same error can be reproduced. If, yes, I will create a bug report on launchpad., if not, I have to live with it.
Sometimes, the OS install just doesn't do everything because of a "glitch". It happens, for whatever reason, because of some unique condition the install encountered, relating to your unique context.
In some cases, the failsafe is to not do anything at all, leave things alone, without establishing a "preset".
So, given that ... what Pavlos outlined as the manual post-installation "repair" is a minimum, mandatory intervention to get to where you want to be.
There is no need to insult people, especially if you had taken the time to scan the Community's postings to see that Pavlos is
VERY knowlegeable,
VERY helpful, and especially,
VERY on-point,
when it comes to his contributions to any issue!
You may want to revisit you posting and retract you "barbs".
for the file that is not triggering the Pluma session you are expecting.
The result may give a hint as to how the system is classifying the file, which may explain the reason why Pluma is not one of the default offerings for "double-click" or "right-click". It might be reacting to rule which is different than what you are expecting.