Common settings (all editions) for Garuda Linux
d42fe80486
Remove ctrl+backspace > DeleteWordLeft binding.
This is a good binding and I think it makes sense to have it as a default, however
during testing I have discovered that not all terminals present these keys to Micro
the same way. For example, in Xterm for some reason "OldBackspace" is the backspace
key and "Backspace" is ctrl+backspace, so unfortunately just pressing backspace invokes
DeleteWordLeft with the binding as committed.
In the case of Xterm, the correct way to bind ctrl+backspace to DeleteWordLeft would be
like this:
"Backspace": "DeleteWordLeft",
"OldBackspace": "Backspace"
In any case, it is probably best we do not set this by default and leave it up to the user
to decide if they would like to set this binding on their own.
|
||
|---|---|---|
| .gitlab | ||
| etc | ||
| usr | ||
| .cz.yaml | ||
| .gitlab-ci.yml | ||
| LICENSE | ||
| README.md | ||
Garuda Linux common settings
Found any issue?
- If any packaging issues occur, don't hesitate to report them via our issues section of our PKGBUILD repo. You can click here to create a new one.
- If issues concerning the configurations and settings occur, please open a new issue on this repository. Click here to start the process.
How to contribute?
We highly appreciate contributions of any sort! 😊 To do so, please follow these steps:
- Create a fork of this repository.
- Clone your fork locally (short git tutorial).
- Add the desired changes to PKGBUILDs or source code.
- Commit using a conventional commit message and push any changes back to your fork. This is crucial as it allows our CI to generate changelogs easily.
- The commitizen application helps with creating a fitting commit message.
- You can install it via pip as there is currently no package in Arch repos:
pip install --user -U Commitizen. - Then proceed by running
cz commitin the cloned folder.
- Create a new merge request at our main repository.
- Check if any of the pipeline runs fail and apply eventual suggestions.
We will then review the changes and eventually merge them.
Where is the PKGBUILD?
The PKGBUILD can be found in our PKGBUILDs repository. Accordingly, packaging changes need to be happening over there.
How to deploy a new version?
To deploy a new version, pushing a new tag is sufficient. The deployment will happen automatically via the PKGBUILDs repo's pipelines, which check half-hourly for the existance of a more recent tag.