From b98831ad96ddfb2368554368ad6301ddc33bc3c1 Mon Sep 17 00:00:00 2001 From: Alec Scott Date: Tue, 3 Jun 2025 17:22:27 -0700 Subject: [PATCH 1/2] Fix command-line to "command line" --- tutorial_basics.rst | 2 +- tutorial_buildsystems.rst | 4 ++-- tutorial_scripting.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tutorial_basics.rst b/tutorial_basics.rst index 5c9aeb082e..c5ea464dba 100644 --- a/tutorial_basics.rst +++ b/tutorial_basics.rst @@ -29,7 +29,7 @@ We will clone Spack and immediately check out the most recent release, v0.23. :language: console Next, add Spack to your path. -Spack has some nice command-line integration tools, so instead of simply prepending to your ``PATH`` variable, source the Spack setup script. +Spack has some nice command line integration tools, so instead of simply prepending to your ``PATH`` variable, source the Spack setup script. .. code-block:: console diff --git a/tutorial_buildsystems.rst b/tutorial_buildsystems.rst index d17bfbb95e..66b51707cb 100644 --- a/tutorial_buildsystems.rst +++ b/tutorial_buildsystems.rst @@ -114,7 +114,7 @@ Which is similar to invoking ``make`` in our Package make("foo") -This is useful if we have packages that ignore environment variables and need a command-line argument. +This is useful if we have packages that ignore environment variables and need a command line argument. Another thing to take note of is in the ``configure()`` method in ``AutotoolsPackage``. Here we see that the ``--prefix`` argument is already included since it is a common pattern amongst packages using ``Autotools``. @@ -273,7 +273,7 @@ Let's change the build and install phases of our package: :linenos: Here we demonstrate another strategy that we can use to manipulate our package's build. -We can provide command-line arguments to ``make()``. +We can provide command line arguments to ``make()``. Since ``Bowtie`` can use ``tbb`` we can either add ``NO_TBB=1`` as a argument to prevent ``tbb`` support, or we can invoke ``make`` with no arguments if TBB is desired and found by its build system. ``Bowtie`` requires our ``install_target`` to provide a path to the install directory. diff --git a/tutorial_scripting.rst b/tutorial_scripting.rst index 8687cb08c1..a075dcc260 100644 --- a/tutorial_scripting.rst +++ b/tutorial_scripting.rst @@ -45,7 +45,7 @@ You can generate that output with the following command: Note that ``name``, ``version``, and ``hash`` are attributes of Spack's internal ``Spec`` object and enclosing them in braces ensures they are output according to your format string. -Using ``spack find --format`` allows you to retrieve just the information you need to do things like pipe the output to typical UNIX command-line tools like ``sort`` or ``uniq``. +Using ``spack find --format`` allows you to retrieve just the information you need to do things like pipe the output to typical UNIX command line tools like ``sort`` or ``uniq``. ^^^^^^^^^^^^^^^^^^^^^ ``spack find --json`` From 7f7e23de68d834cb21be088265d8c6e1606e0da0 Mon Sep 17 00:00:00 2001 From: Alec Scott Date: Tue, 3 Jun 2025 22:06:31 -0700 Subject: [PATCH 2/2] Fix uppercase variants as well --- tutorial_configuration.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tutorial_configuration.rst b/tutorial_configuration.rst index c9d6f4b4c0..16f297d99e 100644 --- a/tutorial_configuration.rst +++ b/tutorial_configuration.rst @@ -27,7 +27,7 @@ A partial list of some key configuration sections is provided below. * - compilers - Define the compilers that Spack can use (required and system specific) * - Mirrors - - Locations where spack can look for stashed source or binary distributions + - Locations where spack can look for stashed source or binary distributions * - Packages - Specific settings and rules for packages * - Modules @@ -97,7 +97,7 @@ These scopes, in order of decreasing priority, are: ============ =================================================== Scope Directory ============ =================================================== -Command-line N/A +Command Line N/A Environment In environment base directory (in ``spack.yaml``) Custom Custom directory, specified with ``--config-scope`` User ``~/.spack/``