Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Suckless Updates, Refactor Config.h and Enhance dwm Performance #242

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

fesowowako
Copy link

@fesowowako fesowowako commented Feb 25, 2024

Suckless Updates: Integrate latest dwm updates from the Suckless project.
Config.h Refactor: Improve readability of config.h, resolving past formatting issues.
In the dwm.c modification, I swapped the fork() and execvp() code for posix_spawnp(). This change enhances efficiency by minimising system calls, which speeds up process creation. posix_spawnp() also offers finer control over the new process, such as setting attributes, optimising its performance.

@fesowowako fesowowako changed the title Merge Suckless Updates and Refactor Config.h Merge Suckless Updates, Refactor Config.h and Enhance dwm Performance Feb 25, 2024
@narukeh
Copy link

narukeh commented Mar 22, 2024

This seems pretty nice. As for the formating, i have added this:
/* vim:set ts=8 sw=8: */
at the top of the file, then "long-cells-in-coulums" look better, though not always :D

Could you, mayhaps, implement #222?

@fesowowako
Copy link
Author

In the latest config.mk update, I've upgraded the version to 6.5 and introduced an optional optimisations flag for those who wish to utilise them. Additionally, I've included the -Wno-unused-function flag in the CFLAGS, which suppresses warnings about unused functions, thereby removing dead code.

@fesowowako
Copy link
Author

This seems pretty nice. As for the formating, i have added this: /* vim:set ts=8 sw=8: */ at the top of the file, then "long-cells-in-coulums" look better, though not always :D

Could you, mayhaps, implement #222?

I will investigate it and aim to implement it within the next three weeks, though I am quite busy at the moment.

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.

None yet

2 participants