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.
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.
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.
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
24
View All Answers
Scan code to download App
Related Books
Naked Scripts
Vic To Ria
10
43.8K
“Hold the fucking counter,” he growls.
I grip the edge. He slams into me raw (one brutal thrust that punches the air from my lungs).
“Fuck—Jake—” I choke.
He sets a punishing rhythm, hips snapping so hard the cabinets rattle, cock splitting me open.
“Quiet,” he snarls, spanking my ass hard enough to echo. “Your brother’s ten feet away.”
Another vicious spank. Then another. My skin burns red.
“Yes—Daddy—harder—” I sob, biting my lip bloody.
He spanks me again and again, handprints blooming, fucking me so deep my toes curl.
“You love this, don’t you?” he rasps. “Love getting wrecked while Tyler sleeps.”
“Yes—fuck yes—don’t stop—”
**
Naked Scripts is a compilation of thrilling, heart throbbing erotica short stories that would keep you at the edge in anticipation for more.
It's loaded with forbidden romance, domineering men, naughty and sex female leads that leaves you aching for release.
From forbidden trysts to irresistible strangers.
Every one holds desires, buried deep in the hearts to be treated like a slave or be called daddy! And in this collection, all your nasty fantasies would be unraveled.
It would be an escape to the 9th heavens while you beg and plead for more like a good girl.
Rejected by her destined mate and betrayed by her pack, Luna warrior Sophie finds herself drowning her sorrows at a human bar. That's where she meets the mysterious Christian Knight - a powerful Alpha from a rival pack. Little does she know, he's not just any Alpha - he's her second chance mate, and her new boss at the pack's front company, Knight Industries.
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.
Carter is a disabled 19 years old ex football player. After an accident one year ago, he was cursed to a lifetime in a wheelchair. Ryder is an antisocial 18 years old jock. He became the quarterback of the football team after his biggest rival, Carter Matvey, changed schools for a totally unknown reason. What happens when Carter's father employs the jock to be the boy's caregiver? Are the two quarterbacks able to go a few quarters back and score points into this crazy match of love? What about the fact that under his impenetrable shell of muscles Ryder hides a very soft core? After Carter breaks his walls will he transform into puddle? Follow their juicy trip of love and hate and you'll find out . "Ryder? I think Rider suits you better... in like... Cart Rider "
Aliens are a real thing, they are hidden, they are a secret, but they have their own agreement with earth.
They choose humans, ones that no one would miss, hated, forgotten, and abandoned kids, they are sent to a special facility, they are groomed and taught since birth about space, their new life, and their owner/CG/Lover.
Violet is one of those kids, born to an addicted mother, and an MIA father, but she never believed in the system, she didn't believe there was someone out there for her, until he came.
Now she refuses to let him go, space life would be coming sooner than later.
This is a cgl story/fluffy story.
Appologies for any misspelling or grammar mistakes.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.