Re: [i3] i3 4.10.2 i3-save-tree perl module missing
I'm using ubuntu 14.04. Can someone please provide guidance relative to how to fix the following. What package do I need to install? ubuntu@sensis-8930:/var/www/cwpmash/app$ i3-save-tree Can't locate AnyEvent/I3.pm in @INC (you may need to install the AnyEvent::I3 module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at /usr/bin/i3-save-tree line 19. BEGIN failed--compilation aborted at /usr/bin/i3-save-tree line 19. This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.
Re: [i3] i3 4.10.2 crash ---- isolated
One crash location found (con.c line 393), reference through null pointer: [cid:image001.png@01D0A9AA.222B9380] I3-with-shmlog is indeed the process to attach to. I started i3 clean, and then as root I was able to attach to this process. For some reason, though i3 is running as ubuntu, I was not able to attach as ubuntu. Once attached, I then initiated the sequence of events that I expected to crash i3, the crash did indeed occur (so this is quite repeatable). I'll continue to see if I can isolate other crash points. I'll post a bug on the bug tracker to ensure that this hits Michael's radar. From: Sargrad, Dave Sent: Thursday, June 18, 2015 9:16 AM To: 'i3-discuss@i3.zekjur.net' Subject: i3 4.10.2 crash I3 4.10.2 has crashed on me. I've seen crashes before but have ignored them. I'm interested in seeing if I can isolate the crash, particularly since I think I know how to repeat the crash. Once isolated I can provide feedback to the dev team. I am currently presented with the crash response window (red border with options to: attach gdb, save a backtracke, restart i3 in place, forget the current layout and restart i3). When I putty into the box and see what i3 processes are running (with an eye towards attaching gdb), I see the following: ubuntu@sensis-8930:~$ ps -aef | grep i3 ubuntu2349 2075 0 Jun17 ?00:00:01 i3-with-shmlog ubuntu2420 2349 0 Jun17 ?00:00:00 /usr/bin/ssh-agent /usr/bin/dbus -launch --exit-with-session /usr/bin/im-launch i3-with-shmlog ubuntu2423 1 0 Jun17 ?00:00:00 /usr/bin/dbus-launch --exit-with -session /usr/bin/im-launch i3-with-shmlog ubuntu2484 1 0 Jun17 ?00:00:00 /bin/sh -c i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.2349 ubuntu2485 2484 0 Jun17 ?00:00:29 i3bar --bar_id=bar-0 --socket=/r un/user/1000/i3/ipc-socket.2349 ubuntu2487 2485 0 Jun17 ?00:00:00 /bin/sh -c i3status ubuntu2489 2487 0 Jun17 ?00:00:24 i3status ubuntu2510 1 0 Jun17 ?00:00:00 /bin/sh -c i3-sensible-terminal ubuntu6031 6005 0 12:12 pts/100:00:00 grep --color=auto i3 The area that I built i3 out of is: /home/ubuntu/work/i3/i3-4.10.2 This is where I should be able to find the source code and symbol files required by gdb. I've attached gdb to debuggable processes in the past (I don't need help with that). I do need some guidance relative to the following questions: 1] If I save a backtrace, where will that get saved on the system 2] Of the processes listed above, which one do I attach to (I don't see i3.. perhaps i3-with-shmlog)? 3] What are the commands that I should enter into gdb so that it loads the proper symbol files? Thanks for any thoughts or guidance. ubuntu@sensis-8930:~/work/i3$ ls i3-4.10.2 i3-4.10.2.tar.bz2 i3status-2.9 i3status-2.9.tar.bz2 This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.
Re: [i3] i3-discuss Digest, Vol 55, Issue 2
Thank You Michael. I'll try that today or Monday, and will let you know how it
works for me.
Appreciated.
-Original Message-
From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of
i3-discuss-requ...@i3.zekjur.net
Sent: Friday, November 07, 2014 6:02 AM
To: i3-discuss@i3.zekjur.net
Subject: i3-discuss Digest, Vol 55, Issue 2
Send i3-discuss mailing list submissions to
i3-discuss@i3.zekjur.net
To subscribe or unsubscribe via the World Wide Web, visit
http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss
or, via email, send a message with subject or body 'help' to
i3-discuss-requ...@i3.zekjur.net
You can reach the person managing the list at
i3-discuss-ow...@i3.zekjur.net
When replying, please edit your Subject line so it is more specific than Re:
Contents of i3-discuss digest...
Today's Topics:
1. Re: i3 4.8 layout file hides my status bar and floating
windows (Michael Stapelberg)
--
Message: 1
Date: Fri, 7 Nov 2014 09:48:06 +0100
From: Michael Stapelberg mich...@stapelberg.ch
To: Discussions/Questions about the i3 window manager
i3-discuss@i3.zekjur.net
Subject: Re: [i3] i3 4.8 layout file hides my status bar and floating
windows
Message-ID:
cannvg6mjigmg8er1qaxdmv_1n1tpi7+p4-by8-xqkgug35k...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
You’re saying you’re running v4.8. I think the problem you are seeing is fixed
with commit 679a5de8cfb9211afb1a1dd882e53bd672084754, so please upgrade to the
“next” git branch and retry. Check the output
“i3 --moreversion”, it should display “Running i3 version:
4.8-115-g0125530 (2014-11-06, branch next)”
On Wed, Nov 5, 2014 at 2:18 PM, Sargrad, Dave dave.sarg...@saabsensis.com
wrote:
I am using i3 4.8 with the layout file at the bottom of this e-mail.
When I append this, everything works ok (my windows layout as I expect them
too, and applications get swallowed correctly) except I hide my status bar
(the roughly 20 pixel high status bar that includes a set of buttons that
allows me to select workspaces to focus). The status bar still exists, but it
seems to be hidden by the appended layout. The other problem is that when I
toggle a tiled window to a floating window it also gets hidden rather than
floating properly (within this appended workspace).
Two other notes of interest, when I close all the windows in this appended
layout i3 seems to hang for a bit (as evidenced by the hourglass cursor)
before it finally returns to normal operation. Additionally despite the fact
that other workspaces are not directly accessible (since I can't get to the
workspace selector in the statusbar), I am able to send them a focus message
and they do focus properly. I am also able to send the appended workspace
(the one that has this hiding problem) a focus message and have it come
back into focus.
How can I tweak this layout so that I don’t hide my statusbar and floating
windows?
{
border: normal,
floating: auto_off,
fullscreen_mode: 1,
layout: splith,
nodes: [
{
border: normal,
floating: user_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:~/work/cwpmash,
percent: 0.5,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
layout: splitv,
nodes: [
{
border: normal,
floating: auto_off,
layout: splith,
nodes: [
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:~,
percent: 0.40875593123030751,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 499
Re: [i3] i3-discuss Digest, Vol 55, Issue 2
I just applied patch 679a5de8cfb9211afb1a1dd882e53bd672084754. Unfortunately I
still see the very same behavior.
I also changed the following line (as suggested by one of the other i3 users)
fullscreen_mode: 1,
To
fullscreen_mode: 0,
This too did not fix the problem.
Please let me know if you would like me to try something else.
Thanks.
I3_VERSION := '$(shell [ -f $(TOPDIR)/I3_VERSION ] cat $(TOPDIR)/I3_VERSION)'
VERSION := '$(shell [ -f $(TOPDIR)/VERSION ] cat $(TOPDIR)/VERSION)'
ifeq ('',$(I3_VERSION))
VERSION := $(shell git describe --tags --abbrev=0)
I3_VERSION := '$(shell git describe --tags --always) ($(shell git log --pretty=f
ormat:%cd --date=short -n1), branch \$(shell git describe --tags --always --all
| sed s:heads/::)\)'
Endif
I think I can just change the VERSION set after ifeq to something
-Original Message-
From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of
i3-discuss-requ...@i3.zekjur.net
Sent: Friday, November 07, 2014 6:02 AM
To: i3-discuss@i3.zekjur.net
Subject: i3-discuss Digest, Vol 55, Issue 2
Send i3-discuss mailing list submissions to
i3-discuss@i3.zekjur.net
To subscribe or unsubscribe via the World Wide Web, visit
http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss
or, via email, send a message with subject or body 'help' to
i3-discuss-requ...@i3.zekjur.net
You can reach the person managing the list at
i3-discuss-ow...@i3.zekjur.net
When replying, please edit your Subject line so it is more specific than Re:
Contents of i3-discuss digest...
Today's Topics:
1. Re: i3 4.8 layout file hides my status bar and floating
windows (Michael Stapelberg)
--
Message: 1
Date: Fri, 7 Nov 2014 09:48:06 +0100
From: Michael Stapelberg mich...@stapelberg.ch
To: Discussions/Questions about the i3 window manager
i3-discuss@i3.zekjur.net
Subject: Re: [i3] i3 4.8 layout file hides my status bar and floating
windows
Message-ID:
cannvg6mjigmg8er1qaxdmv_1n1tpi7+p4-by8-xqkgug35k...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
You’re saying you’re running v4.8. I think the problem you are seeing is fixed
with commit 679a5de8cfb9211afb1a1dd882e53bd672084754, so please upgrade to the
“next” git branch and retry. Check the output
“i3 --moreversion”, it should display “Running i3 version:
4.8-115-g0125530 (2014-11-06, branch next)”
On Wed, Nov 5, 2014 at 2:18 PM, Sargrad, Dave dave.sarg...@saabsensis.com
wrote:
I am using i3 4.8 with the layout file at the bottom of this e-mail.
When I append this, everything works ok (my windows layout as I expect them
too, and applications get swallowed correctly) except I hide my status bar
(the roughly 20 pixel high status bar that includes a set of buttons that
allows me to select workspaces to focus). The status bar still exists, but it
seems to be hidden by the appended layout. The other problem is that when I
toggle a tiled window to a floating window it also gets hidden rather than
floating properly (within this appended workspace).
Two other notes of interest, when I close all the windows in this appended
layout i3 seems to hang for a bit (as evidenced by the hourglass cursor)
before it finally returns to normal operation. Additionally despite the fact
that other workspaces are not directly accessible (since I can't get to the
workspace selector in the statusbar), I am able to send them a focus message
and they do focus properly. I am also able to send the appended workspace
(the one that has this hiding problem) a focus message and have it come
back into focus.
How can I tweak this layout so that I don’t hide my statusbar and floating
windows?
{
border: normal,
floating: auto_off,
fullscreen_mode: 1,
layout: splith,
nodes: [
{
border: normal,
floating: user_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:~/work/cwpmash,
percent: 0.5,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
layout: splitv,
nodes: [
{
border: normal,
floating: auto_off,
layout: splith,
nodes: [
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 499,
x: 0
[i3] i3 4.8 layout file hides my status bar and floating windows
I am using i3 4.8 with the layout file at the bottom of this e-mail.
When I append this, everything works ok (my windows layout as I expect them
too, and applications get swallowed correctly) except I hide my status bar (the
roughly 20 pixel high status bar that includes a set of buttons that allows me
to select workspaces to focus). The status bar still exists, but it seems to be
hidden by the appended layout. The other problem is that when I toggle a tiled
window to a floating window it also gets hidden rather than floating properly
(within this appended workspace).
Two other notes of interest, when I close all the windows in this appended
layout i3 seems to hang for a bit (as evidenced by the hourglass cursor) before
it finally returns to normal operation. Additionally despite the fact that
other workspaces are not directly accessible (since I can't get to the
workspace selector in the statusbar), I am able to send them a focus message
and they do focus properly. I am also able to send the appended workspace (the
one that has this hiding problem) a focus message and have it come back into
focus.
How can I tweak this layout so that I don’t hide my statusbar and floating
windows?
{
border: normal,
floating: auto_off,
fullscreen_mode: 1,
layout: splith,
nodes: [
{
border: normal,
floating: user_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:~/work/cwpmash,
percent: 0.5,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
layout: splitv,
nodes: [
{
border: normal,
floating: auto_off,
layout: splith,
nodes: [
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:~,
percent: 0.40875593123030751,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:~/work/cwpmash,
percent: 0.25791073543635906,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 499,
x: 0,
y: 0
},
layout: splith,
name: user1@company-90076-2:/home/user1,
percent: 0.33343,
swallows: [
{
class: ^XTerm$
}
],
type: con
}
],
percent: 0.2966101694915253,
type: con
},
{
border: normal,
floating: user_off,
geometry: {
height: 993,
width: 1337,
x: 0,
y: 0
},
layout: splith,
name: mashup - Mozilla Firefox,
percent: 0.70338983050847459,
[i3] Struggling to build i3 4.8 on centos 6.5 - but almost there
I am very close to building i3 4.8 on centos 6.5, and will post my procedures once I get them to be clean. I’ve successfully built i3 4.8 in the past on ubuntu 14.04, but am now moving to centos 6.5. I am seeing the error message included at the bottom of this e-mail. I found the following link that is related: http://infra.in.zekjur.net/pipermail/i3-discuss/2013-February/001199.html Within that chain of emails Michael indicates that the following command will fix the problem: git submodule update –init I am not using git, so this command will not help me. I started with a bare vanilla installation of centos. Once I downloaded i3 4.8 I modified common.mk to disable pango. I then downloaded and built the following packages (I’ve indicated the version that I have downloaded and the version range provided in the i3 DEPENDS file): pango disabled cairo 1.12.2 depends 1.12.2 - 1.12.2 pixman 0.22.0depends not specified (was needed for cairo) yajl 2.0.4 depends 2.0.1 - 2.0.4 libxcb 1.7 depends 1.1.93 - 1.7 xcb-util 0.3.8 depends 0.3.3 - 0.3.8 xcb-util-cursor 0.1.1 depends 0.0.99 - 0.0.99 libev 4.11 depends 4.0 - 4.11 I actually tried 0.0.99 for xcb-util-cursor, but ran into another small problem that disappeared with 0.1.1. Anyways I don’t think this is the source of my current issue. The exact links for the files I downloaded and built are: http://cairographics.org/releases/cairo-1.12.2.tar.xz http://cairographics.org/releases/pixman-0.22.0.tar.gz http://github.com/lloyd/yajl/zipball/2.0.4 http://xcb.freedesktop.org/dist/libxcb-1.7.tar.bz2 http://xcb.freedesktop.org/dist/xcb-util-0.3.8.tar.bz2 http://xcb.freedesktop.org/dist/xcb-util-cursor-0.1.1.tar.bz2 http://dist.schmorp.de/libev/Attic/libev-4.11.tar.gz I have successfully gotten past most of my compile issues. I am left with the following: Compile Time Error Follows [i3] CC src/handlers.c ../i3-4.8/src/handlers.c: In function ‘handle_normal_hints’: ../i3-4.8/src/handlers.c:831: warning: implicit declaration of function ‘xcb_icccm_get_wm_size_hints_from_reply’ ../i3-4.8/src/handlers.c:833: warning: implicit declaration of function ‘xcb_icccm_get_wm_normal_hints_reply’ ../i3-4.8/src/handlers.c:833: warning: implicit declaration of function ‘xcb_icccm_get_wm_normal_hints_unchecked’ ../i3-4.8/src/handlers.c:835: error: ‘XCB_ICCCM_SIZE_HINT_P_MIN_SIZE’ undeclared (first use in this function) ../i3-4.8/src/handlers.c:835: error: (Each undeclared identifier is reported only once ../i3-4.8/src/handlers.c:835: error: for each function it appears in.) ../i3-4.8/src/handlers.c:841: error: ‘XCB_ICCCM_SIZE_HINT_P_RESIZE_INC’ undeclared (first use in this function) ../i3-4.8/src/handlers.c:862: error: ‘XCB_ICCCM_SIZE_HINT_BASE_SIZE’ undeclared (first use in this function) ../i3-4.8/src/handlers.c:881: error: ‘XCB_ICCCM_SIZE_HINT_P_ASPECT’ undeclared (first use in this function) ../i3-4.8/src/handlers.c: In function ‘handle_hints’: ../i3-4.8/src/handlers.c:936: warning: implicit declaration of function ‘xcb_icccm_get_wm_hints’ ../i3-4.8/src/handlers.c:936: error: incompatible type for argument 2 of ‘xcb_get_property_reply’ /usr/local/cwp/include/xcb/xproto.h:7306: note: expected ‘xcb_get_property_cookie_t’ but argument is of type ‘int’ make: *** [src/handlers.o] Error 1 Please help me to understand how to fix this. Thanks in advance. This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.
Re: [i3] Struggling to build i3 4.8 on centos 6.5 - but almost there
Johannes, Thanks again for helping me past that compile issue. I am now attempting to link. I got past a problem with a spurious -l by changing how I disabled pango. Apparently the proper way to disable pango is as follows (common.mk snippet): #PANGO_CFLAGS := $(call cflags_for_lib, cairo) #PANGO_CFLAGS += $(call cflags_for_lib, pangocairo) I3_CPPFLAGS += -DPANGO_SUPPORT=0 #PANGO_LIBS := $(call ldflags_for_lib, cairo) #PANGO_LIBS += $(call ldflags_for_lib, pangocairo) The link issue I am seeing is an undefined xcb symbol: [i3] Link i3 /usr/lib64/libxcb-render.so.0: undefined reference to `xcb_str_sizeof' collect2: ld returned 1 exit status make: *** [i3] Error 1 I found the following online: http://www.murga-linux.com/puppy/viewtopic.php?t=95934sid=ca175185bed9514c33942f4795f29892 Here it was suggested that –rdynamic be added to the link options. This did not work for me. Which library should contain this symbol? -Original Message- From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of i3-discuss-requ...@i3.zekjur.net Sent: Tuesday, October 28, 2014 9:09 AM To: i3-discuss@i3.zekjur.net Subject: i3-discuss Digest, Vol 54, Issue 10 Send i3-discuss mailing list submissions to i3-discuss@i3.zekjur.netmailto:i3-discuss@i3.zekjur.net To subscribe or unsubscribe via the World Wide Web, visit http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss or, via email, send a message with subject or body 'help' to i3-discuss-requ...@i3.zekjur.netmailto:i3-discuss-requ...@i3.zekjur.net You can reach the person managing the list at i3-discuss-ow...@i3.zekjur.netmailto:i3-discuss-ow...@i3.zekjur.net When replying, please edit your Subject line so it is more specific than Re: Contents of i3-discuss digest... Today's Topics: 1. Struggling to build i3 4.8 on centos 6.5 - but almost there (Sargrad, Dave) 2. Re: Struggling to build i3 4.8 on centos 6.5 - but almost there (Johannes Lange) This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.
Re: [i3] Struggling to build i3 4.8 on centos 6.5 - but almost there
Well, 1] I do not pretend to understand this, but I “fixed” the link issue. Though my fix leaves me a tiny bit squeamish. I was able to get past the linker error with this modification to common.mk: LDFLAGS ?= $(as_needed_LDFLAG) -u xcb_str_sizeof Can someone please help me to understand what –u actually did? Is it a safe modification? I’ll note that inside /usr/lib64 is an older version of libxcb (1.8). It is there only because I needed to do the following (libX11-devel depends on libxcb): yum install libX11-devel My concern is to ensure that the newer versions of the libxcb stuff (that I compiled) overrides the old stuff found in /usr/lib64. 2] Other changes that I made to common.mk include: I3_CFLAGS = -std=c99 -I/usr/local/cwp/include LIBS = -L$(TOPDIR) -li3 -lm -L/usr/local/cwp/lib Is there an environment variable that I could have defined which would have prevented the need for these last two lines? 3] Last question relates to some of the libxcb elements that I did not seem to have to build. These include: xcb-proto, xcb-util-image, xcb-util-renderutil The fact that I did not have to build these seems odd. Should I have built them for completeness? I’ll also note two libraries that I had to build, which were not listed in DEPENDS: xcb-util-wm and xcb-util-keysyms. 4] As mentioned I will fully publish my procedures, once I scrub them. I will stand up a new box and go step by step through my procedures, at that point I will put them online. I’m about to try to give i3 a run now that it is built… fingers crossed. From: Sargrad, Dave Sent: Tuesday, October 28, 2014 10:07 AM To: i3-discuss@i3.zekjur.net Subject: RE: Struggling to build i3 4.8 on centos 6.5 - but almost there Johannes, Thanks again for helping me past that compile issue. I am now attempting to link. I got past a problem with a spurious -l by changing how I disabled pango. Apparently the proper way to disable pango is as follows (common.mk snippet): #PANGO_CFLAGS := $(call cflags_for_lib, cairo) #PANGO_CFLAGS += $(call cflags_for_lib, pangocairo) I3_CPPFLAGS += -DPANGO_SUPPORT=0 #PANGO_LIBS := $(call ldflags_for_lib, cairo) #PANGO_LIBS += $(call ldflags_for_lib, pangocairo) The link issue I am seeing is an undefined xcb symbol: [i3] Link i3 /usr/lib64/libxcb-render.so.0: undefined reference to `xcb_str_sizeof' collect2: ld returned 1 exit status make: *** [i3] Error 1 I found the following online: http://www.murga-linux.com/puppy/viewtopic.php?t=95934sid=ca175185bed9514c33942f4795f29892 Here it was suggested that –rdynamic be added to the link options. This did not work for me. Which library should contain this symbol? This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.
Re: [i3] i3-discuss Digest, Vol 54, Issue 11
I will certainly try that as well Sean. Thanks for pointing me to that. Now that I'm through the steps, and have documented them carefully, in some ways the source rpm will be a step back. However peeking into it may give me some clues relative to some of the questions I had. Thanks very much. -Original Message- From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of i3-discuss-requ...@i3.zekjur.net Sent: Tuesday, October 28, 2014 12:03 PM To: i3-discuss@i3.zekjur.net Subject: i3-discuss Digest, Vol 54, Issue 11 Send i3-discuss mailing list submissions to i3-discuss@i3.zekjur.net To subscribe or unsubscribe via the World Wide Web, visit http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss or, via email, send a message with subject or body 'help' to i3-discuss-requ...@i3.zekjur.net You can reach the person managing the list at i3-discuss-ow...@i3.zekjur.net When replying, please edit your Subject line so it is more specific than Re: Contents of i3-discuss digest... Today's Topics: 1. Re: Struggling to build i3 4.8 on centos 6.5 - but almost there (Sean Reifschneider) 2. Re: Struggling to build i3 4.8 on centos 6.5 - but almost there (Sargrad, Dave) 3. Re: Struggling to build i3 4.8 on centos 6.5 - but almost there (Johannes Lange) 4. Re: Struggling to build i3 4.8 on centos 6.5 - but almost there (Sargrad, Dave) -- Message: 1 Date: Tue, 28 Oct 2014 08:03:58 -0600 From: Sean Reifschneider j...@jafo.ca To: i3-discuss@i3.zekjur.net Subject: Re: [i3] Struggling to build i3 4.8 on centos 6.5 - but almost there Message-ID: 544fa24e.4040...@jafo.ca Content-Type: text/plain; charset=utf-8 On 10/28/14 06:46, Sargrad, Dave wrote: I am very close to building i3 4.8 on centos 6.5, and will post my procedures once I get them to be clean. I’ve successfully built i3 4.8 in the past on ubuntu 14.04, but am now moving to centos 6.5. Have you tried getting the Rawhide SRPM and building it? http://mirrors.tummy.com/pub/fedora.redhat.com/fedora/linux/development/rawhide/source/SRPMS/i/i3-4.8-5.fc22.src.rpm Then use rpmbuild --rebuild i3-4.8-5.fc22.src.rpm. That's what I did to get 4.8 built on my Ubuntu system, but back-porting the dpkg instead of the SRPM. Leverage the work other's have already done. Sean -- Message: 2 Date: Tue, 28 Oct 2014 14:07:19 + From: Sargrad, Dave dave.sarg...@saabsensis.com To: i3-discuss@i3.zekjur.net i3-discuss@i3.zekjur.net Subject: Re: [i3] Struggling to build i3 4.8 on centos 6.5 - but almost there Message-ID: 85ea6f68ac24da48b220ebea7a8c08b81b523...@corpmail01.corp.sensis.com Content-Type: text/plain; charset=utf-8 Johannes, Thanks again for helping me past that compile issue. I am now attempting to link. I got past a problem with a spurious -l by changing how I disabled pango. Apparently the proper way to disable pango is as follows (common.mk snippet): #PANGO_CFLAGS := $(call cflags_for_lib, cairo) #PANGO_CFLAGS += $(call cflags_for_lib, pangocairo) I3_CPPFLAGS += -DPANGO_SUPPORT=0 #PANGO_LIBS := $(call ldflags_for_lib, cairo) #PANGO_LIBS += $(call ldflags_for_lib, pangocairo) The link issue I am seeing is an undefined xcb symbol: [i3] Link i3 /usr/lib64/libxcb-render.so.0: undefined reference to `xcb_str_sizeof' collect2: ld returned 1 exit status make: *** [i3] Error 1 I found the following online: http://www.murga-linux.com/puppy/viewtopic.php?t=95934sid=ca175185bed9514c33942f4795f29892 Here it was suggested that –rdynamic be added to the link options. This did not work for me. Which library should contain this symbol? -Original Message- From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of i3-discuss-requ...@i3.zekjur.net Sent: Tuesday, October 28, 2014 9:09 AM To: i3-discuss@i3.zekjur.net Subject: i3-discuss Digest, Vol 54, Issue 10 Send i3-discuss mailing list submissions to i3-discuss@i3.zekjur.netmailto:i3-discuss@i3.zekjur.net To subscribe or unsubscribe via the World Wide Web, visit http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss or, via email, send a message with subject or body 'help' to i3-discuss-requ...@i3.zekjur.netmailto:i3-discuss-requ...@i3.zekjur.net You can reach the person managing the list at i3-discuss-ow...@i3.zekjur.netmailto:i3-discuss-ow...@i3.zekjur.net When replying, please edit your Subject line so it is more specific than Re: Contents of i3-discuss digest... Today's Topics: 1. Struggling to build i3 4.8 on centos 6.5 - but almost there (Sargrad, Dave) 2. Re: Struggling to build i3 4.8 on centos 6.5 - but almost there (Johannes Lange) This message is intended only for the addressee and may contain information that is company confidential
[i3] layout file causes i3 to hang
I've got a layout file that cause i3 (version 4.8) to hang 100% consistently.
I use the i3-msg append_layout command to cause this. I've used it with other
layout files just fine.
What is it about this file that causes i3 to hang?
I've included the layout file below:
{
border: normal,
floating: auto_off,
floating_nodes: [
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29940496
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29940864,
last_split_layout: splith,
layout: splith,
name: #aa,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 170,
x: 0,
y: 0
},
id: 29940496,
last_split_layout: splith,
layout: splith,
name: Toolbox - Tool Options,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 164,
x: 753,
y: 95
},
scratchpad_state: none,
swallows: [],
type: con,
urgent: false,
window: 37748871,
window_properties: {
class: Gimp,
instance: gimp,
title: Toolbox - Tool Options,
window_role: gimp-toolbox
},
window_rect: {
height: 820,
width: 160,
x: 2,
y: 0
},
workspace_layout: default
}
],
orientation: horizontal,
percent: null,
rect: {
height: 840,
width: 164,
x: 753,
y: 77
},
scratchpad_state: none,
swallows: [],
type: floating_con,
urgent: false,
window: null,
window_rect: {
height: 0,
width: 0,
x: 0,
y: 0
},
workspace_layout: default
},
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29637472
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29639104,
last_split_layout: splith,
layout: splith,
name: #ff,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 210,
x: 1679,
y: 0
},
id: 29637472,
last_split_layout: splith,
layout: splith,
name: Layers - Brushes,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 214,
x: 733,
y: 113
},
scratchpad_state: none,
swallows: [],
type: con,
urgent: false,
window: 37748887,
window_properties: {
class: Gimp,
instance: gimp,
title: Layers - Brushes,
Re: [i3] layout file causes i3 to hang
Looking more closely. Its clear that the floating_nodes portion of my layout
is incorrect. Will fix by converting window_properties to swallows.
-Original Message-
From: Sargrad, Dave
Sent: Monday, September 29, 2014 9:01 AM
To: i3-discuss@i3.zekjur.net
Subject: layout file causes i3 to hang
I've got a layout file that cause i3 (version 4.8) to hang 100% consistently.
I use the i3-msg append_layout command to cause this. I've used it with other
layout files just fine.
What is it about this file that causes i3 to hang?
I've included the layout file below:
{
border: normal,
floating: auto_off,
floating_nodes: [
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29940496
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29940864,
last_split_layout: splith,
layout: splith,
name: #aa,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 170,
x: 0,
y: 0
},
id: 29940496,
last_split_layout: splith,
layout: splith,
name: Toolbox - Tool Options,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 164,
x: 753,
y: 95
},
scratchpad_state: none,
swallows: [],
type: con,
urgent: false,
window: 37748871,
window_properties: {
class: Gimp,
instance: gimp,
title: Toolbox - Tool Options,
window_role: gimp-toolbox
},
window_rect: {
height: 820,
width: 160,
x: 2,
y: 0
},
workspace_layout: default
}
],
orientation: horizontal,
percent: null,
rect: {
height: 840,
width: 164,
x: 753,
y: 77
},
scratchpad_state: none,
swallows: [],
type: floating_con,
urgent: false,
window: null,
window_rect: {
height: 0,
width: 0,
x: 0,
y: 0
},
workspace_layout: default
},
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29637472
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29639104,
last_split_layout: splith,
layout: splith,
name: #ff,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 210,
x: 1679,
y: 0
},
id: 29637472,
last_split_layout: splith,
layout: splith,
name: Layers - Brushes,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 214,
x: 733,
y: 113
},
scratchpad_state: none,
swallows
[i3] i3 does not swallow title correctly
I3 swallows the following just fine
class: ^Firefox$
But it wont swallow title as follows (notice in this case I don’t use anchors
since I want to match any title containing YouTube):
title: YouTube
I run firefox as follows
firefox -no-remote http://youtube.com
I've done other experiments with the title swallow spec, but I don’t have any
luck getting i3 to swallow the title.
The complete swallows spec that I'm using is:
swallows: [
{title: YouTube}
],
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
Re: [i3] i3 does not swallow title correctly
WM_CLASS(STRING) = Navigator, Firefox
WM_ICON_NAME(STRING) = YouTube - Mozilla Firefox
_NET_WM_ICON_NAME(UTF8_STRING) = YouTube - Mozilla Firefox
WM_NAME(STRING) = YouTube - Mozilla Firefox
_NET_WM_NAME(UTF8_STRING) = YouTube - Mozilla Firefox
-Original Message-
From: Sargrad, Dave
Sent: Monday, September 29, 2014 2:24 PM
To: i3-discuss@i3.zekjur.net
Subject: i3 does not swallow title correctly
I3 swallows the following just fine
class: ^Firefox$
But it wont swallow title as follows (notice in this case I don’t use anchors
since I want to match any title containing YouTube):
title: YouTube
I run firefox as follows
firefox -no-remote http://youtube.com
I've done other experiments with the title swallow spec, but I don’t have any
luck getting i3 to swallow the title.
The complete swallows spec that I'm using is:
swallows: [
{title: YouTube}
],
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
Re: [i3] i3 swallows criteria
Hi Dave,
Heuristic number one: If you have an issue with i3, and flash is involved, it
is not an issue with i3. Can you show the problem with i3-sensible-terminal
(specify which)?
Also, judging from your email address and disclaimer, you are probably building
some multimonitor drone control high precision WMD kill interface. Just for
your information, i3 is really not suited for that. dwm is really more oriented
towards those type of purposes.
Cheers,
Joep
Joep,
Thanks for your response.
Relative to your thought about flash...
I am not using flash not sure how you came up with that. I am using i3 4.8
and trying to get it to swallow a firefox with a title spec. Having dug more, I
do think that this may be an issue with firefox (rather than i3). I've tried
the same with chromium-browser with greater success.
Relative to your second comment something about a WMD kill interface...
Huh?
-Original Message-
From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of
i3-discuss-requ...@i3.zekjur.net
Sent: Monday, September 29, 2014 3:44 PM
To: i3-discuss@i3.zekjur.net
Subject: i3-discuss Digest, Vol 53, Issue 17
Send i3-discuss mailing list submissions to
i3-discuss@i3.zekjur.net
To subscribe or unsubscribe via the World Wide Web, visit
http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss
or, via email, send a message with subject or body 'help' to
i3-discuss-requ...@i3.zekjur.net
You can reach the person managing the list at
i3-discuss-ow...@i3.zekjur.net
When replying, please edit your Subject line so it is more specific than Re:
Contents of i3-discuss digest...
Today's Topics:
1. i3 does not swallow title correctly (Sargrad, Dave)
2. Re: i3 does not swallow title correctly (Sargrad, Dave)
3. Re: i3 does not swallow title correctly (Joep van Delft)
--
Message: 1
Date: Mon, 29 Sep 2014 18:24:11 +
From: Sargrad, Dave dave.sarg...@saabsensis.com
To: i3-discuss@i3.zekjur.net i3-discuss@i3.zekjur.net
Subject: [i3] i3 does not swallow title correctly
Message-ID:
85ea6f68ac24da48b220ebea7a8c08b81b51a...@corpmail01.corp.sensis.com
Content-Type: text/plain; charset=utf-8
I3 swallows the following just fine
class: ^Firefox$
But it wont swallow title as follows (notice in this case I don’t use anchors
since I want to match any title containing YouTube):
title: YouTube
I run firefox as follows
firefox -no-remote http://youtube.com
I've done other experiments with the title swallow spec, but I don’t have any
luck getting i3 to swallow the title.
The complete swallows spec that I'm using is:
swallows: [
{title: YouTube}
],
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
--
Message: 2
Date: Mon, 29 Sep 2014 18:36:40 +
From: Sargrad, Dave dave.sarg...@saabsensis.com
To: i3-discuss@i3.zekjur.net i3-discuss@i3.zekjur.net
Subject: Re: [i3] i3 does not swallow title correctly
Message-ID:
85ea6f68ac24da48b220ebea7a8c08b81b51a...@corpmail01.corp.sensis.com
Content-Type: text/plain; charset=utf-8
Xprop shows the following for the window that is not getting swallowed
correctly:
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x27b
bitmap id # of mask for icon: 0x27c
window id # of group leader: 0x201
WM_WINDOW_ROLE(STRING) = browser
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
0x0, 0x10, 0x0, 0x0, 0x0
_NET_WM_ICON(CARDINAL) =Icon (16 x 16):
âââ
ââ
ââ
â
âââ â
âââ â
âââ â
ââ
âââ
ââ
ââ
Icon (32 x 32):
[i3] How to move workspace by name to a given named output
i3-msg move workspace 6 to output DVI-I-3 I am trying to move a named workspace to a named output. The command above does not seem to work. Rather it moves the current window to a new workspace with the name 6 to output DVI-I-3 How can I achieve this? - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -
[i3] Python save/append layout - toolbar auto-hide bug
I have written my own python script to append a workspace layout to a workspace. As part of this it also creates the workspace on the fly. The script will automatically append a layout to a named workspace and launch applications that will get swallowed by that workspace upon launch. It works fine, except for one small detail. Once the applications get swallowed everything looks fine. I see the applications in their proper layout and I see the toolbar that shows the workspaces (including the newly created one). However as soon as I move the cursor the toolbar disappears (the layout expands to cover it). If I kill the applications in that workspace then the toolbar becomes visible again. The layout file is generated by another python script that I created. It mimics i3-save-tree (except that it does not have the i3-save-tree bug that I mentioned previously). I'm sure that I'm doing something slightly wrong with the layout file creation. Yet as I said this mechanism is almost working perfectly. W What would cause the toolbar to auto-hide? - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -
Re: [i3] How to move workspace by name to a given named output
I've also tried this: i3-msg workspace 5 output DVI-I-3 The following section of the users guide says that should work. However this just creates a new workspace with the name 5 output DVI-I-3 4.13. Automatically starting applications on i3 startup http://i3wm.org/docs/userguide.html DISPLAY=:0.0 xrandr Screen 0: minimum 8 x 8, current 2960 x 1050, maximum 8192 x 8192 DVI-I-0 disconnected primary (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) DVI-I-2 connected 1680x1050+1280+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.0 60.0 800x60075.0 60.3 640x48075.0 59.9 DVI-I-3 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0*+ 75.0 1152x864 75.0 1024x768 75.0 60.0 800x60075.0 60.3 640x48075.0 59.9 -Original Message- From: Sargrad, Dave Sent: Monday, September 22, 2014 8:37 AM To: i3-discuss@i3.zekjur.net Subject: How to move workspace by name to a given named output i3-msg move workspace 6 to output DVI-I-3 I am trying to move a named workspace to a named output. The command above does not seem to work. Rather it moves the current window to a new workspace with the name 6 to output DVI-I-3 How can I achieve this? - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -
[i3] i3-save-tree questions continued
I almost have this working.
Can someone please explain to me what the following code snippet (drawn from
i3-save-tree) does:
for my $key (qw(nodes floating_nodes)) {
$tree-{$key} = [ map { strip_containers($_) } @{$tree-{$key}} ];
}
I think this is making a recursive call to strip_containers, for containers
that container either nodes or floating_nodes.
I don’t see the code that actually deletes empty nodes and empty
floating_nodes. Perhaps this code does that as well through the creation of a
new map that contains just the allowed_keys..
-Original Message-
From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of
i3-discuss-requ...@i3.zekjur.net
Sent: Tuesday, September 16, 2014 6:01 AM
To: i3-discuss@i3.zekjur.net
Subject: i3-discuss Digest, Vol 53, Issue 6
Send i3-discuss mailing list submissions to
i3-discuss@i3.zekjur.net
To subscribe or unsubscribe via the World Wide Web, visit
http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss
or, via email, send a message with subject or body 'help' to
i3-discuss-requ...@i3.zekjur.net
You can reach the person managing the list at
i3-discuss-ow...@i3.zekjur.net
When replying, please edit your Subject line so it is more specific than Re:
Contents of i3-discuss digest...
Today's Topics:
1. Re: i3-discuss Digest, Vol 53, Issue 5 (Sargrad, Dave)
--
Message: 1
Date: Mon, 15 Sep 2014 18:50:01 +
From: Sargrad, Dave dave.sarg...@saabsensis.com
To: i3-discuss@i3.zekjur.net i3-discuss@i3.zekjur.net
Subject: Re: [i3] i3-discuss Digest, Vol 53, Issue 5
Message-ID:
85ea6f68ac24da48b220ebea7a8c08b81b506...@corpmail01.corp.sensis.com
Content-Type: text/plain; charset=utf-8
Ok. I have made even further headway with this. Let me summarize what I think I
have learned:
1] By removing the window_properties from the spec I was able to get the
swallows to work properly 2] By only including the leaf nodes I was able to
append, rather than overlay.
So it would seem that i3 has the ability to not only append a layout but to
overlay a layout (onto an existing workspace). This almost seems like a
feature. Though I am not sure what unintended consequences there might be.
The latter can be seen in two examples:
The following spec does an append:
{
window_properties: {title: mo},
fullscreen_mode: 0,
floating: auto_off,
border: normal,
layout: splith,
percent: 0.5,
nodes: [],
type: con,
swallows: [
{
class: ^XTerm$
}
],
name: one,
geometry: {y: 0, x: 0, height: 316, width: 484} }
{
fullscreen_mode: 0,
floating: auto_off,
border: normal,
layout: splith,
percent: 0.5,
nodes: [],
type: con,
swallows: [
{
class: ^XTerm$
}
],
name: two,
geometry: {y: 0, x: 0, height: 316, width: 484} }
Whereas by keeping the parent workspace we end up with an overlay:
{
fullscreen_mode: 1,
floating: auto_off,
border: normal,
layout: splith,
percent: null,
nodes: [
{
fullscreen_mode: 0,
floating: auto_off,
border: normal,
layout: splith,
percent: 0.5,
nodes: [],
type: con,
swallows: [{class: ^XTerm$}],
name: one,
geometry: {y: 0, x: 0, height: 316, width: 484}},
{
fullscreen_mode: 0,
floating: auto_off,
border: normal,
layout: splith,
percent: 0.5,
nodes: [],
type: con,
swallows: [{class: ^XTerm$}],
name: two,
geometry: {y: 0, x: 0, height: 316, width: 484}}
],
type: workspace,
swallows: []
}
-Original Message-
From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of
i3-discuss-requ...@i3.zekjur.net
Sent: Monday, September 15, 2014 1:41 PM
To: i3-discuss@i3.zekjur.net
Subject: i3-discuss Digest, Vol 53, Issue 5
Send i3-discuss mailing list submissions to
i3-discuss@i3.zekjur.net
To subscribe or unsubscribe via the World Wide Web, visit
http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss
or, via email, send a message with subject or body 'help' to
i3-discuss-requ...@i3.zekjur.net
You can reach the person managing the list at
i3-discuss-ow...@i3.zekjur.net
When replying, please edit your Subject line so it is more specific than Re:
Contents of i3-discuss digest...
Today's Topics:
1. i3 layout save/restore (Sargrad, Dave)
2. Re: i3 layout save/restore (Sargrad, Dave)
--
Message: 1
Date: Mon, 15 Sep 2014 16:33:04 +
From: Sargrad, Dave dave.sarg...@saabsensis.com
To: i3
[i3] i3 save/restore bug
I've found a bug with the i3 save/restore mechanism
In general the save/load works fine (I've tried a number of layouts that work
fine), however I have found a simple configuration that fails to save/load
correctly. I'm not sure yet if this is a problem with i3, or with i3-save-tree.
I opened three windows in a workspace (and then saved using i3-save-tree
--workspace test /home/ubuntu/.i3/spec)
2 xterms side-by-side in top row
1 emacs in bottom row (I used the mod-shift-k to move emacs down)
Correct Layout (the layout I saved with i3-save-tree)
_
|| |
|| |
|| |
| xterm | xterm |
|| |
|| |
|| |
|| |
-
||
||
||
| emacs |
||
||
||
||
_
I then appended using i3-msg (i3-msg workspace new; append_layout
/home/ubuntu/.i3/spec
After Append Layout (Incorrect Result)
_
|| | |
|| | |
|| | |
| xterm | xterm | emacs |
|| | |
|| | |
|| | |
|| | |
|| | |
|| | |
|| | |
_
This is the spec generated by i3-save-tree:
// vim:ts=4:sw=4:et
{
// splith split container with 2 children
border: normal,
floating: auto_off,
layout: splith,
percent: 0.232604373757455,
type: con,
nodes: [
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 484,
x: 0,
y: 0
},
name: ubuntu@sensis-8930: ~,
percent: 0.5,
swallows: [
{
class: ^XTerm$
}
],
type: con
},
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 484,
x: 0,
y: 0
},
name: ubuntu@sensis-8930: ~,
percent: 0.5,
swallows: [
{
class: ^XTerm$
}
],
type: con
}
]
}
{
border: normal,
floating: auto_off,
geometry: {
height: 550,
width: 602,
x: 0,
y: 0
},
name: em...@example.com,
percent: 0.767395626242545,
swallows: [
{
class: ^Emacs23$
}
],
type: con
}
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
[i3] i3 layout save/restore
I am trying to generate my own layout files in python (similar to the files
generated by i3-save-tree). I am looking for something that describes the
layout specification [above and beyond the i3-save-tree code, which is a bit
cryptic for a non-perl expert].
I am already able to get the i3 tree in python. Furthermore I already have a
number of operations that I perform on that tree. For example I have an
operation that generates an image (representing the workspace structure) for
each workspace in the tree. I am at a point where I need to generate layout
specs, so that I can subsequently append these to workspaces.
The first couple of specs that I generated are essentially just a dump of the
portion of the portion of the tree that corresponds to the workspace. I know
these need to be tweaked further. For example I have not yet added swallows,
nor stripped non-necessary elements (like fullscreen_mode or layout).
However I thought that i3 would allow me to load these specs and then I could
begin to trim them and modify them until they looked more like the specs
generated by i3-save-tree. Indeed I hoped that i3 might provide feedback
relative to the elements of the spec that were not right.
The unfortunate thing is that i3 crashes when it attempts to load my specs. So
rather than move from the form that I have incrementally towards the right
form, I need to jump to the right form more quickly.
A specification for the layout structure would help. Is there anything that
exists above and beyond the perl code, and the samples of generated layouts
that I can create with it?
For example, here is the portion of the tree that corresponds to the workspace
that I am trying to save a spec for: this particular simple workspace is one
window on top of another. Other than the obvious things like adding a proper
swallows element, what are the key things that I need to keep in mind when
transforming portions of the i3 tree into a form that can later be appended?
{fullscreen_mode: 1, orientation: horizontal, focus: [2316,
23125184], urgent: false, num: 1, last_split_layout: splith,
floating: auto_off, border: normal, id: 23119648,
current_border_width: -1, layout: splith, percent: null,
workspace_layout: default, window: null, nodes: [{window_properties:
{instance: xterm, class: XTerm, title: ubuntu@example-8930:
~/playground/cwpmash}, fullscreen_mode: 0, orientation: none, focus:
[], urgent: false, last_split_layout: splith, floating: auto_off,
border: normal, id: 23125184, current_border_width: -1, layout:
splith, percent: 0.5, workspace_layout: default, window: 25165860,
nodes: [], type: con, swallows: [], focused: false,
scratchpad_state: none, rect: {y: 18, x: 0, height: 1013, width:
840}, window_rect: {y: 0, x: 2, height: 1009, width: 834}, name:
ubuntu@example-8930: ~/playground/cwpmash, geometry: {y: 0, x: 0,
height: 316, width: 484}, floating_nodes: []}, {window_properties:
{instance: xterm, class: XTerm, title: ubuntu@example-8930: ~},
fullscreen_mode: 0, orientation: none, focus: [], urgent: false,
last_split_layout: splith, floating: auto_off, border: normal,
id: 2316, current_border_width: -1, layout: splith, percent: 0.5,
workspace_layout: default, window: 27263012, nodes: [], type: con,
swallows: [], focused: true, scratchpad_state: none, rect: {y: 18,
x: 840, height: 1013, width: 840}, window_rect: {y: 0, x: 2,
height: 1009, width: 834}, name: ubuntu@example-8930: ~, geometry:
{y: 0, x: 0, height: 316, width: 484}, floating_nodes: []}], type:
workspace, swallows: [], focused: false, scratchpad_state: none,
rect: {y: 0, x: 0, height: 1031, width: 1680}, window_rect: {y:
0, x: 0, height: 0, width: 0}, name: 1, geometry: {y: 0, x: 0,
height: 0, width: 0}, floating_nodes: []}
The correct form (as generated by i3-save-tree) is:
// vim:ts=4:sw=4:et
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 484,
x: 0,
y: 0
},
name: ubuntu@example-8930: ~/playground/cwpmash,
percent: 0.5,
swallows: [
{
// class: ^XTerm$,
// instance: ^xterm$,
// title: ^ubuntu\\@example\\-8930\\:\\ \\~\\/playground\\/cwpmash$
}
],
type: con
}
{
border: normal,
floating: auto_off,
geometry: {
height: 316,
width: 484,
x: 0,
y: 0
},
name: ubuntu@example-8930: ~,
percent: 0.5,
swallows: [
{
// class: ^XTerm$,
// instance: ^xterm$,
// title: ^ubuntu\\@example\\-8930\\:\\ \\~$
}
],
type: con
}
http://i3wm.org/docs/layout-saving.html#_saving_the_layout
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
Re: [i3] i3 layout save/restore
I've made a little progress with this generation of a json layout spec. Note
that I am trying to be completely json compliant. So, unlike the i3-save-tree
(which saves multiple json documents), I have a json spec that only has one
json document. My reading of the i3 documentation seems to suggest that i3 has
no problem with this, and it seems that it doesn't have a problem.
In the sample that I provided below I have reduced the spec to the following
form:
{fullscreen_mode: 1, floating: auto_off, border: normal, layout:
splith, percent: null, nodes: [{window_properties: {title: yo},
fullscreen_mode: 0, floating: auto_off, border: normal, layout:
splith, percent: 0.5, nodes: [], type: con, swallows: [{class:
^XTerm$}], name: ubuntu@example-8930: ~, geometry: {y: 0, x: 0,
height: 316, width: 484}}, {window_properties: {title: go},
fullscreen_mode: 0, floating: auto_off, border: normal, layout:
splith, percent: 0.5, nodes: [], type: con, swallows: [{class:
^XTerm$}], name: ubuntu@example-8930: ~, geometry: {y: 0, x: 0,
height: 316, width: 484}}], type: workspace, swallows: []}
Notice that this spec actually has 3 swallows one for the parent workspace and
two for the 2 xterm leaf nodes. Not sure why this is, but it is what I received
when I requested the tree. I3-save-tree (I think) only shows a swallows for
leaf nodes.
I can actually append this document to a workspace (i3-msg workspace 2;
append_layout /home/ubuntu/.i3/layout_spec) - i3 does not crash on this spec.
However I see two problems:
1] The spec actually overlays the workspace (rather than appending to it)
2] The windows do not swallow a subsequent xterm.
Why does this spec result in an overlay rather than an append? Why is my
swallow not working?
From: Sargrad, Dave
Sent: Monday, September 15, 2014 12:33 PM
To: 'i3-discuss@i3.zekjur.net'
Subject: i3 layout save/restore
I am trying to generate my own layout files in python (similar to the files
generated by i3-save-tree). I am looking for something that describes the
layout specification [above and beyond the i3-save-tree code, which is a bit
cryptic for a non-perl expert].
I am already able to get the i3 tree in python. Furthermore I already have a
number of operations that I perform on that tree. For example I have an
operation that generates an image (representing the workspace structure) for
each workspace in the tree. I am at a point where I need to generate layout
specs, so that I can subsequently append these to workspaces.
The first couple of specs that I generated are essentially just a dump of the
portion of the portion of the tree that corresponds to the workspace. I know
these need to be tweaked further. For example I have not yet added swallows,
nor stripped non-necessary elements (like fullscreen_mode or layout).
However I thought that i3 would allow me to load these specs and then I could
begin to trim them and modify them until they looked more like the specs
generated by i3-save-tree. Indeed I hoped that i3 might provide feedback
relative to the elements of the spec that were not right.
The unfortunate thing is that i3 crashes when it attempts to load my specs. So
rather than move from the form that I have incrementally towards the right
form, I need to jump to the right form more quickly.
A specification for the layout structure would help. Is there anything that
exists above and beyond the perl code, and the samples of generated layouts
that I can create with it?
For example, here is the portion of the tree that corresponds to the workspace
that I am trying to save a spec for: this particular simple workspace is one
window on top of another. Other than the obvious things like adding a proper
swallows element, what are the key things that I need to keep in mind when
transforming portions of the i3 tree into a form that can later be appended?
{fullscreen_mode: 1, orientation: horizontal, focus: [2316,
23125184], urgent: false, num: 1, last_split_layout: splith,
floating: auto_off, border: normal, id: 23119648,
current_border_width: -1, layout: splith, percent: null,
workspace_layout: default, window: null, nodes: [{window_properties:
{instance: xterm, class: XTerm, title: ubuntu@example-8930:
~/playground/cwpmash}, fullscreen_mode: 0, orientation: none, focus:
[], urgent: false, last_split_layout: splith, floating: auto_off,
border: normal, id: 23125184, current_border_width: -1, layout:
splith, percent: 0.5, workspace_layout: default, window: 25165860,
nodes: [], type: con, swallows: [], focused: false,
scratchpad_state: none, rect: {y: 18, x: 0, height: 1013, width:
840}, window_rect: {y: 0, x: 2, height: 1009, width: 834}, name:
ubuntu@example-8930: ~/playground/cwpmash, geometry: {y: 0, x: 0,
height: 316, width: 484}, floating_nodes: []}, {window_properties:
{instance: xterm, class: XTerm, title: ubuntu@example-8930: ~},
fullscreen_mode: 0, orientation: none, focus: [], urgent: false
[i3] i3 tree public or private
I am building some automation to be used with i3, with an eye towards remote management of a suite of i3 desktops. I am using the latest i3 (4.8). I need to make the design decision to use high level tools such as i3-save-tree, or to build my own tree parsing/manipulation tools. I would like to understand how stable the tree structure is. If its relatively stable, then I think its pretty safe to build my own tools that work with the i3 tree. Future changes to the tree would be something that I can work with in this case. However if the tree is expected to change a lot then perhaps I don’t want to build my own tools that work with the tree structure. In a sense I am wondering if I should treat the tree structure (and specification) as a public or a private spec. Certainly for a given i3 release I can treat it as public, but I don’t want to create automation that will become obsolete with future releases of i3. Id appreciate any thoughts or recommendations. - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -
[i3] i3-msg focus parent - odd error
Michael,
Thank you for the suggestion relative to using focus parent
As you see in the following output, I certainly can focus parent (to an
extent), yet after a couple calls to focus parent I see an odd error.
Furthermore this error does not always occur when I have arrived at the
workspace level. I could be at a parent container that is within the workspace.
ubuntu@example:~$ DISPLAY=:0.0 i3-msg focus parent
[{success:true}]
ubuntu@example:~$ DISPLAY=:0.0 i3-msg focus parent
ERROR: Your command: (null)
ERROR: (null)
ERROR: (null)
[{success:false}]
I'm trying to figure out when I arrive at the workspace level. Keep in mind
that I am running this script without actually having the visual feedback of
the desktop to tell me that I am at the workspace level.
It would be much easier if I could focus the workspace by name (this does not
seem to be an option):
i3-msg focus workspace 2
What is the proper way for me to script focus the parent till you arrive at a
containing workspace?
Thanks.
-
Message: 4
Date: Mon, 8 Sep 2014 19:44:09 +0200
From: Michael Stapelberg mich...@i3wm.org
To: Discussions/Questions about the i3 window manager
i3-discuss@i3.zekjur.net
Subject: Re: [i3] using i3-msg to close entire workspace
Message-ID:
CANnVG6kSyfSgmoXK3LFpv6YO9K1DSvu51HyHv9QA=dfkrb9...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
On Mon, Sep 8, 2014 at 6:11 PM, Sargrad, Dave dave.sarg...@saabsensis.com
wrote:
I am looking for a way to use i3-msg to close an entire workspace.
Use “focus parent” until you arrive at the workspace level, then use “kill”.
So far I've not found the way to do this. Can someone please let me know if
this is easy to do.
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this
message may be exported only in accordance with the U.S. International
Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export
Administration Regulations (15 CFR Parts 730-774). Unauthorized use is
strictly prohibited and may be unlawful. If you are not the intended
recipient, or the person responsible for delivering to the intended
recipient, you should not read, copy, disclose or otherwise use this message.
If you have received this email in error, please delete it, and advise the
sender immediately.
-
--
Best regards,
Michael
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
Re: [i3] i3-msg focus parent - odd error
Actually with further experimentation, I think that the funny error always
occurs when I have arrived at a containing workspace.
Assuming that this is true, then it should then be easy for me to simply check
for the first failure to focus a parent.
Is there a way to query i3 for the currently focused object? If so then that
would be a further check that I can make to ensure that the object with focus
is of type workspace.
-Original Message-
From: Sargrad, Dave
Sent: Tuesday, September 09, 2014 3:58 PM
To: i3-discuss@i3.zekjur.net
Subject: i3-msg focus parent - odd error
Michael,
Thank you for the suggestion relative to using focus parent
As you see in the following output, I certainly can focus parent (to an
extent), yet after a couple calls to focus parent I see an odd error.
Furthermore this error does not always occur when I have arrived at the
workspace level. I could be at a parent container that is within the workspace.
ubuntu@example:~$ DISPLAY=:0.0 i3-msg focus parent [{success:true}]
ubuntu@example:~$ DISPLAY=:0.0 i3-msg focus parent
ERROR: Your command: (null)
ERROR: (null)
ERROR: (null)
[{success:false}]
I'm trying to figure out when I arrive at the workspace level. Keep in mind
that I am running this script without actually having the visual feedback of
the desktop to tell me that I am at the workspace level.
It would be much easier if I could focus the workspace by name (this does not
seem to be an option):
i3-msg focus workspace 2
What is the proper way for me to script focus the parent till you arrive at a
containing workspace?
Thanks.
-
Message: 4
Date: Mon, 8 Sep 2014 19:44:09 +0200
From: Michael Stapelberg mich...@i3wm.org
To: Discussions/Questions about the i3 window manager
i3-discuss@i3.zekjur.net
Subject: Re: [i3] using i3-msg to close entire workspace
Message-ID:
CANnVG6kSyfSgmoXK3LFpv6YO9K1DSvu51HyHv9QA=dfkrb9...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
On Mon, Sep 8, 2014 at 6:11 PM, Sargrad, Dave dave.sarg...@saabsensis.com
wrote:
I am looking for a way to use i3-msg to close an entire workspace.
Use “focus parent” until you arrive at the workspace level, then use “kill”.
So far I've not found the way to do this. Can someone please let me know if
this is easy to do.
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this
message may be exported only in accordance with the U.S. International
Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export
Administration Regulations (15 CFR Parts 730-774). Unauthorized use is
strictly prohibited and may be unlawful. If you are not the intended
recipient, or the person responsible for delivering to the intended
recipient, you should not read, copy, disclose or otherwise use this message.
If you have received this email in error, please delete it, and advise the
sender immediately.
-
--
Best regards,
Michael
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
Re: [i3] using i3-msg to close entire workspace
I am looking for a way to use i3-msg to close an entire workspace. So far I've not found the way to do this. Can someone please let me know if this is easy to do. - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. -
[i3] Confusing error message
I think the following should kill all windows having class Emacs23. The error
message is very confusing:
ubuntu@example:~/.i3$ DISPLAY=:0.0 i3-msg [class=Emacs23] kill
ERROR: Your command: a kill
ERROR: ^^
ERROR: Expected one of these tokens: end, '[', 'move', 'exec', 'exit',
'restart', 'reload', 'shmlog', 'debuglog', 'border', 'layout', 'append_layout',
'workspace', 'focus', 'kill', 'open', 'fullscreen', 'split', 'floating',
'mark', 'unmark', 'resize', 'rename', 'nop', 'scratchpad', 'mode', 'bar'
[{success:false,parse_error:true,error:Expected one of these tokens:
end, '[', 'move', 'exec', 'exit', 'restart', 'reload', 'shmlog', 'debuglog',
'border', 'layout', 'append_layout', 'workspace', 'focus', 'kill', 'open',
'fullscreen', 'split', 'floating', 'mark', 'unmark', 'resize', 'rename', 'nop',
'scratchpad', 'mode', 'bar',input:a kill,errorposition:^^}]
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
[i3] Cant subscribe to window::focus events
I am trying to register for a window::focus event, but am not seeing the events
come in.
I can register for window::new and for workspace::focus just fine.
The code snippet I am using to register is:
from gi.repository import i3ipc
# Create the Connection object that can be used to send commands and subscribe
# to events.
conn = i3ipc.Connection()
conn.on('window::focus', on_window_focus)
I did turn on i3 debug and I did notice the following (this occurs when I call
conn.on):
08/29/2014 04:53:25 PM - ipc.c:add_subscription:744 - should add subscription
to extra 0xef61a0, sub window
08/29/2014 04:53:25 PM - ipc.c:add_subscription:754 - client is now subscribed
to:
08/29/2014 04:53:25 PM - ipc.c:add_subscription:756 - event window
08/29/2014 04:53:25 PM - ipc.c:add_subscription:757 - (done)
Not sure how to interpret that debug info, but I think its telling me that I
need to subscribe for window::focus differently.
Again, I am able to register for workspace::focus just fine (and receive
workspace focus events).
conn.on('workspace::focus', on_workspace_focus)
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
