Different vimrc by filetype
up vote
0
down vote
favorite
As the title says: can I use different _vimrcs for different programming languages or filetypes? I have to use a lot of different programming languages for lots of different subjects, and for each filetype I want to toggle the original _vimrc and the individual filetype-specific _vimrc. I think all of the filetypes I use are supported by gVim : I mostly use C, C++, Java (Kotlin), and LaTeX.
I'd prefer something I can code without installing plugins, but if I DO need plugins, I'd be very grateful for a suggestion or two.
gvim latex filetype
asked Nov 7 at 8:04
K. Paul
14
add a comment |
up vote
0
down vote
favorite
As the title says: can I use different _vimrcs for different programming languages or filetypes? I have to use a lot of different programming languages for lots of different subjects, and for each filetype I want to toggle the original _vimrc and the individual filetype-specific _vimrc. I think all of the filetypes I use are supported by gVim : I mostly use C, C++, Java (Kotlin), and LaTeX.
I'd prefer something I can code without installing plugins, but if I DO need plugins, I'd be very grateful for a suggestion or two.
gvim latex filetype
asked Nov 7 at 8:04
K. Paul
14
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
As the title says: can I use different _vimrcs for different programming languages or filetypes? I have to use a lot of different programming languages for lots of different subjects, and for each filetype I want to toggle the original _vimrc and the individual filetype-specific _vimrc. I think all of the filetypes I use are supported by gVim : I mostly use C, C++, Java (Kotlin), and LaTeX.
I'd prefer something I can code without installing plugins, but if I DO need plugins, I'd be very grateful for a suggestion or two.
gvim latex filetype
asked Nov 7 at 8:04
K. Paul
14
As the title says: can I use different _vimrcs for different programming languages or filetypes? I have to use a lot of different programming languages for lots of different subjects, and for each filetype I want to toggle the original _vimrc and the individual filetype-specific _vimrc. I think all of the filetypes I use are supported by gVim : I mostly use C, C++, Java (Kotlin), and LaTeX.
I'd prefer something I can code without installing plugins, but if I DO need plugins, I'd be very grateful for a suggestion or two.
gvim latex filetype
gvim latex filetype
asked Nov 7 at 8:04
K. Paul
14
asked Nov 7 at 8:04
K. Paul
14
asked Nov 7 at 8:04
K. Paul
14
asked Nov 7 at 8:04
K. Paul
14
asked Nov 7 at 8:04
K. Paul
14
14
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Nobody's been answering, so I'll just leave what I found for future reference: (I use Windows)
In the $HOME directory, there is a file called vimfiles. In that folder, make a ftplugin folder, and in that, make folders (or .vim extension files) with the first word of the name being a specific filetype extension. For instance, tex filetype plugins would be named tex_blahblahblah.vim. After that, leave the following line in your main _vimrc file:
filetype plugin on
answered Nov 24 at 3:04
K. Paul
14
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Nobody's been answering, so I'll just leave what I found for future reference: (I use Windows)
In the $HOME directory, there is a file called vimfiles. In that folder, make a ftplugin folder, and in that, make folders (or .vim extension files) with the first word of the name being a specific filetype extension. For instance, tex filetype plugins would be named tex_blahblahblah.vim. After that, leave the following line in your main _vimrc file:
filetype plugin on
answered Nov 24 at 3:04
K. Paul
14
add a comment |
up vote
0
down vote
accepted
Nobody's been answering, so I'll just leave what I found for future reference: (I use Windows)
In the $HOME directory, there is a file called vimfiles. In that folder, make a ftplugin folder, and in that, make folders (or .vim extension files) with the first word of the name being a specific filetype extension. For instance, tex filetype plugins would be named tex_blahblahblah.vim. After that, leave the following line in your main _vimrc file:
filetype plugin on
answered Nov 24 at 3:04
K. Paul
14
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Nobody's been answering, so I'll just leave what I found for future reference: (I use Windows)
In the $HOME directory, there is a file called vimfiles. In that folder, make a ftplugin folder, and in that, make folders (or .vim extension files) with the first word of the name being a specific filetype extension. For instance, tex filetype plugins would be named tex_blahblahblah.vim. After that, leave the following line in your main _vimrc file:
filetype plugin on
answered Nov 24 at 3:04
K. Paul
14
Nobody's been answering, so I'll just leave what I found for future reference: (I use Windows)
In the $HOME directory, there is a file called vimfiles. In that folder, make a ftplugin folder, and in that, make folders (or .vim extension files) with the first word of the name being a specific filetype extension. For instance, tex filetype plugins would be named tex_blahblahblah.vim. After that, leave the following line in your main _vimrc file:
filetype plugin on
answered Nov 24 at 3:04
K. Paul
14
answered Nov 24 at 3:04
K. Paul
14
answered Nov 24 at 3:04
K. Paul
14
answered Nov 24 at 3:04
K. Paul
14
14
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1373363%2fdifferent-vimrc-by-filetype%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
