Inform newcommers about SCRIPT_DIR env #421
Open
Conversation
This file contains 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
Added some note about SCRIPT_DIR, as it was one of two glitches for me (newcomer to i3blocks), when I have followed this documentation.
luvarqpp
added a commit
to luvarqpp/i3blocks-contrib
that referenced
this pull request
Apr 11, 2020
Fixed path for command. By default when following documentation on https://vivien.github.io/i3blocks/ there are commands in directories. This was missing in example script. Added some clarification for `$SCRIPT_DIR` thing. Also made another pull request to clarify this in documentation. See vivien/i3blocks#421
dllud
pushed a commit
to dllud/i3blocks
that referenced
this pull request
Jan 12, 2024
volume-pipewire fix forward sinks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added some note about SCRIPT_DIR, as it was one of two glitches for me (newcomer to i3blocks), when I have followed this documentation.