Add glossary and disambiguate cabal vs Cabal - #10631
Draft
philderbeast wants to merge 3 commits into
Draft
Conversation
philderbeast
marked this pull request as draft
December 10, 2024 02:40
geekosaur
reviewed
Dec 10, 2024
| satisfy this requirement. | ||
|
|
||
| When ``cabal.project`` doesn't exist, ``cabal-install`` fabricates an ephemeral | ||
| When ``cabal.project`` doesn't exist, :term:`cabal-install:exe:cabal` fabricates an ephemeral |
Collaborator
There was a problem hiding this comment.
In other places, cabal-install describes the package and cabal the command.
| :default: 1 | ||
|
|
||
| Control the verbosity of ``cabal`` commands, valid values are from 0 | ||
| Control the verbosity of :term:`cabal` commands, valid values are from 0 |
Collaborator
There was a problem hiding this comment.
…this line being an example
| :term:`cabal-install:exe:cabal` provides a system for external commands, akin to the ones used by tools like ``git`` or ``cargo``. | ||
|
|
||
| If you execute ``cabal <cmd>``, ``cabal-install`` will search the path for an executable named ``cabal-<cmd>`` and execute it. The name of the command is passed as the first argument and | ||
| If you execute ``cabal <cmd>``, :term:`cabal-install:exe:cabal` will search the path for an executable named ``cabal-<cmd>`` and execute it. The name of the command is passed as the first argument and |
Collaborator
There was a problem hiding this comment.
Mmm, and here's a third one for the same thing. Consistency would be nice.
philderbeast
force-pushed
the
doc/add-glossary
branch
from
December 27, 2024 14:23
962365d to
0779866
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
January 12, 2025 12:40
0779866 to
027a7ea
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
February 2, 2025 01:59
027a7ea to
450e18d
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
February 9, 2025 19:47
450e18d to
7b5b9b5
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
March 22, 2025 20:32
7b5b9b5 to
c013747
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
April 19, 2025 12:41
c013747 to
99f02ba
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
July 6, 2025 20:09
99f02ba to
5dfa20a
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
July 15, 2025 14:22
5dfa20a to
09e1b8c
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
2 times, most recently
from
July 25, 2025 12:28
565ff94 to
44af8d6
Compare
philderbeast
force-pushed
the
doc/add-glossary
branch
from
July 25, 2026 13:28
44af8d6 to
4c77648
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #9976, by referring to glossary terms.
Warning
Very much a draft but review comments are welcome. Am I on the right track with this?