_ _ ___ | |__ __ _ _______ | |_ / _ \| '_ \ / _` |_ / _ \| __| | (_) | | | | (_| |/ / (_) | |_ \___/|_| |_|\__,_/___\___/ \__|
| ohazot | docs | links | dev | conf | txt |
| es | en (only, es pending / solamente en, es pendiente) |
| mdoc file |
| search |
suckless —
tools and usage
| st | : suckless simple terminal - usage and patches. |
| tabbed | : suckless tabbed interface - usage and patches. |
| surf | : suckless web browser. |
USAGE
Clone the repository and [make|make install|make clean install] as needed. Generally, any personal modifications can be done on config.def.h
PATCHES
Patches can be found in the <repository>/patches
- Clone git repository
cd <git_repository>- Get patch
wget <patch_url> - Apply patch
patch -p1 < <patch_file>
Rejects
Patches are generally created from the original source code. There may have conflicts with other patches if they apply to the same section. The changes that could not be applied will be saved to <filename>.rej. The pending changes can be applied manually.
personal
To make a personal modification combining all applied patches:
- Clone git repository
- Copy git repository to an alternate location for modifications.
cp -r repo repo_mod - Apply patches on the alternate directory
cd repo_mod wget patch1 wget patch2 patch -p1 < patch1 patch -p1 < patch2
- Modify config.def.h as needed.
- Remove the patches and .orig files
- Create a diff from the modified directory:
diff -up repo repo_mod > mod.diff - mod.diff can now be applied as needed.
TODO
| - Translate to Spanish. |
SEE ALSO
HISTORY
| 2026-07-06 | : Created. |