About: Bisecting   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

So learn about bisecting, aka Binary Chop, aka Delta Debugging, aka Divide and Conquer. When you do bisect, you have to start with a ☺ version and a ☠ version. Then you pick a point in between the two, and test to see if it's ☺ or ☠. After you've done that, you've moved the two closer together, so your search space is smaller. When you are debugging, you have your "☠" version automatically, because you've got something that's not working currently. An important test in Vim is to use vim -u NONE (which skips almost all of the startup sequence) to see if the problem reproduces there or not.

AttributesValues
rdfs:label
  • Bisecting
rdfs:comment
  • So learn about bisecting, aka Binary Chop, aka Delta Debugging, aka Divide and Conquer. When you do bisect, you have to start with a ☺ version and a ☠ version. Then you pick a point in between the two, and test to see if it's ☺ or ☠. After you've done that, you've moved the two closer together, so your search space is smaller. When you are debugging, you have your "☠" version automatically, because you've got something that's not working currently. An important test in Vim is to use vim -u NONE (which skips almost all of the startup sequence) to see if the problem reproduces there or not.
Version
  • 7(xsd:integer)
dbkwik:vim/property/wikiPageUsesTemplate
Previous
  • 0(xsd:integer)
Author
  • Ryanking
Subpage
  • /201209
Complexity
  • basic
Created
  • 2012-09-12(xsd:date)
ID
  • 0(xsd:integer)
NEXT
  • 0(xsd:integer)
abstract
  • So learn about bisecting, aka Binary Chop, aka Delta Debugging, aka Divide and Conquer. When you do bisect, you have to start with a ☺ version and a ☠ version. Then you pick a point in between the two, and test to see if it's ☺ or ☠. After you've done that, you've moved the two closer together, so your search space is smaller. When you are debugging, you have your "☠" version automatically, because you've got something that's not working currently. An important test in Vim is to use vim -u NONE (which skips almost all of the startup sequence) to see if the problem reproduces there or not. Generally it will not. * If debugging a .gvimrc problem, you might want to trygvim -U NONE after you determine the status of the lower-cased version. * Try vim -u NORC to see if loading plugins but not rc-files works. * Try vim --noplugin to see if loading rc-files but not plugins works. Then the next step is a bit of a mess. 1. * vim's bairui has a plan for a script, bisectly, that will help you with it, but at the moment his batsuit is at the batdrycleaners, so we're batwaiting with bated batbreath. In the mean-time, what you can do is: mv ~/.vimrc ~/.vim /tmp && mkdir ~/.vim Then do: mv /tmp/.vimrc ~ && vim And test the behavior again. (Note that tools like Pathogen and the Vim-Addon-Manager will complicate this first step a bit). If the problem reappears descend into your ~/.vimrc and comment out half of it (with something like 50%:.,$s/^/" ) and find the section that is causing the problem. If it doesn't reappear, then move one of the pieces of /tmp/.vim/* back into ~/.vim/ and try again. Keep doing this until you find the source of your problem.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software