Re: [i3] Reloading i3wm and saving layout

2015-07-24 Thread Eric Duncan
Finally had time to sit down and do this.

@Michael: I opened an issue on Github:

https://github.com/i3/i3/issues/1810

And I made a comment of what I propose the fix to be: have the mkdir()
function ignore if the directory already exists.



On Sat, Jul 4, 2015 at 2:01 PM, Michael Stapelberg  wrote:

> To me, this sounds like a bug, but I’m not yet sure where precisely it is
> :).
>
> Eric, can you please file an issue at https://github.com/i3/i3? When you
> file it, please include the version of i3 as well as a logfile (as the
> instructions ask you to). In addition, can you please include the output of
> “ls -lR /run” and “mount”?
>
> Thanks.
>
> On Sat, Jul 4, 2015 at 6:59 PM, Karol Langner 
> wrote:
>
>> Just wanted to mention that I remember having the same thing on Debian
>> wheezy, although I did not look at the logs and it went away when I moved
>> to Ubuntu 12/14. I also did revamp my config at the same, so it could have
>> been related to that.
>>
>> On Sat, Jul 4, 2015 at 8:28 AM, Eric Duncan  wrote:
>>
>>> i3 version 4.10.2 (2015-04-16, branch "4.10.2")
>>>
>>> Though it doesn't matter - been like this ever since I started using
>>> i3wm on Debian (6, 7, and Testing), Ubuntu (14.04, 14.10, 15.04) and Arch
>>> for over a year.
>>>
>>> Maybe I am missing a configuration parameter...
>>>
>>> On Sat, Jul 4, 2015 at 6:19 AM, Michael Stapelberg 
>>> wrote:
>>>
>>>> Which version of i3 are you using?
>>>>
>>>> On Sat, Jul 4, 2015 at 6:34 AM, Eric Duncan 
>>>> wrote:
>>>>
>>>>> So, been using i3wm for a bit over a year across multiple distros
>>>>> (Debian6, 7 and Testing; Ubuntu 14.04, 14.10 and 15.04; now Arch).
>>>>>
>>>>> When pressing MOD+R to reload i3wm, it's always annoyed me that it
>>>>> doesn't keep my terminal layouts (usually stacks them on the screen I am
>>>>> on).
>>>>>
>>>>> Today while monitoring journalctl, I noticed some interesting logs:
>>>>>
>>>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015
>>>>> 12:27:30 AM - ERROR: mkdir(/run/user/1000/i3) failed: File exists
>>>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
>>>>> libi3/font.c Using Pango font Segoe UI, size 10
>>>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
>>>>> libi3/font.c X11 root window dictates 96.252632 DPI
>>>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: Exiting due to
>>>>> signal.
>>>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015
>>>>> 12:27:30 AM - ERROR: Could not create "/run/user/1000/i3" for storing the
>>>>> restart layout, layout will be lost.
>>>>>
>>>>> It says that this file exists:
>>>>>
>>>>> /run/user/1000/i3
>>>>>
>>>>> And indeed this directory does.
>>>>>
>>>>> Could this be the bane of my annoyances?
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Michael
>>>>
>>>
>>>
>>
>
>
> --
> Best regards,
> Michael
>


Re: [i3] Reloading i3wm and saving layout

2015-07-04 Thread Eric Duncan
i3 version 4.10.2 (2015-04-16, branch "4.10.2")

Though it doesn't matter - been like this ever since I started using i3wm
on Debian (6, 7, and Testing), Ubuntu (14.04, 14.10, 15.04) and Arch for
over a year.

Maybe I am missing a configuration parameter...

On Sat, Jul 4, 2015 at 6:19 AM, Michael Stapelberg  wrote:

> Which version of i3 are you using?
>
> On Sat, Jul 4, 2015 at 6:34 AM, Eric Duncan  wrote:
>
>> So, been using i3wm for a bit over a year across multiple distros
>> (Debian6, 7 and Testing; Ubuntu 14.04, 14.10 and 15.04; now Arch).
>>
>> When pressing MOD+R to reload i3wm, it's always annoyed me that it
>> doesn't keep my terminal layouts (usually stacks them on the screen I am
>> on).
>>
>> Today while monitoring journalctl, I noticed some interesting logs:
>>
>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015
>> 12:27:30 AM - ERROR: mkdir(/run/user/1000/i3) failed: File exists
>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
>> libi3/font.c Using Pango font Segoe UI, size 10
>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
>> libi3/font.c X11 root window dictates 96.252632 DPI
>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: Exiting due to
>> signal.
>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015
>> 12:27:30 AM - ERROR: Could not create "/run/user/1000/i3" for storing the
>> restart layout, layout will be lost.
>>
>> It says that this file exists:
>>
>> /run/user/1000/i3
>>
>> And indeed this directory does.
>>
>> Could this be the bane of my annoyances?
>>
>>
>>
>
>
> --
> Best regards,
> Michael
>


[i3] Reloading i3wm and saving layout

2015-07-03 Thread Eric Duncan
So, been using i3wm for a bit over a year across multiple distros (Debian6,
7 and Testing; Ubuntu 14.04, 14.10 and 15.04; now Arch).

When pressing MOD+R to reload i3wm, it's always annoyed me that it doesn't
keep my terminal layouts (usually stacks them on the screen I am on).

Today while monitoring journalctl, I noticed some interesting logs:

Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015 12:27:30
AM - ERROR: mkdir(/run/user/1000/i3) failed: File exists
Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
libi3/font.c Using Pango font Segoe UI, size 10
Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
libi3/font.c X11 root window dictates 96.252632 DPI
Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: Exiting due to
signal.
Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015 12:27:30
AM - ERROR: Could not create "/run/user/1000/i3" for storing the restart
layout, layout will be lost.

It says that this file exists:

/run/user/1000/i3

And indeed this directory does.

Could this be the bane of my annoyances?


Re: [i3] gnome-settings-daemon not working

2015-05-23 Thread Eric Duncan
Thanks.  This did it:

exec_always --no-startup-id xset r rate 200 40

Though I wonder why the gnome-settings-daemon is not setting it, like it
always has for other distros (again, this is Arch).

Btw, dconf is only a setting.  You don't need to execute it on every
login.  Just run it in the shell once, and it sticks:

$ dconf write /org/gnome/settings-daemon/plugins/cursor/active false

And this led me down another path with Awesome, setting the OnlyShowIn to
include i3:

https://awesome.naquadah.org/wiki/Quickly_Setting_up_Awesome_with_Gnome

But that didn't seem to change anything.

Last, I also changed my paths to use the 64bit versions of the daemons:

# exec once in Arch Linux
exec --no-startup-id /usr/bin/vmware-user-suid-wrapper
exec --no-startup-id /usr/lib64/gnome-settings-daemon/gnome-settings-daemon
&
exec --no-startup-id
/usr/lib64/gnome-settings-daemon/gnome-settings-daemon-localeexec &
#exec --no-startup-id /usr/bin/gnome-keyring-daemon --start
--components=pkcs11,secrets,ssh,gpg #
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1

Still didn't change anything...

You'll note that I am not starting the gnome-keyring-daemon.  I am actually
using the gnome-keyring-daemon, and I've completely disabled ssh-agent from
managing my keys.  GDM starts the gnome-keyring-daemon for me on login,
under my username.  I found this was different than all other distros.

Maybe it's the latest versions of GDM and Gnome that is changing, as
running under Arch you get the latest and greatest.

Thanks!





On Sat, May 23, 2015 at 8:18 PM, Martin Cigorraga  wrote:

> I forgot to mention this:
> exec --no-startup-id /usr/libexec/gnome-settings-daemon-localeexec
> exec --no-startup-id dconf write
> /org/gnome/settings-daemon/plugins/cursor/active false   # Fix a bug
> in gnome-settings-daemon:
> http://feeding.cloud.geek.nz/posts/creating-a-modern-tiling-desktop-environment-using-i3/
>
> -M.
>
> On Sat, May 23, 2015 at 6:39 PM, Martin Cigorraga <
> martincigorr...@gmail.com> wrote:
>
>> Hey Eric,
>>
>> You could use xset until you figure out what's happening there:
>> $ xset r rate 200 40
>>
>> If you also want to specify a kbd layout:
>> $ setxkbmap -rules evdev -model evdev -layout us -variant altgr-intl
>>
>> HTH.
>> -Martín
>>
>> On Sat, May 23, 2015 at 5:31 PM, Eric Duncan 
>> wrote:
>>
>>> i3 version 4.10.2 (2015-04-16, branch "4.10.2") © 2009-2014 Michael
>>> Stapelberg and contributors
>>>
>>> I recently switched to Arch and I'm bringing over my i3 dot files, etc.
>>>
>>> Got a problem... I can't see to get my Gnome 3.16 settings working in
>>> i3wm.  I haven't had a problem with my Debian (7 and Jessie Testing) and
>>> Ubuntu (14.04 and 14.10) installs in the past.  But I've installed Arch on
>>> two different machines, and on both I cannot get the gnome-settings-daemon
>>> (or at least that's what I think it is) to enable my Gnome settings.
>>>
>>> Specifically, I can't get my Gnome setting for Keyboard short delay and
>>> faster repeat enabled.  I have not tried any other settings.
>>>
>>> If it matters, I am running within VMware Workstation and Fusion.
>>>
>>> My config looks like:
>>>
>>> exec --no-startup-id /usr/bin/vmware-user-suid-wrapper
>>> #exec --no-startup-id
>>> /usr/lib/gnome-settings-daemon/gnome-settings-daemon
>>> #exec --no-startup-id /usr/bin/gnome-keyring-daemon --start
>>> --components=pkcs11,secrets,ssh,gpg #
>>> /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
>>> #exec --no-startup-id dropbox start
>>> exec --no-startup-id compton -Cb --config ~/.i3/compton.conf # -CGb
>>>
>>> So when logged in, I see:
>>>
>>> $ ps aux | grep gnome-settings
>>> gdm 897  0.0  0.3 820888 29796 tty1 Sl+  16:24   0:00
>>> /usr/lib/gnome-settings-daemon/gnome-settings-daemon
>>>
>>> If I uncomment the gnome-settings-daemon one, it starts under my
>>> username and loads a few other gnome services:
>>>
>>> $ ps aux | grep gnome-settings
>>> gdm 897  0.0  0.3 820888 29796 tty1 Sl+  16:24   0:00
>>> /usr/lib/gnome-settings-daemon/gnome-settings-daemon
>>> eric   1049  0.0  0.6 915224 51304 ?Sl   16:24   0:00
>>> /usr/lib/gnome-settings-daemon/gnome-settings-daemon
>>> eric   1112  0.0  0.2 283984 18924 ?Sl   16:24   0:00
>>> /usr/lib/gnome-settings-daemon/gsd-locate-pointer
>>> eric   1114  0.0  0.1 433304 11408 ?Sl   16:24   0:00
>>> /usr/lib/gnome-settings-daemon/gsd-printer
>>>
>>> Sounds good, except no keyboard settings have taken effect.
>>>
>>> Thoughts?
>>>
>>> Thanks!
>>> Eric
>>>
>>>
>>
>


[i3] gnome-settings-daemon not working

2015-05-23 Thread Eric Duncan
i3 version 4.10.2 (2015-04-16, branch "4.10.2") © 2009-2014 Michael
Stapelberg and contributors

I recently switched to Arch and I'm bringing over my i3 dot files, etc.

Got a problem... I can't see to get my Gnome 3.16 settings working in
i3wm.  I haven't had a problem with my Debian (7 and Jessie Testing) and
Ubuntu (14.04 and 14.10) installs in the past.  But I've installed Arch on
two different machines, and on both I cannot get the gnome-settings-daemon
(or at least that's what I think it is) to enable my Gnome settings.

Specifically, I can't get my Gnome setting for Keyboard short delay and
faster repeat enabled.  I have not tried any other settings.

If it matters, I am running within VMware Workstation and Fusion.

My config looks like:

exec --no-startup-id /usr/bin/vmware-user-suid-wrapper
#exec --no-startup-id /usr/lib/gnome-settings-daemon/gnome-settings-daemon
#exec --no-startup-id /usr/bin/gnome-keyring-daemon --start
--components=pkcs11,secrets,ssh,gpg #
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
#exec --no-startup-id dropbox start
exec --no-startup-id compton -Cb --config ~/.i3/compton.conf # -CGb

So when logged in, I see:

$ ps aux | grep gnome-settings
gdm 897  0.0  0.3 820888 29796 tty1 Sl+  16:24   0:00
/usr/lib/gnome-settings-daemon/gnome-settings-daemon

If I uncomment the gnome-settings-daemon one, it starts under my username
and loads a few other gnome services:

$ ps aux | grep gnome-settings
gdm 897  0.0  0.3 820888 29796 tty1 Sl+  16:24   0:00
/usr/lib/gnome-settings-daemon/gnome-settings-daemon
eric   1049  0.0  0.6 915224 51304 ?Sl   16:24   0:00
/usr/lib/gnome-settings-daemon/gnome-settings-daemon
eric   1112  0.0  0.2 283984 18924 ?Sl   16:24   0:00
/usr/lib/gnome-settings-daemon/gsd-locate-pointer
eric   1114  0.0  0.1 433304 11408 ?Sl   16:24   0:00
/usr/lib/gnome-settings-daemon/gsd-printer

Sounds good, except no keyboard settings have taken effect.

Thoughts?

Thanks!
Eric


Re: [i3] Assign workspaces to outputs dynamically.

2015-03-20 Thread Eric Duncan
I too use a laptop and move between 3 different environments with 3
different monitor setups (@ home has 3 external monitors, @ work has 2
external + laptop's LCD, and @ work2 has 1 large monitor + laptop's LCD).

I too was frustrated with managing environments every time I disconnect and
move to another location (@ work with a nice arrangement, on train with
only built-in LCD, back at home to continue working... argh, have to
rearrange everything).

What I ended up doing was binding a few keys to "move the entire workspace
from one monitor to another monitor", keeping the exact arrangement:

https://github.com/eduncan911/env-scripts/blob/master/.i3/config#L204-L208

^- see highlighted lines starting with "bindsym $mod+Control+Shift+Left
move workspace to output left"

-E


On Fri, Mar 20, 2015 at 12:16 PM, Ultrabug  wrote:

>  As a side note if you're a py3status user or want to give it a try, one
> of the features of the *xrandr* module [1] allows you to automatically
> move a workspace to an output when it's activated.
>
> If I'm not mistaken, that's the behavior you were after.
> Quick doc abstract :
>
> This modules allows you to handle your screens outputs directly from your bar!
> - Detect and propose every possible screen combinations
> - Switch between combinations using click events and mouse scroll
> - Activate the screen or screen combination on a single click
> - It will detect any newly connected or removed screen automatically
>
> For convenience, this module also proposes some added features:
> - Dynamic parameters for POSITION and WORKSPACES assignment (see below)
> - Automatic fallback to a given screen or screen combination when no more
> screen is available (handy for laptops)
> - Automatically apply this screen combination on start: no need for xorg!
> - Automatically move workspaces to screens when they are available
>
>
> Maybe it can be of interest to someone, cheers.
>
> [1]
> https://github.com/ultrabug/py3status/blob/master/py3status/modules/xrandr.py
>
> On 26/02/2015 14:36, Guillaume Maudoux (Layus) wrote:
>
> Ok, reached a stable solution.
> A restart is needed because otherwise the missing (i3)bars for the new
> display are not started.
>
> If some are interested, here is the gist :
> https://gist.github.com/layus/89a6bb8feebe6c1f96d2#file-postswitch
>
> Layus.
>
> PS : No bug yet with the "next" branch :)
>
> Le 21/02/15 12:05, Michael Stapelberg a écrit :
>
> Correct. I’m not sure if reload does the trick or if a restart is
> required. In case reload is not sufficient, I bet TonyC is interested
> in fixing that ;).
>
> On Sat, Feb 21, 2015 at 11:47 AM, Layus 
>  wrote:
>
> @Michael,
>
> You mean that I should rewrite .i3/config and reload (restart?) i3 every
> time I detect a monitor change, right ?
>
> This seems a bit overkill but might just work.
> I will try that on Monday.
>
> Le 21/02/15 11:25, Michael Stapelberg a écrit :
>
> For the level of customization you describe, you’ll need to create a
> simple script that generates/puts together your config file. See e.g.
> https://faq.i3wm.org/question/1367/anyway-to-include-in-config-file/
>
> On Tue, Feb 17, 2015 at 9:31 PM, Serge van Ginderachter
>   wrote:
>
> fwiw, I use a script that detects things like which monitor is connected,
> and falls back to certain defaults, or can be forced to e.g. VGA display
> etc.
>
>   https://github.com/srvg/dotfiles/blob/master/bin/xdisp
>
> HTH,
>
> Serge
>
> On 17 February 2015 at 21:24, Layus 
>  wrote:
>
> Hi,
>
> I use my laptop in three different environments with different randr
> outputs enabled.
> I often switch between environments, and could not configure i3 to place
> my workspaces on the desired outputs.
> My randr configuration is updated automatically on udev drm change
> events
> with autorandr.
> Is there some way to specify dynamic output bindings ?
>
> My three environments are pretty simple :
>
> Nomad (undocked)
>
> eDP1 connected primary ← all workspaces
>
> Docked
>
> eDP1 connected ← workspace 0
> DP1-1 connected primary ← all other workspaces
>
> Presentation
>
> VGA1 connected ← workspace 0
> eDP1 connected primary ← all other workspaces
>
> My current config works for situation 1 and 2 :
>
> workspace 0 output eDP1
>
> workspace 1 output DP1-1
> workspace 2 output DP1-1
> workspace 3 output DP1-1
> workspace 4 output DP1-1
> workspace 5 output DP1-1
> workspace 6 output DP1-1
> workspace 7 output DP1-1
> workspace 8 output DP1-1
> workspace 9 output DP1-1
> workspace 10 output DP1-1
>
> This is already a hack because the configuration describes the Docked
> configuration.
> It incidentally works when Undocked because there is only one output,
> and
> all workspaces are mapped to it.
>
> It does not work at all for my presentation.
>
> One solution that would suit me would be to extend the workspace 
> output command to support multiple outputs in order of preference.
> for example, worspace 0 output(s) VGA1 eDP

[i3] Split-Views in Tabs: Display Window Titles, not process name

2015-03-20 Thread Eric Duncan
Hello!

I've been using i3wm for a little over a year.  Recently I've been using
the Tabs feature, grouping several terminal windows in different tabs
(monitoring a dozen or so logs).  I have my .bash environment set the
Window Title properly for terminals, and that works with single tabs -
displaying the gnome-terminal's title in the Tab's title just like it
should.

"Single Tabs" meaning with only 1 process running within that tab, i3wm
shows the Window Title of that one process.  E.g. my gnome-terminal's
window title.

This message is about tabs that have multiple processes running within the
tab's i3wm container.  E.g. two or more terminal windows.  i3wm currently
displays in the window title of the tab:

i3: H[gnome-terminal gnome-terminal]

It is obviously showing the process name, and that I am split via Height.
Cool, but I am missing the Window Title I have set in the terminals.
Again, the Tab's Window Title normally displays the Window Title of the
executing process.  It's when grouping multiple processes within a single
tab.

I think the "H" and "V" is fine. I get things like this:

i3: H[V[gnome-terminal gnome-terminal] V[gnome-terminal gnome-terminal]]

That obviously says I have a 2x2 arrangement in that tab.  It would really
nice if it showed the Window Title of those processes though.  For example,
if the terminal has the current path set for Window Title, it would look
like:

i3: H[V["~/code/sp-validator" "~/code/sp-juke"] V["~/go/src/
github.com/eduncan911/go-mspec" "~/"]]

Now, you'll notice I put in quotations. An additional tweak may be to put
in some type of delimier for when titles have spaces - so we know the
different in a title like this:

i3: H[Evolution Inbox ~/code/sp-validator:grep]

^- That's two different apps running in horizonal split view.  Without
quotes around "Evolution Inbox", it would hard to determine where the first
one ends and second begins.

Just a suggestion to an awesome window manager!

Thanks!
Eric