The weird error message is a bug, so please report it as such at
http://bugs.i3wm.org/

The layout tree contains “focused” properties, and you can also
manually look at the “focus” array to determine which container is
focused.

On Tue, Sep 9, 2014 at 10:06 PM, Sargrad, Dave
<dave.sarg...@saabsensis.com> wrote:
> 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.
> -



-- 
Best regards,
Michael

Reply via email to