Library

How Do Filetype Plugins Interact With Vim Auto-Indent?

2025-09-04 22:00:34

296

Follow18

LoganKit

Inquirer

Doctor

4 Answers

Nora

Book Guide

Driver

I get picky about editor behavior, so I like to think in terms of responsibilities: ftplugins are for configuration and user conveniences, indent scripts are for the algorithm. The key detail is that both operate per-buffer, so they communicate by reading and writing buffer-local options. Order matters because buffer-local options don't merge — they get replaced. That’s why you’ll often see an ftplugin set shiftwidth and an indent/.vim set indentexpr; if indentexpr is present, Vim uses that function to compute indentation regardless of simpler flags like 'smartindent'.

A few nuanced rules I rely on: FileType autocommands trigger ftplugin loading (which commonly runs first), but distributions and plugins can change load order; indent scripts often guard themselves with b:did_indent to avoid double-loading, so you can set that flag manually in an ftplugin to prevent an indent script from running. For persistent tweaks I use after/ftplugin/.vim or after/indent/.vim so my preferences load after built-in scripts. And when debugging, :setlocal, :verbose setlocal, and :scriptnames are my friends — they tell me who stomped on what. In short, treat ftplugin for the style and indent/ for the brain, and use 'after' or b:did_indent when you want to pick the winner.

2025-09-05 01:34:11

Caleb

Contributor

Receptionist

If you've ever opened a file in Vim and wondered why indentation behaves one way in one project and differently in another, the way filetype plugins and indent scripts interact is the usual culprit. In my messy but beloved setup I keep separate snippets in ~/.vim/ftplugin/ and ~/.vim/indent/ and they each have a job: ftplugin files generally set buffer-local editing options (things like shiftwidth, tabstop, expandtab, mappings) while indent scripts (under indent/) provide indentation logic by setting 'indentexpr', 'cindent', 'indentkeys', or related buffer-local options. Because these are buffer-local, whichever script writes a particular option last wins for that buffer.

Practically that means you can get conflicts. An ftplugin might set 'shiftwidth' to 4 for 'python' and an indent script might expect 2; or an indent script will set 'indentexpr' to a custom function that overrides simpler behaviors such as 'autoindent'. The usual fixes I use are: enable both with :filetype plugin indent on, then put overrides in after/ftplugin/ or after/indent/ so they load later; or explicitly set local options with setlocal in a ftplugin; or prevent an indent script with let b:did_indent = 1 if you deliberately want to skip it. For debugging, :scriptnames shows what got sourced, and :verbose setlocal shiftwidth? / :verbose setlocal indentexpr? tell you who last changed a setting. I like keeping ftplugin for styling and small mappings, and leaving indentation math to indent scripts — but I always keep an 'after' copy for those moments when I need the last word.

2025-09-09 17:49:50

Wyatt

Sharp Observer

Student

I usually keep things simple: filetype plugins and indent scripts both run when filetype detection is enabled, but they have different jobs. The ftplugin configures buffer-local settings and convenience stuff, and the indent script provides the indentation logic (often by setting 'indentexpr' or enabling 'cindent'). Because these scripts set buffer-local options, whichever one runs later or explicitly sets an option last determines the final behavior in that buffer.

If you need to override built-in behavior, put changes in after/ftplugin/ or after/indent/ so they load after the defaults, or disable indent scripts with :filetype indent off. For quick fixes, :verbose setlocal shiftwidth? and :scriptnames show recent changes and loaded scripts. It’s worked for me whenever a project insists on tabs while my brain prefers spaces.

2025-09-09 18:30:33

Nevaeh

Reply Helper

Police Officer

I tend to tinker a lot, so here's the practical short guide I use every time Vim mis-indents: Vim treats filetype plugins (ftplugin/.vim) and indent scripts (indent/.vim) as separate things. The ftplugin usually configures buffer-specific options like tabstop or shiftwidth and adds convenient mappings, while the indent script defines the actual indentation logic by setting 'indentexpr', 'cindent', or 'indentkeys'. If both try to control the same option, the last file that sets it wins for that buffer.

To control the order, you can place custom changes in after/ftplugin/ or after/indent/ so they load later, or set let b:did_indent = 1 inside an ftplugin to skip the indent script. If you want to turn off indent scripts entirely, use :filetype indent off. When things go weird I use :scriptnames to see what loaded and :verbose setlocal indentexpr? to find who changed it. That little workflow saves me from pointless reformatting fights.

2025-09-09 23:39:40

View All Answers

Related Books

I Shared My World, He Shared an Algorithm

Raw & Ruined: Short Romantic Sins

Elly

36.8K

Raw and Ruined: Short Erotic Sins Step into a world where desire doesn’t ask permission and shame is just foreplay. Several merciless, sweat-slick stories that don’t seduce—they take. No slow burns. No sweet nothings. Just skin slapping skin, nails carving lines down backs, mouths full, thighs trembling, and the kind of orgasms that make your vision white out and your voice break. These stories are greedy. They bruise. They stain sheets and memories. They leave teeth marks and handprints and the delicious ache of being used exactly the way you secretly always wanted. These are not love stories. These are lust stories. Short. Sharp. Unapologetic. And they will leave you throbbing, aching, and reaching for someone—or something—to ruin you next. Raw and Ruined: Short Erotic Sins Because sometimes the dirtiest thing you can do… is let yourself be devoured.

Read Now

DIRTY PAGES (A Short Story Collection)

Aria Steele

39.6K

WARNING: HEAVY SMUT AHEAD!!! Mature audiences only! Proceed with caution! ~ ~ ~ ~ ~ “Please,” she whispered, desperation cracking her voice. “Please, Chase.” “Begging already?” His voice was cruel, his fingers circling faster, pushing her to the edge. “I'm not even nearly done with you yet.” She squeezed her eyes shut, the recruit’s muffled cries and the whip’s crack filling her ears, amplifying her need. Chase’s fingers were relentless, stroking her clit, and dipping inside just enough to tease. “Please,” she whimpered, louder now, her hands gripping his shoulders. “I’m sorry. I won’t lie again. I’ll be good. Please, let me cum.” He chuckled, his lips brushing her neck. “Not yet, baby. Fight it.” Her body screamed, every nerve on fire, the recruit’s struggles mirroring her own. The girl’s master groaned, close to release, as Lila’s whip landed again and again on her ass. Emma’s head felt like it was about to explode under the pressure, her thighs shook with the effort to conceal it, her pleas spilling out. “Please, Chase, I can’t hold it any longer… I need it." "Don't. You. Dare. Come." ~ ~ ~ ~ ~ Picture this: A CEO pinning his partner's daughter over his desk, whispering rules that chain her soul while his cock claims her body. Or a werewolf's claws raking skin in the moonlit woods, rutting her senseless till she's howling his name. We mix it up... sweet, slow-burn romances that melt into tender fucks and whispered "I love yous," flipping to the dark side with BDSM bites, non-con edges that blur fear into filthy want, and horror vibes where ghosts fuck you cold then hot. Your panties? Ruined. Your cravings? Fed. And yet, you'll still be here begging for more. Dive in if you're brave enough.

Read Now

DEVIN

Castiel

9.7

508.0K

Love For The Wicked Book One. Devin, a stereotypical playboy billionaire, wears a ruthless CEO’s charade. Life was perfect for him that way until he realized he had a gem in his office all this time. Innocent, kind, and compassionate Ren never thought she’d fall in love with her boss a.k.a. the Devil. The same man who made her life miserable for three excruciating long years. Love made their opposite worlds collide. Love surpassed the walls Devin and Ren surrounded their hearts. When obstacles arise, will love be enough to let forgiveness in? Can love mend the rift that is caused by the same passion that pulled them together? ~~ “Ren! Wait!” Devin’s strode was huge enough to reach me before I could walk away from the mansion. The dawn was slowly breaking, boasting its beauty in my face as Devin wrapped his arms around me from behind. “Please, let’s talk this through.” “I have to go...” to get as far away as possible from you. He buried his face in my hair and whispered, “don’t leave me, please… I love you.” ~~ [Mature Content] Cover by DobolyuV

Read Now

SLIPPERY SINS (A collection)

Gift N.A

1.3K

Blurb. “You're so tight Val! As tight as I imagined. I'll have to expand this to fit my c*ck.” Boris my strict older boss whispered before forcing four of his fingers inside of me. I let out a loud moan. “Oh mi goddddddd.” “Good, this is what happens when you send your nude file to your boss.” “It was a mistak…..” “A mistake? And your panties are all soaked and dripping at my touch.” He mocked. “Be a good girl and allow daddy, ease your tense body.” There was something about his voice that sent shivers through me. Within seconds my pussy walls throbbed and clenched around his fingers and I had a convulsive orgasm that shook my body like one possessed with a slimy sin demon. ********************************** Slippery sins is an unapologetically sensual compilation of the dirtiest and steamiest erotica short stories that will leave your pants soaked and you cocks hard. It is loaded with irresistible tension, unspoken longings, dark, craving, deep chemistry, and forbidden touches. Each story in this collection is designed to make you cum or orgasm whichever one but you will definitely be wet as you slip into the pages. ️Warning: This book is rated 18 , it contains explicit sexual contents. Graphic languages, dirty talks and mature themes that may not be suitable for all readers.

Read Now

I Shared My World, He Shared an Algorithm

Fortune Paws

629

I'm the type who has the urge to overshare my life with him. It can be anything, be it the flowers blooming by the side of the road, the unpleasant coffee I end up having, or the sunset I've seen when I'm on my way home from work. Heck, when I think of Edwin Howell all of a sudden, I can't resist texting him at all. His replies are always short and perfunctory, though I suppose they count as a form of response from him. Hence, over the past six months, I've relied on these cold-sounding yet present replies to give me enough strength to deal with the engagement party, go wedding gown shopping, and choose the wedding venue all by myself. Somehow, I've managed to hang in there till the week before the wedding. But five days before the wedding, I discover an AI program that's installed within Edwin's computer. It can categorize every single sentence that I've sent to Edwin and extract the keywords. Then, it'll draft the most perfunctory responses that will never go wrong. If I miss Edwin, the AI will reply, "Mm-hmm." If I feel aggrieved, the AI will reply, "Got it." When I try to vent my frustrations to Edwin, the AI will reply, "Don't make such a big deal out of it." It turns out that Edwin isn't the one who has been responding to my need to overshare. The thing is, he has been texting another woman nonstop in another private chat. They talk about anything and everything under the sun, from exchanging simple good mornings and good nights to asking, "What are you having for lunch today?" and "Do you wanna go to the beach someday?" Finally, I realize that Edwin isn't the silent type who keeps his love in. If anything, he's the flashy type who will proclaim his love anywhere, anytime. It's just that… his love has never been mine to have. As for me, I've finally made up my mind to stop spending my life waiting for a response that will never come.

Read Now

They Called Me the Freaking Rulebot

Mini Min

7.3

8.9K

I was in the office bathroom stall when I heard them trash-talking me. The intern I'd trained for three months whined, "She's a heartless witch—like a robot with zero brain cells." I was about to swing the door open when another voice jumped in, laughing. "Documents incomplete." "Receipts don't match." "No signature? Denied." "Seriously, we've all memorized the freaking rulebot's script!" Once they were gone, I headed back to my desk. The intern stormed in and slammed a fat stack of reimbursement forms in front of me. "Don't go on another power trip and block everyone's claims." I skimmed the obviously fake receipts. Normally, I'd tear into her. But this time, I just smiled. "My head's killing me. Can't read the fine print."

Read Now

Related Questions

Which plugins improve vim auto-indent accuracy?

4 Answers2025-09-04 05:51:09

Okay, I’ll gush a bit: if you want auto-indent to actually behave instead of randomly guessing, start by combining a detector, a language-aware indenter, and a formatter. I like using vim-sleuth to sniff tabs vs spaces and shiftwidth automatically; it fixes half my headaches before I even open the file. After sleuth, for Neovim I plug in nvim-treesitter with its indent module turned on — it understands syntax much better than old regex-based indent scripts. Pair that with either null-ls or coc.nvim (or ale if you prefer linters/formatters) to run real formatters like prettier, clang-format, shfmt, or rustfmt on save. That lets the language tools correct structural indentation rather than vim guessing. Small extras that helped me: editorconfig-vim to respect project settings, indent-o-matic as a fallback detector in weird repos, and indent-blankline.nvim for visual guides so you can spot mistakes. Also don't forget filetype plugin indent on and sensible defaults (autoindent, smartindent/cindent where appropriate). With those layered, indentation accuracy improves dramatically and my diffs stop being a jungle of whitespace edits.

How does vim auto-indent handle mixed tabs and spaces?

10 Answers2025-09-04 19:39:38

If you've ever opened a file that looks like a bento box of tabs and spaces, Vim's auto-indent behavior is surprisingly predictable once you know the pieces involved. Auto-indent (the basic 'autoindent' option) simply copies the leading characters from the previous line — literally. That means if the previous line starts with a tab, then two spaces, Vim will start the new line with that exact sequence. Nothing clever, just a straightforward copy. Where things get interesting is when you press Tab or when you run reindent commands: Tab insertion is governed by 'expandtab' and 'softtabstop'. If 'expandtab' is set, inserting a tab character from Insert mode actually inserts spaces. If it's unset, Vim inserts a real tab character, and 'softtabstop' affects how many spaces the Tab key represents while editing. Reformatting with commands like '=' or using cindent/smartindent is different: Vim computes the desired indentation in columns based on 'shiftwidth' and the language indent rules, then writes the indentation according to your tab settings (usually honoring 'expandtab' to decide whether to use spaces, or using tabs where possible when it's unset). Practical tips: use ':set list' to reveal hidden whitespace, ':set tabstop=4 shiftwidth=4 softtabstop=4', ':set expandtab' to normalize new indentation to spaces, and ':retab' to convert existing characters if you want to clean the file up.

What vim auto-indent commands adjust indent width?

4 Answers2025-09-04 09:02:52

If you're fiddling with Vim's indentation and want precise control, the trio I reach for is :set shiftwidth, :set tabstop, and :set softtabstop. shiftwidth (sw) controls how many spaces a single indentation level uses for operations like >>, <<, and automatic indentation. I usually do :setlocal shiftwidth=4 for projects that use four-space indents. tabstop (ts) sets how many spaces a literal TAB character displays as; use :set tabstop=4 to make existing tabs line up visually with your intended width. softtabstop (sts) affects insert-mode behavior: :set softtabstop=4 makes pressing Backspace or Tab behave like you're working with 4-space logical tabs even if actual file uses tabs. A couple of other practical commands I keep in my .vimrc: :set expandtab to insert spaces instead of real tabs (or :set noexpandtab to keep tabs), :set autoindent to keep the previous line's indentation, and :set cindent or :set smartindent for C-like auto-indenting. If you want the changes to apply only to the current buffer, use :setlocal sw=2 ts=2 sts=2. To reformat an entire file after changing settings, I often run gg=G to reindent the whole buffer, or :retab to convert tabs to spaces (or the reverse with :retab!). These little tweaks saved me hours when I was switching between Python, Makefiles, and Go projects.

Why is vim auto-indent not working after vimrc changes?

12 Answers2025-09-04 02:43:46

Man, that frustration is so real — I’ve been there. First thing I do is check whether vim even thinks it should indent: open the file and run :set filetype? and :verbose set autoindent. If filetype is empty or wrong, indent scripts won’t run. If :verbose shows autoindent being turned off by some script, that points to the culprit. Next, consider obvious toggles that silently kill indentation: if you’ve got 'set paste' enabled (or you toggled paste mode earlier with a mapping), indentation won’t behave. Also check whether you disabled 'autoindent', 'smartindent', or 'cindent' by mistake. Use :set paste? and :set autoindent? to inspect current state. If those look fine, source your vimrc manually (:source ~/.vimrc) and watch :messages for errors — a syntax error early in the file can stop the rest of the config from loading, so later indent settings never get applied. Also run vim -u NONE (or nvim -u NORC) to see if a vanilla session indents correctly; if it does, a plugin or a line in your vimrc is to blame. Useful commands: :scriptnames (shows loaded scripts), :verbose set shiftwidth? tabstop? expandtab? and checking ~/.vim/indent or plugin ftplugin files for overrides. If you want, paste the problematic snippet and I’ll poke at it with you.

How can I enable vim auto-indent for Python files?

4 Answers2025-09-04 03:25:38

Honestly, getting Python auto-indent working in vim is one of those tiny victories that makes editing a joy. My go-to is to enable vim's filetype detection and then set sensible Python indentation rules in my config. Add these lines to your ~/.vimrc or init.vim for Neovim: filetype plugin indent on set autoindent set expandtab set shiftwidth=4 set softtabstop=4 set tabstop=4 The first line turns on filetype-specific plugins and indent scripts (this loads vim's python indent file). The rest make tabs into spaces and use four spaces per indent, which is the common Python convention. If you want the setting to apply only to Python buffers, drop the global lines into ~/.vim/ftplugin/python.vim and use setlocal instead of set. If indentation still feels off, check the buffer's filetype with :set filetype? and inspect loaded scripts with :scriptnames. I sometimes install a plugin like 'vim-python-pep8-indent' or use external formatters like 'black' called via a formatter plugin to normalize whitespace. Try opening a .py and typing an indented block — it should behave. If not, tell me what output :set filetype? and :verbose set shiftwidth? give and we can debug further.

How do I disable vim auto-indent temporarily?

4 Answers2025-09-04 20:03:23

Okay, here's a practical and friendly way I handle Vim's auto-indent when I need it out of the way for a few moments. If I just want to paste something without Vim reformatting it, I usually toggle paste mode: :set paste to turn it on, paste the text, then :set nopaste to go back. I often map a key for that so it’s painless, for example :set pastetoggle= or put in my config nnoremap :set paste! to flip it. Paste mode stops auto-indent, indentexpr, and other niceties, so your pasted code won't get mangled. If I need to disable automatic indentation for editing (not just pasting), I prefer buffer-local switches so I don’t mess with other files: :setlocal noautoindent nosmartindent nocindent and, if needed, :setlocal indentexpr= to clear any expression-based indent. To restore, use :setlocal autoindent smartindent cindent or reopen the buffer. Little tip: :set paste? shows whether paste is on. Personally, I use paste for quick fixes and :setlocal for longer edits — keeps things predictable and quiet during a frantic refactor.

How do I fix inconsistent vim auto-indent across buffers?

4 Answers2025-09-04 15:03:11

Okay — let me walk you through this like we’re debugging a stubborn editor together. In my experience inconsistent Vim indentation across buffers usually comes down to a few culprits: buffer-local options, filetype-specific plugins, modelines in files, or external tools like an .editorconfig plugin. First, check what each buffer actually has set. Use :setlocal and :verbose set shiftwidth? tabstop? softtabstop? expandtab? and :set filetype? and :verbose set autoindent? — the verbose form tells you where a setting was last changed. If you see different values between buffers, that’s your clue: something is changing options per file. Often a ftplugin or indent script is overriding global settings, or a modeline inside a file is setting tabs/spaces. To fix it, pick a consistent baseline in your vimrc/init.vim: filetype plugin indent on (or in Neovim, enable filetype and indentation early), then set sensible defaults like set tabstop=4 shiftwidth=4 softtabstop=4 expandtab or use set noexpandtab for projects that prefer tabs. If a project has specific rules, add an .editorconfig file and install the editorconfig plugin or add autocmds to apply per-filetype settings. When you need to find the source of an override, :scriptnames shows loaded scripts and :verbose set

What are the best vim auto-indent settings for JavaScript?

4 Answers2025-09-04 23:27:43

Okay, this is the hot take I give my friends when they ask how to stop JavaScript files from turning into a jagged mess: treat indentation as a filetype thing, not a global, and use 2 spaces plus an actual JS-aware indent engine. I usually put this in my vimrc (or better, in ftplugin/javascript.vim): filetype plugin indent on autocmd FileType javascript,typescript setlocal shiftwidth=2 softtabstop=2 tabstop=2 expandtab autocmd FileType javascript,typescript setlocal autoindent smartindent Those lines give you consistent 2-space soft tabs (the de facto style for many JS projects) and rely on Vim's smartindent for basic braces. But honestly, for real-world code with ES6/JSX/template literals, install a javascript-indent plugin (like the popular one that provides an indentexpr) and let it set indentexpr for you; it handles arrow functions, template literals and some weird edge cases better than plain smartindent. I also map = to re-indent visually: vmap = = or use gg=G to reformat a whole file. Finally, I pair this with an on-save formatter — 'prettier' is my go-to — so even when teammates differ, my local formatting is predictable. If you want the exact plugin names or a sample ftplugin that runs Prettier on save, I can paste that too.

Can vim auto-indent be configured per project directory?

4 Answers2025-09-04 16:52:11

I'll be blunt: yes, you absolutely can set up Vim to auto-indent differently per project directory, and I've done it a bunch of times across projects with different coding styles. When I need a project-specific policy I usually pick one of three safe routes: use a repository-level '.editorconfig' with the EditorConfig Vim plugin (works across editors and is a huge life-saver), add per-project autocommands in my global vimrc that match the project path, or—if I must—use a controlled local vimrc mechanism (with security checks). For example, in your main vimrc you can add an autocmd that applies settings only when the buffer lives under a particular path: augroup proj_indent autocmd! autocmd BufRead,BufNewFile /path/to/myproj/* setlocal shiftwidth=4 tabstop=4 expandtab augroup END That keeps the rules scoped to files under that directory. I avoid blindly enabling 'exrc' because executing arbitrary project .vimrc files can be risky; instead I either require a checked-in '.editorconfig' or use a trusted plugin like 'localvimrc' that prompts you before sourcing. Also remember to use setlocal so other projects aren’t affected. For Neovim, the same autocmds work, but I often detect the project root via an LSP/root_pattern helper and then apply settings dynamically. Overall, choose EditorConfig if you want a cross-editor approach, or autocommands if you prefer staying purely in Vim land.

How to use expandtab in Vim for indentation?

3 Answers2026-03-27 01:15:25

Vim's expandtab feature is a lifesaver for anyone who prefers spaces over tabs for indentation. I stumbled upon this while working on a collaborative project where mixing tabs and spaces caused chaos in the codebase. To enable it, just type ':set expandtab' in command mode. This ensures every tab press inserts spaces instead of a tab character. You can customize the number of spaces with ':set tabstop=4' (or any number you prefer). What's cool is that this pairs beautifully with 'autoindent' and 'smartindent' for seamless formatting. I once spent hours debugging an issue only to realize inconsistent indentation was the culprit—expandtab would've saved me the headache. Now it's the first thing I configure in my .vimrc for any new environment.

How Do Filetype Plugins Interact With Vim Auto-Indent?

4 Answers

Related Books

Raw & Ruined: Short Romantic Sins

DIRTY PAGES (A Short Story Collection)

DEVIN

SLIPPERY SINS (A collection)

I Shared My World, He Shared an Algorithm

They Called Me the Freaking Rulebot

Related Questions

Which plugins improve vim auto-indent accuracy?

How does vim auto-indent handle mixed tabs and spaces?

What vim auto-indent commands adjust indent width?

Why is vim auto-indent not working after vimrc changes?

How can I enable vim auto-indent for Python files?

How do I disable vim auto-indent temporarily?

How do I fix inconsistent vim auto-indent across buffers?

What are the best vim auto-indent settings for JavaScript?

Can vim auto-indent be configured per project directory?

How to use expandtab in Vim for indentation?

Related Searches

Vim Auto-indent

Vim Json-formatter

Vim Autocomplete

Autocomplete Vim

Vim Foldmethod

Plugin Install Vim

Vim Key Bindings

Vim Highlight Syntax

Expandtab Vim

Vim Highlighting