From: woffs <woffs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Can't customize XMonad
Date: Tue, 26 Oct 2021 16:48:35 +0200 [thread overview]
Message-ID: <20211026144835.cGfBrE2RMc489pMzJsIMfyJ3NVRP-SCMejURhaQ_vqY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-6414@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
New comment by woffs on void-packages repository
https://github.com/void-linux/void-packages/issues/6414#issuecomment-952017464
Comment:
>> @xaltsc should xmobar be added to that list as well ? I don't know if
>> xmobar can be used on other WM ... If not I will added it to the commit
>
> I don't use xmobar anymore, but there's a chance that xmobar may work if
> the binary is successfully instance since xmobar can be used without a
> xmobar.hs.
xmobar is fine and works well.
next prev parent reply other threads:[~2021-10-26 14:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-6414@inbox.vuxu.org>
2019-10-13 3:31 ` voidlinux-github
2020-10-15 4:22 ` Rex-Official
2020-11-18 1:13 ` chilledfrogs
2021-01-14 23:42 ` jchook
2021-01-14 23:51 ` jchook
2021-01-15 0:51 ` jchook
2021-01-15 0:51 ` jchook
2021-01-15 1:04 ` jchook
2021-01-15 1:13 ` jchook
2021-01-15 1:51 ` jchook
2021-01-15 1:52 ` jchook
2021-02-15 14:39 ` ericonr
2021-03-06 22:50 ` jchook
2021-03-13 16:04 ` xaltsc
2021-10-25 7:36 ` motorto
2021-10-25 13:22 ` ericonr
2021-10-25 15:00 ` motorto
2021-10-25 19:08 ` ericonr
2021-10-25 20:24 ` motorto
2021-10-25 22:47 ` jchook
2021-10-26 4:07 ` xaltsc
2021-10-26 4:08 ` xaltsc
2021-10-26 4:10 ` xaltsc
2021-10-26 14:48 ` woffs [this message]
2021-11-08 19:10 ` Chocimier
2021-11-08 19:10 ` [ISSUE] [CLOSED] " Chocimier
2022-02-17 14:12 ` riseekrthakur
2022-02-17 22:13 ` jchook
2022-02-18 13:47 ` riseekrthakur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211026144835.cGfBrE2RMc489pMzJsIMfyJ3NVRP-SCMejURhaQ_vqY@z \
--to=woffs@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).