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

Any reason to don't set filetype to some value? #43

Open
vitalk opened this issue Sep 16, 2014 · 6 comments
Open

Any reason to don't set filetype to some value? #43

vitalk opened this issue Sep 16, 2014 · 6 comments

Comments

@vitalk
Copy link
Contributor

vitalk commented Sep 16, 2014

Any way to set default filetype for new files? For example, I mostly use
vim-anywhere to write in markdown and need to set ft=markdown any time
a new Vim window opened.

For now I use the custom autocommand in my .vimrc to force set filetype for
vim-anywhere files:

augroup ft_vim_anywhere
  au!
  au BufNewFile,BufRead **/vim-anywhere/doc-** setl ft=markdown
augroup END

Why not set filetype to text or markdown by default?

@cknadler
Copy link
Owner

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.

@vitalk
Copy link
Contributor Author

vitalk commented Feb 15, 2015

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 (.vimrc). Think, how would Vim look like if any plugin and extension (I think about vim-anywhere more as a Vim extension then a simple wrapper) has its own config in a separate file. Each vimmer has a own, lovely organized .vimrc, and the best thing you can do is to forward them to the right direction. I mean, add a separate section about vim-anywhere configuration into the readme.

Best regards.

@cknadler
Copy link
Owner

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.

@omeid
Copy link

omeid commented Feb 17, 2018

You could set a variable from the command line, then one could set the file type and other configuration in vimrc based on that.

@nimaje
Copy link

nimaje commented Feb 17, 2018

how about setting filetype to vim-anywhere? (e.g. by adding --cmd 'set filetype=vim-anywhere' to the commandline)
afaik that should behave like default if the user didn't added any config, but they can detect it if wanted

@cknadler
Copy link
Owner

@nimaje @omeid Happy to discuss a pull request that adds this functionality. Probably won't get around to implementing myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants