collapse multiple empty lines into a single empty line

doc/src/Build_development.rst

@@ -4,10 +4,8 @@ Development build options (CMake only)
 The CMake build of LAMMPS has a few extra options which are useful during
 development,  testing or debugging.
 
-
 ----------
 
-
 .. _compilation:
 
 Verify compilation flags
@@ -17,22 +15,18 @@ Sometimes it is necessary to verify the complete sequence of compilation flags
 generated by the CMake build. To enable a more verbose output during
 compilation you can use the following option.
 
-
 .. code-block:: bash
 
    -D CMAKE_VERBOSE_MAKEFILE=value    # value = no (default) or yes
 
 Another way of doing this without reconfiguration is calling make with variable VERBOSE set to 1:
 
-
 .. code-block:: bash
 
    make VERBOSE=1
 
-
 ----------
 
-
 .. _sanitizer:
 
 Address, Undefined Behavior, and Thread Sanitizer Support
@@ -47,17 +41,14 @@ The following settings allow you enable these features if your compiler supports
 it. Please note that they come with a performance hit. However, they are
 usually faster than using tools like Valgrind.
 
-
 .. code-block:: bash
 
    -D ENABLE_SANITIZE_ADDRESS=value    # enable Address Sanitizer, value = no (default) or yes
    -D ENABLE_SANITIZE_UNDEFINED=value  # enable Undefined Behaviour Sanitizer, value = no (default) or yes
    -D ENABLE_SANITIZE_THREAD=value     # enable Thread Sanitizer, value = no (default) or yes
 
-
 ----------
 
-
 .. _testing:
 
 Code Coverage and Testing
@@ -71,7 +62,6 @@ developers can run the tests directly on their workstation.
 
    this is incomplete and only represents a small subset of tests that we run
 
-
 .. code-block:: bash
 
    -D ENABLE_TESTING=value               # enable simple run tests of LAMMPS, value = no (default) or yes
@@ -80,7 +70,6 @@ developers can run the tests directly on their workstation.
 
 If you enable testing in the CMake build it will create an additional target called "test". You can run them with:
 
-
 .. code-block:: bash
 
    make test
@@ -92,14 +81,12 @@ faster.
 You can also collect code coverage metrics while running the tests by enabling
 coverage support during building.
 
-
 .. code-block:: bash
 
    -D ENABLE_COVERAGE=value  # enable coverage measurements, value = no (default) or yes
 
 This will also add the following targets to generate coverage reports after running the LAMMPS executable:
 
-
 .. code-block:: bash
 
    make test               # run tests first!
@@ -108,7 +95,6 @@ This will also add the following targets to generate coverage reports after runn
 
 These reports require GCOVR to be installed. The easiest way to do this to install it via pip:
 
-
 .. code-block:: bash
 
    pip install git+https://github.com/gcovr/gcovr.git