-
Notifications
You must be signed in to change notification settings - Fork 146
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
Any reason to don't set filetype to some value? #43
Comments
Hey, I've definitely thought about this. I was going back and forth between adding a config file for vim-anywhere or finding a simple way to set this up by having vim anywhere read something set in the user's Vim config file whenever it's started. I stayed away from setting defaults initially to keep the defaults from getting in anyone's way. Like if I default to markdown and you are trying to write something else, the fact that the filetype is markdown could cause unwanted highlighting and formatting. I figured nothing is better than something you might not want. Thats a neat trick though. I may do add that to the readme eventually. I'll leave this open as a feature request if. |
Thanks for the detailed reply. Note about configuration. Please, don't reinvent the wheel. The Vim has a built-in way to configure all the things ( Best regards. |
Thats a good point. I wonder if there is some way to make it easier to identify vim-anywhere editing in .vimrc? I'll take another look and see if I can find anything. |
You could set a variable from the command line, then one could set the file type and other configuration in vimrc based on that. |
how about setting filetype to |
Any way to set default filetype for new files? For example, I mostly use
vim-anywhere
to write inmarkdown
and need toset ft=markdown
any timea new Vim window opened.
For now I use the custom autocommand in my
.vimrc
to force set filetype forvim-anywhere
files:Why not set filetype to
text
ormarkdown
by default?The text was updated successfully, but these errors were encountered: