--- Begin Message ---
Subject: |
i3-gaps package is misbehaving |
Date: |
Wed, 25 Dec 2019 08:29:59 +0000 |
I submitted a patch to add i3-gaps a couple days ago:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38721
After it got merged into master with the inheritance modification (see
patch), I installed it over the one I had installed from my original
script and it seemed to work fine. But I think that's just because I
didn't reboot to restart the i3 executable.
Now that I shutdown and opened my machine again, i3-gaps specific
commands don't work... To test this, write `i3-msg gaps` in a shell.
If it does NOT work, it will output something like:
brown@121407 ~$ i3-msg gaps
ERROR: Your command: gaps
ERROR: ^^^^
ERROR: Expected one of these tokens: <a long list of stuff that
represent valid commands>
However, it seems that gaps work if I remove the package, install it
from the original package definition (without Brett's (inherit i3-wm))
and reboot. The following output means that i3-gaps has been correctly
installed:
brown@121407 ~$ i3-msg gaps
ERROR: Your command: gaps
ERROR:
ERROR: Expected one of these tokens: 'inner', 'outer', 'horizontal',
'vertical', 'top', 'right', 'bottom', 'left'
This is strange. I still don't know enough about the packaging API to
troubleshoot this all just by having a quick look at i3-gaps'
definition. I'll try to investigate this issue but I encourage someone
more knowledgeable than me too look into this too.
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#38739: i3-gaps package is misbehaving |
Date: |
Thu, 26 Dec 2019 15:50:27 +0100 |
User-agent: |
Notmuch/0.29.3 (https://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu) |
Sergiu Marton <address@hidden> writes:
> Tried installing i3-gaps on a fresh VM with Guix. Still the same
> problem when getting it from the official sources. Gaps aren't
> working. When installing from a file that has the original definition
> (without inheritance), gaps work. So it's exactly the same situation.
> Wanted to be sure.
I believe this is fixed with 3ebaa635f7a4e2178b321f949e533402e3cf2987.
The problem was that the original i3-wm checksum appears to have been
copy-pasted during the refactor.
Thanks!
signature.asc
Description: PGP signature
--- End Message ---