I had checked suckless.org on https://www.hardenize.com/, which report
`TLS, No support for STARTTLS`, but on checktls.com or testtls.com,
suckless.org is fine.
On 09.04.23 13:47, Quentin Rameau wrote:
>
> No, suckless.org MX configuration hasn't changed since last April (2022).
>
> Also, you
Voila, one single line of change make dmenu_extended_run launch again!
git diff dwm.c
diff --git a/dwm.c b/dwm.c
index c2bd871..f8f83f8 100644
--- a/dwm.c
+++ b/dwm.c
@@ -1653,6 +1653,7 @@ spawn(const Arg *arg)
if (dpy)
I built dwm based on https://aur.archlinux.org/packages/dwm-git
> diff config.h src/dwm/config.def.h
> 62d61
> < static const char *dmenu_extend[] = { "dmenu_extended_run", NULL };
> 67d65
> < { MODKEY, XK_o, spawn, {.v =
> dmenu_extend } },
in config.h
- patch is disabled
- `dwm 2> ~/dwm.log` shows nothing
define command as
static const char *dmenu_extend[] = { "dmenu_extended_run", NULL };
bind the command to a keyboard shortcut
static Key keys[] = {
MODKEY, XK_o, spawn, {.v =
they are not enforcing tls, since mx.suckless.org supported tls before,
according to their log, last time mx.suckless.org has tls on
2023-02-06, so they use the cache for the following email delivery, but
out of a sudden, mx.suckless.org downgrade to non tls, so email failed to
deliver.
so my
I am using the wrong words "not properly configured", what I mean is,
since mx.suckless.org supported tls connection before, but right now
mx.suckless.org downgraded to non tls, is this deliberately to be doing
so?
On 08.04.23 18:54, Quentin Rameau wrote:
> > Hello everyone,
>
Hello everyone,
I try to post to the list, but randomly failed with the error `TLS is
required, but was not offered by host mx.suckless.org` I report the
issue [1] to my email provider, it seems that mx.suckless.org somehow does
not properly configured.
[1]
Hello everyone,
I bind keyboard shortcut to launch dmenu_extended[1] in dwm, what works
flawlessly before the `Use sigaction(SA_NOCLDWAIT) for SIGCHLD
handling` [1] commit, since dmenu_extended does not change anything here,
is this a regression or bug introduced with this commit or
