Use :gmt-docs: instead of full links

[seisman]

Description of proposed changes

Fixes #

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

• /format: automatically format and lint the code
• /test-gmt-dev: run full tests on the latest GMT development version

[yvonnefroehlich]

In the Contributors Guide, in the section "Cross-referencing with Sphinx", we also should update the example link for the GMT configuration parameters from "latest" to "6.4":

An example would be using :gmt-docs:makecpt.html to link to https://docs.generic-mapping-tools.org/6.4/makecpt.html. For GMT configuration parameters, an example is :gmt-term:COLOR_FOREGROUND to link to https://docs.generic-mapping-tools.org/latest/gmt.conf#term-COLOR_FOREGROUND.

[seisman]

In the Contributors Guide, in the section "Cross-referencing with Sphinx", we also should update the example link for the GMT configuration parameters from "latest" to "6.4":

An example would be using :gmt-docs:makecpt.html to link to https://docs.generic-mapping-tools.org/6.4/makecpt.html. For GMT configuration parameters, an example is :gmt-term:COLOR_FOREGROUND to link to https://docs.generic-mapping-tools.org/latest/gmt.conf#term-COLOR_FOREGROUND.

Yes, I also saw this one. I'm a little hesitate to update "latest" to "6.4", because doing that means we also need to update it when we bump to GMT 6.5. Actually, I feel we should change

For GMT configuration parameters, an example is
<code>:gmt-term:\`COLOR_FOREGROUND\`</code> to link to
{gmt-term}`https://docs.generic-mapping-tools.org/latest/gmt.conf#term-COLOR_FOREGROUND <COLOR_FOREGROUND>`.

to

For GMT configuration parameters, an example is
<code>:gmt-term:\`COLOR_FOREGROUND\`</code> to link to
{gmt-term}`COLOR_FOREGROUND`.

[yvonnefroehlich]

In the Contributors Guide, in the section "Cross-referencing with Sphinx", we also should update the example link for the GMT configuration parameters from "latest" to "6.4":

An example would be using :gmt-docs:makecpt.html to link to https://docs.generic-mapping-tools.org/6.4/makecpt.html. For GMT configuration parameters, an example is :gmt-term:COLOR_FOREGROUND to link to https://docs.generic-mapping-tools.org/latest/gmt.conf#term-COLOR_FOREGROUND.

Yes, I also saw this one. I'm a little hesitate to update "latest" to "6.4", because doing that means we also need to update it when we bump to GMT 6.5. Actually, I feel we should change

For GMT configuration parameters, an example is
<code>:gmt-term:\`COLOR_FOREGROUND\`</code> to link to
{gmt-term}`https://docs.generic-mapping-tools.org/latest/gmt.conf#term-COLOR_FOREGROUND <COLOR_FOREGROUND>`.

to

For GMT configuration parameters, an example is
<code>:gmt-term:\`COLOR_FOREGROUND\`</code> to link to
{gmt-term}`COLOR_FOREGROUND`.

Actually, your suggested change was my first idea of how to update it. But then I thought that it was maybe intended to show the complete link. However, I am fine with your suggestion, as it shows how the link finally appears in the documentation.