How come the LQ Attachment Uploader doesn't support shell scripts, in particular in blog entries? Since it doesn't, I have to keep updating the link to my Linux Kernel Build Script every day, since the site it is hosted on autogenerates the links!

Hi Kenny,

The attachment uploader filters by filetype (based on extension) so if you want to attach a shell script, you must give it's name a .txt extension. Even though this extension has no bearing on whether or not the script will run, you might add a note to the blog entry, or to the script's #comments, telling people they can/should rename the file to 'whatever.sh' or simply 'whatever', rather than 'whatever.txt' if they wish.

Even a script with no extension will then require a .sh or .txt extension added to it in order to upload. I don't really know how most people name their scripts, but I don't always use a .sh extension for mine.

For the record, since .txt files are allowed by the uploader, I think it would be OK to put a provision for .sh files too (Jeremy, what say you?) since they are merely text files anyway.

Agreed, and I'd add .patch/.diff files. (I had to upload a patch as .txt today and found this thread because I was about to start one of my own asking for the same thing.) What would be better is to run file on it (or equivalent) to check by magic rather than extension. Either way, people are going to want to upload non-.txt text like c, sh, and patches a lot.