Skip to content

Conversation

@mbercx
Copy link
Contributor

@mbercx mbercx commented Sep 25, 2025

The documentation section was using both <build-path> and <build-dir>. This makes it unclear that they are both referring to the same string.

Here we choose to consistently use <build-path>, since it is a path to a directory.

The documentation section was using both `<build-path>` and `<build-dir>`. This makes it unclear that they are both referring to the same string.

Here we choose to consistently use `<build-path>`, since it is a path to a directory.
@mbercx
Copy link
Contributor Author

mbercx commented Sep 25, 2025

Not an expert on uenv (hence I'm reading the docs ^^), so feel free to close in case my assumption that build-path and build-dir are the same is incorrect.

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/268

Copy link
Member

@bcumming bcumming left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mbercx for improving the docs!

Technically, build-dir might be a little more appropriate, because in POSIX, path can be a directory, file, symlink etc.
But, it doesn't matter whether we use build-dir or build-path, so long as it is consistent.

@bcumming bcumming added this pull request to the merge queue Sep 25, 2025
Merged via the queue into eth-cscs:main with commit 39b3804 Sep 25, 2025
4 checks passed
@mbercx mbercx deleted the patch-1 branch September 25, 2025 04:47
@mbercx
Copy link
Contributor Author

mbercx commented Sep 25, 2025

Thanks @mbercx for improving the docs!

Very happy to contribute! Also: I'm back to using the CSCS facilities after a while, and I must say these new docs look spiffy. 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants