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)
close
On 08.04.23 23:43, Страхиња Радић wrote:
> On 23/04/08 07:24PM, p...@mailbox.org wrote:
> > static const char *dmenu_extend[] = { "dmenu_extended_run", NULL };
>
> How about:
>
> > > (Try changing your
> > > dmenu_extended keybind to something else and see if that works or not).
>
I tried t
On Sat, Apr 08, 2023 at 04:28:15PM +0200, p...@mailbox.org wrote:
> 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 her
On 23/04/08 07:24PM, p...@mailbox.org wrote:
> static const char *dmenu_extend[] = { "dmenu_extended_run", NULL };
How about:
> > (Try changing your
> > dmenu_extended keybind to something else and see if that works or not).
1. What happens if you use:
static const char *dmenu_exten
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 in
On Sat, Apr 08, 2023 at 07:24:07PM +0200, p...@mailbox.org wrote:
> - 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[] =
- 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 =
dmenu_extend
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 ques
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,
>
> Hi PFX,
>
> > I
> Hello everyone,
Hi PFX,
> 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]
> https://userf
Hi,
On Sat, Apr 08, 2023 at 04:28:15PM +0200, p...@mailbox.org wrote:
> 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 r
Is your mail provider enforcing mandatory TLS?
On Saturday, 8 April 2023 15:40:21 BST p...@mailbox.org wrote:
> 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 p
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]
https://userforum.mailbox.org/topic/65
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
dmenu_extended
14 matches
Mail list logo
