Indeed, it is often hard to determine exactly what kind of file has
the Markdown filetype. Any suffix you decide to use can do
(.mkd, .markdown, .text, etc.). Also, the design philosophy behind
Markdown was precisely that it was meant to be based on standard,
plain text files. I find it fairly easy to read and edit plain text
files with Markdown syntax, and only call the filetype plugin whenever
I need to apply some kind of transformation, or export the file.
So that could make a right mess out of using different filetype
icons. Aside from the bundle size issue which Nico points out.
Come to think of it, what (Mac)Vim needs is a more advanced, more
fully-featured Markdown mode. Right now, I'm using Multi-markdown, and
export by piping the file "manually" (a couple of keybindings).
On Dec 1, 4:40 am, Nico Weber <nicolaswe...@...> wrote:
> Hi garfield,
> On 30.11.2009, at 13:42, garfield wrote:
> > I was wondering whether or not it would be possible to include a
> > filetype icon for Markdown files (mkd) in a future update? Right now
> > they're just blank documents. As it's a small request, I hope it
> > wouldn't be too much to ask it to be included in the next snapshot /
> > stable release.
> we discussed this a few months ago in a thread that I'm not able to
> find at the moment. The reasoning was that including "real" document
> icons for all supported file types made macvim several megabytes
> larger, so we decided to only include "real" icons for the more
> popular formats.
> Oh, wait, just found the thread, so just read that:http://groups.google.com/group/vim_mac/browse_thread/thread/adf11a984...
> Here's some data that suggests that not having an icon for markdown
> kinda makes sense:
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php