My go-to practical tip: adjust three main settings — :set shiftwidth=NUM, :set tabstop=NUM, and :set softtabstop=NUM — and then decide whether you want real tabs or spaces with :set expandtab or :set noexpandtab. shiftwidth controls how many spaces Vim uses for each indent level, tabstop affects how existing TAB characters display, and softtabstop makes editing with the Tab key feel right. For file-specific behavior I use :setlocal inside an autocmd for the filetype (for example Python gets four spaces), and if I change the rules for an open file I run gg=G to reindent it or :retab to convert tabs/spaces. That combination covers most real-world headaches I've hit while juggling other people's style guides.
I tend to approach this from a project configuration angle: first I check what Vim is currently using with :set shiftwidth? :set tabstop? and :set softtabstop? so I know what's active. shiftwidth determines the logical indentation size that automatic indentation uses and that >>/<< apply, while tabstop controls how many spaces a real TAB char stands for in the file. softtabstop is the editing compromise — it makes pressing Tab and Backspace feel natural without changing existing characters until you write the file with :retab or toggle expandtab.
For per-project consistency I add FileType autocommands, something like autocmd FileType python setlocal expandtab shiftwidth=4 softtabstop=4, which keeps Python files clean while allowing different settings for, say, Makefiles (where literal tabs are required). If you want to switch on the fly, :setlocal sw=2 ts=2 sts=2 is handy. I also use :set cindent and tweak cinoptions for C/C++ work; those control deeper formatting behavior beyond width. Honestly, once you combine :setlocal, :retab, and gg=G you can migrate an entire codebase to the indentation rules you prefer without losing your mind.
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.
Okay, for a quick practical checklist: use :set shiftwidth=4 to set the indent amount Vim uses for operations and automatic indentation; use :set tabstop=4 to set how many spaces a literal TAB represents; and use :set softtabstop=4 to fine-tune tab behavior while editing. If you prefer spaces over tabs, add :set expandtab, and if you want buffer-local settings for a filetype, use :setlocal shiftwidth=2 softtabstop=2 expandtab. Also remember :set autoindent to enable simple carry-over indentation, and :set cindent or :set smartindent for smarter language-aware indentation. When changing these mid-file, gg=G reindents lines and :retab converts between tabs and spaces. I learned this the hard way when my collaborator kept committing mixed tabs and spaces—once you get the sw/ts/sts relationship, life gets easier.
2025-09-10 18:36:05
13
View All Answers
Scan code to download App
Related Books
Dripping Forbidden: 100 Ways to Make Yourself Wet
Flimxy vic
10
23.8K
If you’re a delicate little flower who clutches pearls and believes sex should only happen in the missionary position with the lights off and your spouse’s permission, close this book immediately. Seriously. Put it down before you ruin your boring little life with uncontrollable wetness and questionable morals.
Still here? Good girl.
Welcome to Dripping Forbidden: 100 Ways to Make Yourself Wet — a ruthless, dripping-wet collection of one hundred filthy, plot-driven taboo stories that don’t just flirt with the line… they bend you over it, fuck you senseless, and leave you leaking.😉 💦
“You wear these little skirts… are you trying to seduce me?” His eyes dragged down my body.
“I—I don’t know what you’re talking about”
Before I could finish, his hand slid up my thigh, fingers brushing beneath the edge of my skirt. My breath hitched. He shoved my panties aside and pressed two thick fingers inside me.
“Ahh. . . Kelvin. .” My knees buckled against the sink as he started slow, then thrust rougher, stretching me with every push.
“You like that, baby girl?” he whispered against my lips.
“Yes… oh God, yes.”
His mouth hovered over mine, stealing the sound of my moans before he spun me around to face the mirror. My own reflection stared back at me wide eyes, flushed cheeks while Kelvin loomed behind, his heat swallowing me whole.
“Watch while I fuck you,” he growled, shoving down his zipper.
The heavy length of him slammed into me in one rough stroke, knocking the air from my lungs.
“F-fuck!” I cried out, gripping the sink for dear life.
He yanked my hair back, forcing me to look at myself as he pounded into me. “Be my slut today.”
Dripping Wet is a collection of straight-up filthy stories about raw, no-limits sex.
Bodies crashing together in hard fucks. Holes stretched wide, throats used rough, sheets drenched in cum and sweat.
Each one dives deep into pure hunger, cocks slamming in deep, pussies taking it hard, asses getting claimed with no mercy. All the taboo stuff you crave, laid out in brutal detail.
No romance. No sweet talk. Just hard, wet, pounding sex that leaves you spent. This book isn't about love. It's about need and giving in until you're soaked.
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.
Victor gently caressed her inner thigh, his fingertip grazing her smooth skin. He gently slipped his down her panties and took a sniff of it before placing it on the other end of the bed. Her neat and recently shaved pussy glistened, making it obvious that she was already prepared for the moment, and inviting his touch. Her pink and tender pussy is oozing already. "Is this your first time?" he whispered softly in her ear. She nodded and said "yes," her voice was shaky and barely audible. "Don't worry, I'll be gentle," he reassured, in a soothing voice.
****
He gently slipped his cock in. "Fuck," Lily cried as she let out a very loud moan.....
I was nineteen the first time Cole Whitfield broke me.
Not with cruelty. With a single word.
Why.
Not did you — why. Like the answer was already settled and he just wanted the story to make sense. I told him the truth anyway. He said nothing that mattered. So I picked up my bag, walked out of his apartment, and decided that a man who trusted a rumor over two years of me wasn’t worth a correction.
I spent the next two years becoming someone I actually liked. New city. Graduate program. A published paper with my name on it. I was done with Cole Whitfield in every way a person can be done.
Then I walked into Seminar Room 114 and he was sitting right there, gray eyes already on the door, like some part of him knew.
I sat down. I opened my notebook. I did not look up.
Here’s the thing about studying how people form beliefs: you understand exactly why he believed it. That doesn’t mean you forgive it. That doesn’t mean two years of silence disappear because he’s learned how to look at you like he’s sorry.
He wants a conversation. I want my degree.
But the campus is small, the seminar table is round, and the boy who broke my heart at nineteen is doing everything right at twenty-one — and I’m starting to understand that composed isn’t the same thing as healed.
I hate that I still know the exact sound of his voice.
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.
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, 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.
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.
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.
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.
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.
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.
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