Creating a new text file in the Finder
When switching from one operating system to another, sometimes it's not obvious how to do something that was straightforward to do on the previous OS.
As someone who switched from Windows to a Mac a couple of years ago, I was able to find easy solutions to most of the things that I originally struggled with. But there is one irritant that has stuck around for the past two years, and though I've found various workarounds, it's still unclear to me why OS X has this gaping hole in the functionality of the Finder.
The issue I'm talking about is the Finder's inability to create a file, specifically a text file, in the folder the user is actively viewing. There are lots of reasons that you might want to quickly drop a text file into a folder, and for some reason Apple thinks that if you want to do this, you should open a text editor, create the file, then save it and re-navigate to the folder that you were already looking at in the Finder.
Though the Finder can't do this simple task, there is a way to make it pretty straightforward with the use of an Applescript compiled as an executable app. Download this newtextfilehere.zip file hosted on Droplr, and unzip it into a folder where you can trust it won't be deleted. Then, viewing that folder, simply drag the newtextfilehere.app file up to the Finder's toolbar, where you'll see a script icon added. Now, clicking this icon will automatically create an empty text file called new.txt in whatever folder you happen to be viewing. Simply double-click the new file to edit it, and you're done.
[via storiesofmac]












Comments
13
Subscribe to commentsWill NeaversonJan 14th 2010 5:25AM
Very useful - thanks!
DuckJan 13th 2010 6:51PM
Oh that's a nice tip.
Being a long time Mac User, I never really felt the need to do that, it's one of those things that you do on Windows, then when you're on the Mac you want to do it.
I'd also like to add: Thanks for writing a (mostly) unbiased article rather than hating on Mac :P
Sgt ZeppelinJan 13th 2010 7:38PM
Other good options include Nufile (http://growlichat.com/NuFile.php), Document Palette (http://www.coldpizzasoftware.com/documentpalette/), and FinderPop (http://www.finderpop.com/). I know FinderPop has a SL compatible beta available, and I believe the others already work on SL.
Personally the new file feature is not one that I've ever used (or missed!), but it's good to know that there are always ways to add features you want.
DavidJan 14th 2010 2:23AM
I miss this very much and humbly thank you for posting this.
MikeJan 14th 2010 8:06AM
I have been a Mac user for a long time. This idea I find ridiculous! Can someone explain what use this serves? If a Mac user needs to put a small note in the same folder as a file (perhap with a date or version number or some other piece of information), we create a sub-folder and name the folder with the information required. This way, you don't need to open an application to read it.
The only possible use for this I can see is if you are going to upload a file to bit-torrent and want to include a read-me. Fine, open your text editor, write the note and save it in the folder with the file.
This article is completely non-Mac.
Sgt ZeppelinJan 14th 2010 10:32AM
I don't think it's something a large percentage of users needs to do (on Windows or OS X), but I can see where there might be problems for the people that do.
I'm not blaming it on OS X though, because they were designed with a different set of ideas. Some of those ideas were the same, and some were similar, but a lot were different. It's these differences that give us a chance to find a system that works better for each of us.
And I wouldn't call this article non-mac, it's more of a complaint and tutorial to fix a problem some users might have with the way OS X handles creating new files. Not useful for you and me, but I'm sure it'll be a life-saver for some.
MikeJan 14th 2010 12:06PM
Well, since you think some people do it, why not give a few examples of why they are doing it? Personally, I find the idea completely ridiculous.
And, when I read the original author call this a "gaping hole in the functionality of the Finder", it clearly showed that the author has little understanding of computers or computing.
TheOneAndOnlyJHJan 15th 2010 8:21PM
I do this all the time. Yes, you could create a subfolder, but that only works if your note is a short sentance or phrase. If you want to write, say three or four sentances, a text file is much better. You can give a simple title (readme.txt) and to read, just open the text. Opening a text editor is painless and quick.
For example, I take lots of pictures on my camera. Instead of having to look through them each time to find the best shots to print (no blinking, all smiling, etc) I write a text file listing which files are the best. A subfolder named IMG_0027, IMG_0069, IMG-0072....... would be too long, and not as easy to read as a column of filenames. This way I can print out more copies when relatives request.
Also, I like to add a short description of where photos came from so I can zip up the folder and share it with relatives. A paragraph is short and concise, but would not be good as a subfolder name.
I also use .txt files for many other uses, and I couldn't imagine not being able to add a .txt file for a short note. Subfolder names... I really don't like long filenames. I think I'll pass on that.
MikeJan 17th 2010 6:44AM
Thanks for being the first (and only) to post a specific example. Unfortunately, I can only assume from your example, that you are not a Mac user. Everything you have described can be easily done within iPhoto, the program supplied free with Mac OS. If you were running Mac OS, you would know that.
Jason ClarkeJan 18th 2010 12:42AM
Hi Mike,
I'm a copious note-taker, and I find it's always best to leave the note in a place that is contextually relevant. So, on my computer, I find it is very useful to be able to drop text files into folders quickly.
For example, when I download shareware and decide to purchase it, I keep an archive folder with folders for all of the installers, and I record the license key information in a text file in each installer's folder.
When I collect a bunch of files to email someone, I will put them into a folder then quickly drop in a readme.txt file before zipping the folder up. That way, the recipient receives instructions right with the files they receive from me when they unzip the archive.
At work we use plain text files wherever possible, and our office network is littered with useful little text files with nuggets of information where you need them.
I could go on and on. For some people that are used to working this way, creating text files on the fly is almost a reflex. If you don't have a use-case where this would be useful, nobody is criticizing you as someone who has "little knowledge of computers and computing". But is it really that hard to imagine that it would be useful to some people, who may well have a relatively significant knowledge of computers and computing?
digamejhJan 14th 2010 10:47AM
I switched from PC to Mac in 2004 and only felt the first desire for Windows' "New Text Document" feature just last week.
I will try out this new app anyway should I have the need again.
Jeff VandeheyJan 14th 2010 7:59PM
I couldn't agree more. It's surprising that OSX can't do this out of the box. I personally use an app called 'pathfinder' that is a sort of finder replacement. With pathfinder, you can right click and add a text file. It does this and fills other gaps in the stock OSX finder. It works great, I highly recommend it.
KolaJan 18th 2010 4:50PM
If you don't mind using Terminal the easiest way is to simply enter 'touch filename.extension' see http://www.coolskool.blog-city.com/creating_a_new_text_file_in_osx.htm
K