That's weird. Are you sure those files aren't empty? e.g. do they have a file length? Maybe it's just the file associations that got messed up? Do you use KDE or GNOME?sprocket_dk wrote:Hej I can't seem to open txt files. When I double click on a txt file nothing happens. Am I missing some program here?
Huh??? On which OS and from which parallel Universe?Husse wrote:Files with a .txt file association tend to be treated as executable text files
your problems are surprising, or I misunderstand you (that is always possible)Husse wrote:
Files with a .txt file association tend to be treated as executable text files
Huh??? On which OS and from which parallel Universe?
:)Pas de f***ing kidding, I had the very same thoughtlinuxviolin wrote: your problems are surprising, or I misunderstand you (that is always possible)
Yes, because there those files (and everything else) get the execute bit set unless you set the "noexec" parameter or use a proper Linux filesystem which is able to report the correct bit settings (rwx ..) to the system. This has not really something to do with the *.txt files being really 'executable' but rather how Linux is interpreting stuff from non-Linux filesystems.Husse wrote: something.txt comes from my ntfs partition so that may be it...
Maybe they originate from Windows or some other non-UNIX-like OS? Could be then that somehow that execute bit got preserved.Husse wrote: Yaeh - that's it, but I've got some .txt files not coming from ntfs being like that too....
Husse wrote: So much so that it's been annoying
Code: Select all
find . -name *.[Tt][Xx][Tt] -type f -print -exec chmod 644 {} \;