
- #How to open txt file on mac how to
- #How to open txt file on mac mac os x
- #How to open txt file on mac manual
- #How to open txt file on mac mac
(at least I did since I always used slightly non standard stuff and wanted it done my own way, ie., inside tmux). You'll probably have to edit the wrapper script a few times. Step 3 is trying to open your *.txt file and then banging your forehead on the table when it doesn't work.

I've forgotten where everything is but this will most likely be in /Library/ somewher) (Again, I used guides on the internet for this. You can probably sorta do this using dialogue menus n what not for OSX but trust me when I say it's far more robust and easier if you do this by creating/editing a mysterious plist file somewhere. Step 2 is setting this thing as default for all *.txt files, blank no-extension files, *.md, and whatever other file extension you want. I followed (99% copy/paste) some guides on the internet for this. The script is going to launch your executable (vim), inside your terminal, and open the file in it. The wrapper script will be the "app" that you set as default for *.txt files.

Step 1 is gonna be making a "wrapper" script (language will be AppleScript). Ok so this is actually possible, don't worry! I'm going off of memory here since it's been years since I've actually used a mac. And please those of you who deign to grace us with your vim wisdom - be kind.
#How to open txt file on mac how to
#How to open txt file on mac mac
Vim Mac Mailing List: low volume mac specific list.Vim Dev Mailing List: high volume dev list.Vim Use Mailing List: high volume user support list.Vim Announcements Mailing List: low volume announcement list.Our Wiki!: Let me know if you want to be a contributor.#vim on freenode: 1000+ person reasonably active IRC channel.
#How to open txt file on mac manual
Vim user manual (PDF): 341 pages (extracted from full help linked below).It's real fun when you have thousands of text scripts that have to be ported across OSes and have to figure out what program can best be used to batch convert them all. This is probably all confusing to non-UNIX geeks, but this is something I've had to deal with for the entire 20+ years I've been dealing with text between DOS and UNIX. The vi command line way I deal with this is:Īnd they will be be converted to 'cr' (carriage return, not carriage return-linefeed) and when you save the file it'll be all well in the UNIX world.

Over on the Mac side, TextEdit generally seems to handle text files properly regardless of where they are created, but vi will show those 'crlf' characters as a ^M, which is not a big deal, but annoying.
#How to open txt file on mac mac os x
Oddly enough, if you edit a text file created by Mac OS X with the "DOS" command line 'edit' command under Windows and just save it, it'll convert the newlines to what Windows expects with the rest of the Windows text editors. You'll note that if you use vi on a text file created by a Windows notepad, for example, will show ^M characters at each newline, while text files created by Mac OS X will look all goofy using windows notepad. This is also why I use command line utilities for both OS's, and this is something that goes back to the early days of all the UNIX's and the DOS world.
