set hidden? about vim-sensible HOT 17 CLOSED

@zehrizzatti I do. Although I also use splits a lot (and occasionally tabs). Splits (particularly with <C-W>_) are almost the same, but keep things in sight, in mind.

@sickill I actually added 'autowrite' mainly because it makes 'hidden' more tolerable. My worst experiences have been pairing with people who set the latter but not the former. (For the same reason, I set 'smartcase' but not 'ignorecase'.) One thing that drove me nuts was the way the swap files piled up (frequentATTENTION errors because I edited a file in another instance earlier), but I now have a hack in my vimrc to selectively disable those, so maybe I'll give it another go. I wouldn't hold my breath.

I'm going to close this. I thought that maybe I was out of touch with what the kids are doing nowadays, but after discussing with some colleagues (a subset of whom found their way here), I think it's divisive enough to omit.

from vim-sensible.

👍

from vim-sensible.

👍

from vim-sensible.

I can't stand 'hidden'. I constantly get burned by out-of-sight, out-of-mind scenarios. But let's assume, for the sake of discussion, I'm the only one in the world that feels this way.

Who among you uses :set hidden? without some other plugin to help you manage buffers (including bufkill and similar)?

from vim-sensible.

👍

from vim-sensible.

I hate :set hidden as well, fwiw.

from vim-sensible.

The time for 👍 ended when I attempted to start a discussion. My question stands. I'm not going to set an option that's worthless and confusing without other plugins.

from vim-sensible.

I have hidden on, and no plugins to help with buffers. I always thought it was annoying to save a file any time I wanted to check something somewhere else, and was glad when I discovered that option. I like, though, that vim will complain if I try to exit with unsaved files, making me check what was it that I forgot to save. Sometimes you are just not ready to save a file but need to check something else.
@tpope I'm just wondering, you actually save every single time when alternating with things like :A for example?

from vim-sensible.

I hate :set hidden. Who the fuck wants a shit ton of buffers behind the scenes with unwritten changes? More times than I can count I'm wondering why the hell fuck test isn't passing only to realize I bounced back to the test with :A without saving. Every new environment I sit down to, I :set nohidden now.

from vim-sensible.

Well, as for "i-have-to-constantly-save / i-have-to-remember-to-save" issue there's autowrite (which is already a part of this plugin btw) and I suppose this is what nohidden guys are using, right?

from vim-sensible.

Actually, @sickill I simply :w all the live-long day. shrugs

from vim-sensible.

Well, I don't know guys. I'm pretty much validating my own vimrc. If anybody else thinks the things in it are sensible, I'm cool :D But I get the idea. I'm in it for learning as much as anyone. So, those who don't like hidden, pretty much use :w all the time. I'll throw a :wa every once in a while if tests go nuts :p

from vim-sensible.

Fair enough.

from vim-sensible.

I've always used scripts that automatically recompile and retest my code when a change is detected to the source. That's why I have set hidden noautowrite, and use :wa to save everything and trigger a test. I'm curious, how do you do it?

from vim-sensible.

@dbakker I'm basically doing the same (set hidden noautowrite + :wa)

from vim-sensible.

Instead of dancing around to avoid writes (because they will trigger an unwanted recompile), why not map a leader key to your "recompile and retest" script?

from vim-sensible.

@justinmk My (and I guess, the general) requirements for the solution are:

1. It should run in a seperate thread, so that one can keep working during compilation and stuff.
2. Any time it's triggered, if the target is still running, it needs to be killed.
3. Previous output should stay visible, as it is helpful at times.

The script I have now runs as a seperate process which covers 1 & 3, and it basically is a while-loop with { compile and start program, wait for changes, kill program }. How do you do it?

from vim-sensible.