From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Strange Xmonad problem
Date: Sun, 1 Oct 2017 15:45:55 -0500 [thread overview]
Message-ID: <CAAD4mYhMC_uTZ01ne0OZCzUPr7raOWJziRmV6E_CiXhdNaNnVA@mail.gmail.com> (raw)
In-Reply-To: <873773us0j.fsf@openmailbox.org>
On Sun, Oct 1, 2017 at 4:38 AM, Melleus <melleus@openmailbox.org> wrote:
> Simon Thelen <gentoo-user@c-14.de> writes:
>
>>> This config doesn't work either. It looks like something is seriously
>>> broken in this version of Xmonad (0.13). It's a pity that it has a stable
>>> keyword. Will wait for updates. Sorry for the noise. And thank you for attention.
>> I'm running 0.13 (and have been since February) so I doubt it's that.
>> Though it could be related to the earlier issue with the state file. I
>> didn't delete that in my tests.
>
> It (v0.13) does have bugs: a bug with that xmonad.state file that keeps
> appearing, a bug with xmobar that one have to put docksEventHook in
> config to make it respect the size of other windows again, configs from
> previous versions that do not work like they should. I understand that
> those are minor bugs for experienced users, but the testing keyword for
> this version would benefit and save from trouble such new converts to
> Gentoo as I am.
>
This is the reason I suggest following the repository (via secure
checkout, which some ebuilds do not do). There is a strange place in
between "Debian stable" and "live checkout" that tends to have more
harder to fix bugs than the "live checkout" version does. The problem
with "Debian stable" is that it typically is lacking features an
informed user would want.
If you end up fixing the issue in the live version then you can more
easily submit a pull request. If not, you can still revert to an old
release.
Cheers,
R0b0t1
prev parent reply other threads:[~2017-10-01 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 16:22 [gentoo-user] Strange Xmonad problem Melleus
2017-09-27 21:06 ` Simon Thelen
2017-09-27 23:40 ` R0b0t1
2017-09-28 17:56 ` [gentoo-user] " Melleus
2017-09-28 17:30 ` Melleus
2017-09-28 18:27 ` Simon Thelen
2017-09-29 9:13 ` Melleus
2017-09-29 14:13 ` Simon Thelen
2017-09-29 19:09 ` Melleus
2017-09-30 0:22 ` Simon Thelen
2017-10-01 9:38 ` Melleus
2017-10-01 20:45 ` R0b0t1 [this message]
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=CAAD4mYhMC_uTZ01ne0OZCzUPr7raOWJziRmV6E_CiXhdNaNnVA@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=gentoo-user@lists.gentoo.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