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?
*.txt files
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Re: *.txt files
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
- linuxviolin
- Level 8
- Posts: 2081
- Joined: Tue Feb 27, 2007 6:55 pm
- Location: France
I have no problem to open the .txt files with the text editor... your problems are surprising, or I misunderstand you (that is always possible)
K.I.S.S. ===> "Keep It Simple, Stupid"
"Simplicity is the ultimate sophistication." (Leonardo da Vinci)
"Everything should be made as simple as possible, but no simpler." (Albert Einstein)
"Simplicity is the ultimate sophistication." (Leonardo da Vinci)
"Everything should be made as simple as possible, but no simpler." (Albert Einstein)
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 {} \;