Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overly Agressive Restrictions About File Type #7

Closed
lgarron opened this issue Jun 26, 2014 · 1 comment
Closed

Overly Agressive Restrictions About File Type #7

lgarron opened this issue Jun 26, 2014 · 1 comment
Labels
Milestone

Comments

@lgarron
Copy link

lgarron commented Jun 26, 2014

The first thing I tried to open in MacDown.app was my .zshrc, which is actually literate zsh: https://github.com/lgarron/dotfiles/blob/master/home/.zshrc

  1. First, I tried to open a convenience symlink to it called zshrc.md:
    screenshot 2014-06-25 17 25 30
  2. Then I tried opening the symlink located at ~/.zshrc. Same error.
  3. Then I tried opening the target of the symlinks: the file named .zshrc in my source-controlled dotfiles. Same error.
  4. Then I tried copying. .zshrc and renaming it to zshrc.md. Different error. We're making progress!
    screenshot 2014-06-25 17 28 22
  5. Renamed zshrc.md to zshrc.markdown. It finally works.

This was even more aggravating for me, because my usual way of following symlinks to their targets isn't working.
No other program has ever had a problem with any of these.

@uranusjr uranusjr added the bug label Jun 26, 2014
@uranusjr
Copy link
Member

OS X uses UTI to identify file formats, and the extension is only a hint. I missed a UTI import in the 0.1 release, so MacDown wasn’t able to map .md extensions to the Markdown UTI automatically. The reason why .markdown works is probably because another editor (Mou?) recognised it and mapped the UTI instead. With the UTI mapped MacDown can then open the file.

The UTI import has been fixed in 5e2e188, which will be included in the next release. I’m closing this right now, but please feel free to reopen it if you experience any similar problems in the future.

Thanks a lot.

@uranusjr uranusjr added this to the 0.1.1 milestone Jun 26, 2014
This was referenced Jun 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants