News for hackers. Stuff that matters.
Re:Vim 8.0 released by rakhimov on Monday September 12, 2016 @11:06AM (#12480302)
I'd recommend https://github.com/tpope/vim-commentary for commenting out code. Anyway, it's not a good practice.
Re:Vim 8.0 released by hackmiester on Monday September 12, 2016 @11:30AM (#12480553)
What would you recommend for turning off a section of code temporarily?
Re:Vim 8.0 released by OMGWTF on Monday September 12, 2016 @11:46AM (#12480685)
For C:

    #if 0
    ...code...
    #endif
Re:Vim 8.0 released by jaymon on Tuesday September 13, 2016 @04:41PM (#12492032)
You could try a plugin I wrote to quickly comment/uncomment blocks of code:

https://github.com/Jaymon/vim-commentify

It's a no frills plugin that only does one thing, but it does it pretty well.

Re:Vim 8.0 released by RBerenguel on Monday September 12, 2016 @11:37AM (#12480610)
Kill region, save, run/compile/read, undo if needed. With undo tree (or if you add commit to the process above) there is no need to comment just one region to turn off something.

Optionally, convert the region into a separate function/method and just don't call it while checking.

Re:Vim 8.0 released by pablasso on Monday September 12, 2016 @01:41PM (#12481835)
You still didn't explained why it wasn't a good practice. This just sounds impractical.
Re:Vim 8.0 released by RBerenguel on Monday September 12, 2016 @04:43PM (#12483471)
Commented code (as in, working code commented out, not comments in code) eventually rots/becomes cruft that at some point in time is going to bite you (or someone else in your team, or some maintainer in the future)
Re:Vim 8.0 released by ssalazar on Monday September 12, 2016 @02:29PM (#12482332)
Yeah, "not a good practice" (i.e. "the user is wrong" or "why would you want to do that?") is the lazy way of justifying software deficiencies.
Re:Vim 8.0 released by RBerenguel on Monday September 12, 2016 @04:45PM (#12483492)
I use emacs, so deficiencies on how vim handles anything do not mean much to me, actually.