dwl icon indicating copy to clipboard operation
dwl copied to clipboard

Update the wiki to allow patches per dwl version

Open sevz17 opened this issue 2 years ago • 3 comments

I think in something like this =================

Autostart

Description

Allow dwl to execute commands from autostart array in your config.h file. And when you exit dwm all processes from autostart array will be killed.

Example

static const char *const autostart[] = {
	"foot", "--server", NULL,
	"fnott", NULL,
	NULL
};

Attention

Commands from array are executed using execvp(). So if you need to execute shell command you need to prefix it with "sh", "-c" (change sh to any shell you like).

Download

git wlroots-next v0.3.1

sevz17 avatar Jun 13 '22 00:06 sevz17

Adding individual per-patch pages like you've templated looks fantastic!

Adding the option for patching per dwl version seems like a separate issue and not necessarily as appealing. Considering that individual patch contributors are often not developers who are carefully following the stable, AND git, AND wlroot-next, the likelihood that one patch will cleanly merge against more than one branch seems low. On the other hand, even if a patch is only intended and maintained for one branch, this method will at least make that clear.

Sidenote: @Sevz17 if you plan to maintain the autostart branch in your repo you've made to demo here, I will edit the existing wiki accordingly and happily turn over the autostart patch. It was your work to begin with.

fauxmight avatar Jun 14 '22 16:06 fauxmight

WIP: https://github.com/sevz17/dwl/wiki

sevz17 avatar Jun 22 '22 02:06 sevz17

This template looks great.

fauxmight avatar Jun 22 '22 03:06 fauxmight

Any update on this issue ?

Ogromny avatar Aug 31 '22 19:08 Ogromny

No, I haven't had enough time to work on this, and no one seems to have started to work on this, or shared their work.

sevz17 avatar Aug 31 '22 21:08 sevz17

I made a somewhat ready layout for the wiki. If everyone is satisfied with it I can start moving it to the main wiki and gradually updating the patches. Here's the link. Looking forward to your feedback.

dm1tz avatar Sep 02 '22 12:09 dm1tz

Hi @dm1tz, that looks amazing!, just a few comments

  • I don't mind sharing my email, but there may be people who do (even if they use their real address in commits)
  • related to the previous one, add something like this: ... then create a new page on the wiki using this example (you can add or remove sections as you like):
  • please s/Sevz17/sevz/

sevz17 avatar Sep 03 '22 01:09 sevz17

Hi @dm1tz, that looks amazing!, just a few comments

  • I don't mind sharing my email, but there may be people who do (even if they use their real address in commits)

Agree, I will remove email part.

  • related to the previous one, add something like this: ... then create a new page on the wiki using this example (you can add or remove sections as you like):
  • please s/Sevz17/sevz/

Will do. So may I start moving this template to the main wiki? Btw, I was thinking about overhauling the README a bit, for example we can move status information section to the wiki and mention the link to that instead.

dm1tz avatar Sep 03 '22 11:09 dm1tz

So may I start moving this template to the main wiki?

Sure

Btw, I was thinking about overhauling the README a bit, for example we can move status information section to the wiki and mention the link to that instead.

I'd like to keep that info in the README, but we can move the external bars to the wiki.

sevz17 avatar Sep 04 '22 03:09 sevz17

So may I start moving this template to the main wiki?

Sure

Btw, I was thinking about overhauling the README a bit, for example we can move status information section to the wiki and mention the link to that instead.

I'd like to keep that info in the README, but we can move the external bars to the wiki.

All done. Created a PR here.

dm1tz avatar Sep 04 '22 09:09 dm1tz

Many thanks

sevz17 avatar Sep 05 '22 21:09 sevz17