[i3] [meta] Migrating mailing lists to freelists.org
Hey, For the last 6 years, I have hosted the i3-announce and i3-discuss mailing lists myself. Now, I’m looking to retire the server which hosts these lists without a replacement — there’s nothing exciting about hosting a mailman instance, it’s just work. Hence, I’ve decided to migrate the i3-announce and i3-discuss mailing lists to freelists.org, who have agreed to host these lists (thanks!). All subscribers and the archives will be migrated, so you do not need to re-subscribe. What you might need to change are filters (as the list-id will change) and the address to which you will send emails in order to post to the lists. The subjects will stay the same. The i3-announce list is already set up, see https://www.freelists.org/list/i3-announce The i3-discuss list will follow early next week. I will let you know once the migration is done via a post on the new lists. If you have any significant concerns about this, please let me know in a private email thread. In case you do not want to be on either of the lists anymore, please unsubscribe now. -- Best regards, Michael
Re: [i3] Weird keybinding issue after suspend
If you want to be 100% sure, run `DISPLAY=:1 setxkbmap us; DISPLAY=:1 setxkbmap de; DISPLAY=:1 setxkbmap us`. If afterwards it still doesn’t work, chances are very high that it is NOT an i3 bug. See xinput(1) for your input devices. On Wed, Nov 11, 2015 at 2:55 AM, Benjamin Kaiser <benjaminjkai...@gmail.com> wrote: > Okay I tried with `DISPLAY=:1 setxkbmap us` (wasn't 100% if us was what I > wanted, it didn't print an error when I ran it) and then changed back to > TTY2 (where i3 was loaded) and the keyboard was still unresponsive. > > And yes I meant DISPLAY, that's what I typed, I just copied it out wrong > in the email. > > What commands can I run to list all input devices? Maybe that might help > investigate things. > Do you have any other ideas what could be causing it? > > Thanks again for your help! > > On Mon, 9 Nov 2015 at 03:48 Michael Stapelberg <mich...@i3wm.org> wrote: > >> On Sun, Nov 8, 2015 at 6:01 AM, Benjamin Kaiser < >> benjaminjkai...@gmail.com> wrote: >> >>> So the issue popped up again, these were the steps I did to debug it: >>> >>> - jump to TTY3 >>> - run: `DISAPLY=:1 setxkbmap | tee /tmp/setxkbmap.out` (not sure if I >>> should have been passing any arguments specifically) >>> >> >> I meant using e.g. “setxkbmap de” to set the keyboard layout. Also, I >> think you meant DISPLAY. >> >> >>> - observe there was no output >>> - jump back to TTY2, keyboard/keybindings still unresponsive in i3 >>> - jump back to TTY2 >>> - run `DISAPLY=:1 xev | tee /tmp/xev.out` (output starts spewing out, >>> and also to the file) >>> - jump back to TTY2, keyboard is now responsive to i3wm bindings >>> - jump back to TTY3 and kill xev >>> >>> Output in `/tmp/xev.out`: http://p.nnev.de/7524 >>> >>> Hope this helps with tracking down what could be causing this, as I >>> still don't have much of a clue how to fix it. >>> >>> Cheers, >>> Ben Kaiser >>> >>> On Mon, 2 Nov 2015 at 20:54 Benjamin Kaiser <benjaminjkai...@gmail.com> >>> wrote: >>> >>>> Thanks for the reply Michael, >>>> >>>> I had the issue happen again yesterday and ran `sudo >>>> libinput-debug-events`, then changed back to i3, run a bunch of shortcuts >>>> and pressed a bunch of keys (all of which did nothing) then changed back to >>>> the tty only to see that it was registering those keys being pressed. >>>> >>>> I'll try running `setxkbmap` and `xev` from a TTY next time the issue >>>> occurs to see if it fixes it / gives me any more information. >>>> >>>> Also another small thing I noticed. To get out of the situation I click >>>> the workspaces, but the keyboard only works if I click a different >>>> workspace the the one I am currently in, it doesn't do anything (keyboard >>>> still won't register shortcuts) if I click the current workspace. >>>> >>>> modified my i3config to that (i3lock then systemctl suspend), I think >>>> it was that at some point and the issue still occurred, but I'll try it out >>>> let you know if the issue happens again. >>>> >>>> Cheers, >>>> Ben Kaiser >>>> >>>> On Mon, 2 Nov 2015 at 19:00 Michael Stapelberg <mich...@i3wm.org> >>>> wrote: >>>> >>>>> When this situation happens: >>>>> >>>>> 1. Does running xev(1) still show keyboard events? >>>>> >>>>> 2. Does using setxkbmap to set your layout make the problem go away? >>>>> That should force i3 to re-grab all keys. >>>>> >>>>> On Fri, Oct 30, 2015 at 12:38 PM, Benjamin Kaiser < >>>>> benjaminjkai...@gmail.com> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I've got a really weird issue that's been bothering me for perhaps >>>>>> the last 6 months (before then it worked fine, perhaps could have been >>>>>> around when I switched to using my keyboard to suspend). Sometimes when I >>>>>> resume from suspend (I have i3lock launching at the same time as when I >>>>>> suspend) I can unlock my computer, but then no more keyboard events work. >>>>>> The keyboard remains active (lights on) and I can switch to a TTY, but >>>>>> none >>>>>> of the i3 events fire. The only way I can fix it is to use the m
Re: [i3] Weird keybinding issue after suspend
On Sun, Nov 8, 2015 at 6:01 AM, Benjamin Kaiser <benjaminjkai...@gmail.com> wrote: > So the issue popped up again, these were the steps I did to debug it: > > - jump to TTY3 > - run: `DISAPLY=:1 setxkbmap | tee /tmp/setxkbmap.out` (not sure if I > should have been passing any arguments specifically) > I meant using e.g. “setxkbmap de” to set the keyboard layout. Also, I think you meant DISPLAY. > - observe there was no output > - jump back to TTY2, keyboard/keybindings still unresponsive in i3 > - jump back to TTY2 > - run `DISAPLY=:1 xev | tee /tmp/xev.out` (output starts spewing out, and > also to the file) > - jump back to TTY2, keyboard is now responsive to i3wm bindings > - jump back to TTY3 and kill xev > > Output in `/tmp/xev.out`: http://p.nnev.de/7524 > > Hope this helps with tracking down what could be causing this, as I still > don't have much of a clue how to fix it. > > Cheers, > Ben Kaiser > > On Mon, 2 Nov 2015 at 20:54 Benjamin Kaiser <benjaminjkai...@gmail.com> > wrote: > >> Thanks for the reply Michael, >> >> I had the issue happen again yesterday and ran `sudo >> libinput-debug-events`, then changed back to i3, run a bunch of shortcuts >> and pressed a bunch of keys (all of which did nothing) then changed back to >> the tty only to see that it was registering those keys being pressed. >> >> I'll try running `setxkbmap` and `xev` from a TTY next time the issue >> occurs to see if it fixes it / gives me any more information. >> >> Also another small thing I noticed. To get out of the situation I click >> the workspaces, but the keyboard only works if I click a different >> workspace the the one I am currently in, it doesn't do anything (keyboard >> still won't register shortcuts) if I click the current workspace. >> >> modified my i3config to that (i3lock then systemctl suspend), I think it >> was that at some point and the issue still occurred, but I'll try it out >> let you know if the issue happens again. >> >> Cheers, >> Ben Kaiser >> >> On Mon, 2 Nov 2015 at 19:00 Michael Stapelberg <mich...@i3wm.org> wrote: >> >>> When this situation happens: >>> >>> 1. Does running xev(1) still show keyboard events? >>> >>> 2. Does using setxkbmap to set your layout make the problem go away? >>> That should force i3 to re-grab all keys. >>> >>> On Fri, Oct 30, 2015 at 12:38 PM, Benjamin Kaiser < >>> benjaminjkai...@gmail.com> wrote: >>> >>>> Hello, >>>> >>>> I've got a really weird issue that's been bothering me for perhaps the >>>> last 6 months (before then it worked fine, perhaps could have been around >>>> when I switched to using my keyboard to suspend). Sometimes when I resume >>>> from suspend (I have i3lock launching at the same time as when I suspend) I >>>> can unlock my computer, but then no more keyboard events work. The keyboard >>>> remains active (lights on) and I can switch to a TTY, but none of the i3 >>>> events fire. The only way I can fix it is to use the mouse (which is still >>>> working) to click on a workspace in the statusbar and then the keyboard >>>> responds again. >>>> >>>> As mentioned above, it only happens sometimes, and as a fellow dev it >>>> really annoys me to no end when something is unreproducible. Things I have >>>> tried to reproduce are just suspending, then detaching my keyboard and >>>> attaching it again before resuming from suspend, but that doesn't trigger >>>> the issue. Just about the only common thing I can find is time (after being >>>> suspended for a long time, 12hours+, it seems to happen more frequently). >>>> >>>> One idea I've had is that because I use a keyboard shortcut to suspend >>>> (`bindsym --release $mod+Control+Shift+s exec "systemctl suspend; i3lock"` >>>> in my config, the -- >>>> >>> >>> nit: you should i3lock first, then suspend. That way, your screen is >>> guaranteed to be locked in a race-free way when you resume. “i3lock && >>> systemctl” suspend should work. >>> >>> >>>> release was me weeks ago trying to rectify the issue, but it still >>>> persisted) i3wm is somehow holding onto the keyboard before flushing, but >>>> then post-suspend, i3lock takes the keyboards focus, i3wm holds onto an old >>>> un-flushed pointer to the keyboard (not sure if that is how that works) and >>>> doesn't refresh
Re: [i3] Weird keybinding issue after suspend
When this situation happens: 1. Does running xev(1) still show keyboard events? 2. Does using setxkbmap to set your layout make the problem go away? That should force i3 to re-grab all keys. On Fri, Oct 30, 2015 at 12:38 PM, Benjamin Kaiserwrote: > Hello, > > I've got a really weird issue that's been bothering me for perhaps the > last 6 months (before then it worked fine, perhaps could have been around > when I switched to using my keyboard to suspend). Sometimes when I resume > from suspend (I have i3lock launching at the same time as when I suspend) I > can unlock my computer, but then no more keyboard events work. The keyboard > remains active (lights on) and I can switch to a TTY, but none of the i3 > events fire. The only way I can fix it is to use the mouse (which is still > working) to click on a workspace in the statusbar and then the keyboard > responds again. > > As mentioned above, it only happens sometimes, and as a fellow dev it > really annoys me to no end when something is unreproducible. Things I have > tried to reproduce are just suspending, then detaching my keyboard and > attaching it again before resuming from suspend, but that doesn't trigger > the issue. Just about the only common thing I can find is time (after being > suspended for a long time, 12hours+, it seems to happen more frequently). > > One idea I've had is that because I use a keyboard shortcut to suspend > (`bindsym --release $mod+Control+Shift+s exec "systemctl suspend; i3lock"` > in my config, the -- > nit: you should i3lock first, then suspend. That way, your screen is guaranteed to be locked in a race-free way when you resume. “i3lock && systemctl” suspend should work. > release was me weeks ago trying to rectify the issue, but it still > persisted) i3wm is somehow holding onto the keyboard before flushing, but > then post-suspend, i3lock takes the keyboards focus, i3wm holds onto an old > un-flushed pointer to the keyboard (not sure if that is how that works) and > doesn't refresh it upon i3lock giving up focus. > From searching around in the i3 source code, seeing the line in > main.c:main() with the comment annotation > /* Grab the keyboard to get all input */ > xcb_flush(conn); > And that function also occuring in click.c:route_click() (i.e. when I > click the workspaces in the status bar) > xcb_flush(conn); > Maybe this is what is allowing the keyboard to work again. Is there some > way this could be run upon i3lock giving up focus / i3wm resuming focus? > > Any help in solving this would be much appreciated! > > Here is some information about my system: > Mouse: Razer Naga, (one with 12 buttons on side) > Keyboard: ducky shine 3 with mini usb cable for connection (issue has > occurred on my laptops internal keyboard also though) > Distro: Arch Linux > i3 Version: 4.11 > Kernel version: 4.2.3-1-ARCH > > Cheers, > Ben Kaiser > -- Best regards, Michael
Re: [i3] Debugging techniques.
Starting i3 with --shmlog-size is a good idea if you’re interested in the logs, and we even ship a session file for that (so that you can just select “i3 (with debug log)” in your session manager: https://github.com/i3/i3/blob/next/i3-with-shmlog.xsession.desktop As for “-V -d all”, I already mentioned how it might be inconvenient for users to rotate the log files away. As long as you’re prepared for that, go ahead :). On Fri, Oct 30, 2015 at 10:56 PM, Layus <layus...@gmail.com> wrote: > Thank you for the detailed answer. > > I think I have sorted it all out. > > My use case is an i3 session started with some session manager like gdm or > kdm (or any other *dm). > In that setup, the users have little access to the arguments passed to i3. > > Let's assume the system uses an i3 build from git@master. > It should be sufficient to start i3 as "i3 --shmlog-size=2500 -V -d > all" to get extended logs including the starting phase, and suitable for > bug reports. > > If users are annoyed by the memory usage, they can add 'exec > --no-startup-id i3-msg shmlog no' to their config. > > This way, I enable users to > 1) access complete logs suitable for debug without needing root access > 2) disable i3 logging if they do not want it > > If it is not an up-to-date git build, they can still use the logs it for > their own debug purposes. > > Do you think the idea of always starting i3 with the > "--shmlog-size=2500 -V -d all" parameters makes sense ? > > -- > Regards, > Layus > > > On 27/10/15 15:22, Michael Stapelberg wrote: > > > > On Tue, Oct 27, 2015 at 7:01 AM, Guillaume Maudoux (Layus) < > <layus...@gmail.com>layus...@gmail.com> wrote: > >> Hello world! >> >> I am trying to enable debugging in i3, and I am confused by the number of >> different options to do this. >> >>command line config option >> -- - >> 1 i3 --shmlog-size=X shmlog on|off|toggle| >> > > Note that “shmlog on|off|toggle|” refers to a command, not a config > directive. > > 2 i3 -V ? >> > > Errors (ELOG in the code) are always printed to stdout. > Verbose log messages (LOG in the code) are printed to stdout if -V is > enabled. Intended for curious users. > Debug log messages (DLOG in the code) are printed if -d is enabled. > > >> 3 i3 -d all ? >> 4 ? debuglog on|off|toggle >> > > 3 and 4 are the same setting. The “all” argument to -d is obsolete, but > kept for backwards compatibility. > > See also https://github.com/i3/i3/issues/1823 for a related discussion. > > >> >> So my question are: >> >> Which one is the recommended way ? >> > > The recommended way is to use an automatically built version from > http://i3wm.org/docs/repositories.html (or i3-git if your package manager > knows how to build automatically build software from git) because otherwise > any of your findings will need to be confirmed again on a more recent > version. > > These versions automatically enable debug logging to shared memory (they > check whether they were built from a git version that is not a release > version). > > >> Does `shmlog on` imply `debuglog on` ? >> > > No. > > >> Does `-d all` imply `-V` ? >> > > No. > > >> What size do you recommend for the shmlog size ? >> > > 25MB (arbitrarily chosen, but proven to be enough for all issues we’ve > encountered so far). > > >> May I assume that the config options cannot be used to debug issues prior >> to loading the configuration file (nor issues while loading the >> configuration file) ? >> > > If you specify them as command-line parameters to i3, they will be active > before loading the configuration file. > > >> Which of these options provide enough information for a bug report ? Is >> -V enough ? >> > > Please use -V -d all, as per section 2 of > <http://i3wm.org/docs/debugging.html>http://i3wm.org/docs/debugging.html > > >> >> It seems that shm logging is better in the sense that it does not >> increase a log file size, but not as nice as it locks some memory space. >> > > Correct. > > >> What is the reason behind shm logging, instead of the usual logging to >> file + logrotate ? > > > It’s easier for us to set aside a chunk of memory than to make sure that > every user of i3 knows about having to logrotate a file away. Anecdotally, > we’ve had a bunch of users whose hard drive (or RAM, in case of /tmp being > on tmpfs) filled up because of an ever-growing i3 logfile. > > -- > Best regards, > Michael > > > -- Best regards, Michael
Re: [i3] Debugging techniques.
On Tue, Oct 27, 2015 at 7:01 AM, Guillaume Maudoux (Layus) < layus...@gmail.com> wrote: > Hello world! > > I am trying to enable debugging in i3, and I am confused by the number of > different options to do this. > >command line config option > -- - > 1 i3 --shmlog-size=X shmlog on|off|toggle| > Note that “shmlog on|off|toggle|” refers to a command, not a config directive. 2 i3 -V ? > Errors (ELOG in the code) are always printed to stdout. Verbose log messages (LOG in the code) are printed to stdout if -V is enabled. Intended for curious users. Debug log messages (DLOG in the code) are printed if -d is enabled. > 3 i3 -d all ? > 4 ? debuglog on|off|toggle > 3 and 4 are the same setting. The “all” argument to -d is obsolete, but kept for backwards compatibility. See also https://github.com/i3/i3/issues/1823 for a related discussion. > > So my question are: > > Which one is the recommended way ? > The recommended way is to use an automatically built version from http://i3wm.org/docs/repositories.html (or i3-git if your package manager knows how to build automatically build software from git) because otherwise any of your findings will need to be confirmed again on a more recent version. These versions automatically enable debug logging to shared memory (they check whether they were built from a git version that is not a release version). > Does `shmlog on` imply `debuglog on` ? > No. > Does `-d all` imply `-V` ? > No. > What size do you recommend for the shmlog size ? > 25MB (arbitrarily chosen, but proven to be enough for all issues we’ve encountered so far). > May I assume that the config options cannot be used to debug issues prior > to loading the configuration file (nor issues while loading the > configuration file) ? > If you specify them as command-line parameters to i3, they will be active before loading the configuration file. > Which of these options provide enough information for a bug report ? Is -V > enough ? > Please use -V -d all, as per section 2 of http://i3wm.org/docs/debugging.html > > It seems that shm logging is better in the sense that it does not increase > a log file size, but not as nice as it locks some memory space. > Correct. > What is the reason behind shm logging, instead of the usual logging to > file + logrotate ? It’s easier for us to set aside a chunk of memory than to make sure that every user of i3 knows about having to logrotate a file away. Anecdotally, we’ve had a bunch of users whose hard drive (or RAM, in case of /tmp being on tmpfs) filled up because of an ever-growing i3 logfile. -- Best regards, Michael
Re: [i3] i3 new user experiences summary
Thanks for taking the time to follow up. I hope my reply makes things more clear. On Fri, Oct 16, 2015 at 11:33 AM,wrote: > Hi Michael, > > Thanks again for the great piece of software. > > I'm replying off-list because I didn't want to get into a public > I’m adding the list to CC again because I think the clarifications might be useful not only for you, but also for other people interested in the thread. I hope you don’t mind. > argument - at first I thought you were a troll, and then I saw that > you're the author of i3wm! :) Maybe I'm not realizing something about > my suggestions, but here is some more clarification in response to > your comments: > > (regarding i3-config-wizard) > > > The key _positions_ make some sense, the key mnemonics likely don’t. > > I don’t think this is a big problem, as users are very likely to > > change their config file anyway. Also, you’re free to use/not use > > the wizard as you see fit — for most users, using the wizard seems > > to be the best solution, which is why it’s started by default. > > If I recall, the wizard runs (or offers to run) by default, and > doesn't explain what it's doing, so new Dvorak users don't have a > warning of why the config file bindings look so strange - nor do they > have any indication that another option is available for obtaining a > default config. I don't know why you say it seems to be the best > solution for most users - obviously, most users are Qwerty users, for > whom the config wizard does almost nothing, it just queries the user > for a modifier key, IIRC. > It asks for the modifier key and creates the config file. Both of that could be achieved by using “sed 's/$mod Mod1/$mod Mod4/g' /etc/i3/config > ~/.i3/config”, yes. The main point why the wizard starts by default is that the default config file has to use Mod1 (Alt by default) because there are computers which don’t have a physical Mod4 (Windows by default) key. We strongly want to encourage people to use Mod4 as a modifier, because that avoids clashes with key combinations that other software uses. At the same time, we cannot make the default config use Mod4, because then i3 would just not work on computers which lack the Windows key. > > I think we both understand the rationale of the config wizard: it > makes the navigation keys match up - but all the other keys become > wrong, which means that 95% (rough estimate) of the config file is > 13 lines out of 69 lines in the i3 default config are bindings that use keys whose positions typically change depending on the layout — that’s not even 20% :). Regardless of the numbers, I think it boils down to personal preference: i3 currently goes the route where the positions make some sense (navigation keys first and foremost, but also how the remaining keys are positioned). Some people might prefer the mnemonics to make sense. It’s impossible to please both crowds. > wrong. On my system, /etc/i3/config already has variable aliases for > the navigation keys, which seems like a much better solution (didn't > check whether this is part of the Arch package or your i3wm > distribution) > > set $up l > set $down k > set $left j > set $right semicolon > > Why would anyone not prefer to just have a copy of this file in ~/.i3/ > to start out with? > > I'm not sure but it seems like Layus was also agreeing with me in his > reply: "Also, it is easier to have the same bindings on all > installations, even if misplaced. This way, the tutorials can assume > that the users all have Mod+p [sic] for restart." > > > Does “workspace_layout tabbed” do what you want? > > Yes, thank you! > > > Can you please send a pull request for https://github.com/i3/i3 > > which adds an explanation where you think it makes sense? > > I'm not familiar with git but I'll give you a human-readable patch. In > the i3 man page, after: > > Window > > An X11 window, like the Firefox browser window or a terminal > emulator. > > I would insert > > Floating Window > > A window which "floats" on top of other windows. This style is > used by i3 to display X11 windows with type "dialog", such as > the "Print" or "Open File" dialog boxes in many GUI > applications. Use of floating windows can be fine-tuned with > the for_window command (see HTML userguide). > > I think that should be more than enough - I originally became > frustrated when not finding the word "dialog" in the man page. I hope > the last sentence isn't out of place. If you want an actual patch for > that text, let me know. > https://github.com/i3/i3/commit/d56264e00185023d433a913ef468428d345a3c7a > > > > - Even after learning the "floating toggle" binding it sometimes > > > becomes annoying or confusing to have to press it each time - > > > for instance if I have to print a lot of stuff in Firefox, but I > > > sometimes want to navigate to other windows when the print > > > dialog is
Re: [i3] Error: status_command process exited unexpectedly (exit 1)
Could you open an issue for this at https://github.com/i3/i3 please? We’d like to keep all bugs in one place. Also, please try changing your login shell from fish to bash before reporting, just so that you know whether fish is to blame here. We’ve certainly had trouble with fish before. On Wed, Oct 14, 2015 at 11:44 PM, Taro Muraowrote: > Hello, > > when I start i3status with i3 in bar {}, I get the error message: > Error: > status_command process exited unexpectedly (exit 1). Can anyone help? > > I followed the debugging instruction on > http://i3wm.org/docs/debugging.html. > When the bar is displayed with > > $ for c in $(i3-msg -t get_bar_config | python -c \ 'import > json,sys;print("\n".join(json.load(sys.stdin)))'); do \ (i3bar > --bar_id=$c > >i3bar.$c.log 2>&1) & \ done; > > The bar displays without error. I use Fish shell, Arch Linux and KDE. > Below > is the log I obtained with "verbose yes", but the log probably > contains no > error messages because I don't have the error when I restart i3bar > this way. > > i3status: trying to auto-detect output_format setting > i3status: auto-detected "i3bar" > [libi3] libi3/font.c Using Pango font monospace, size 8 > [libi3] libi3/font.c X11 root window dictates 96.094581 DPI > [i3bar/src/xcb.c:1216] Calculated font height: 13 > [i3bar/src/xcb.c:1342] Setting bar_fg = #FF as > _NET_SYSTEM_TRAY_COLORS > [i3bar/src/xcb.c:985] received an xkb event > [i3bar/src/ipc.c:197] Got data! > [i3bar/src/ipc.c:63] Parsing outputs JSON... > > - Ignored: > [i3bar/src/ipc.c:65] Reconfiguring windows... > [i3bar/src/xcb.c:1488] Re-allocating statusline buffer, > statusline_width = > 0, root_screen->width_in_pixels = 1366 > [i3bar/src/xcb.c:1583] Destroying window for output VIRTUAL1 > [i3bar/src/xcb.c:1583] Destroying window for output VGA1 > [i3bar/src/xcb.c:1583] Destroying window for output HDMI3 > [i3bar/src/xcb.c:1583] Destroying window for output HDMI2 > [i3bar/src/xcb.c:1583] Destroying window for output HDMI1 > [i3bar/src/xcb.c:1583] Destroying window for output DP3 > [i3bar/src/xcb.c:1583] Destroying window for output DP2 > [i3bar/src/xcb.c:1583] Destroying window for output DP1 > [i3bar/src/xcb.c:1588] Creating window for output LVDS1 > [i3bar/src/xcb.c:1259] Initializing system tray functionality > [i3bar/src/xcb.c:1342] Setting bar_fg = #FF as > _NET_SYSTEM_TRAY_COLORS > [i3bar/src/xcb.c:1793] Drawing bars... > [i3bar/src/xcb.c:1801] Output VIRTUAL1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output VGA1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI3 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI2 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP3 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP2 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP1 inactive, skipping... > [i3bar/src/ipc.c:197] Got data! > [i3bar/src/ipc.c:54] Got subscribe reply: {"success":true} > [i3bar/src/ipc.c:197] Got data! > [i3bar/src/ipc.c:43] Got workspace data! > [i3bar/src/workspaces.c:142] Got workspace canonical: 1, name: '1', > name_width: 7, glyphs: 1 > [i3bar/src/workspaces.c:142] Got workspace canonical: 2, name: '2', > name_width: 7, glyphs: 1 > [i3bar/src/xcb.c:1793] Drawing bars... > [i3bar/src/xcb.c:1801] Output VIRTUAL1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output VGA1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI3 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI2 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP3 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP2 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP1 inactive, skipping... > [i3bar/src/xcb.c:1825] Drawing button for WS 1 at x = 0, len = 7 > [i3bar/src/xcb.c:1825] Drawing button for WS 2 at x = 18, len = 7 > [i3bar/src/child.c:420] Detecting input type based on buffer > *{"version":1} > [ > * > [i3bar/src/xcb.c:1793] Drawing bars... > [i3bar/src/xcb.c:1801] Output VIRTUAL1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output VGA1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI3 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI2 inactive, skipping... > [i3bar/src/xcb.c:1801] Output HDMI1 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP3 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP2 inactive, skipping... > [i3bar/src/xcb.c:1801] Output DP1 inactive, skipping... > [i3bar/src/xcb.c:1825] Drawing button for WS 1 at x = 0, len = 7 > [i3bar/src/xcb.c:1825] Drawing button for WS 2 at x = 18, len = 7 > [i3bar/src/child.c:297]
Re: [i3] i3 new user experiences summary
Thanks for writing this up. Answers inline. On Wed, Oct 14, 2015 at 1:08 AM, Frederik Eatonwrote: > Hello All! > > I just switched from Notion to i3 about a month ago. In general it's > been a positive experience, I especially appreciate the smaller > configuration file, the more sensible default bindings, the ability to > put windows in a tree (if that's the correct word). > > After settling in, I made a quick list of some issues I ran into and > wanted to report back to the developers. > > - As a user of the Dvorak keyboard layout, I was confused by the > result of running i3-config-wizard. I can see how h,t,n,s could be > used for navigation, but many of the remaining key bindings don't > make sense - why should 'd' split horizontally, or 'p' restart? This > wasn't really explained to me through the process of installing and > trying out the software. I ended up having to revert most of the > bindings to the Qwerty defaults. I think the wizard made things more > difficult in the end. > The key _positions_ make some sense, the key mnemonics likely don’t. I don’t think this is a big problem, as users are very likely to change their config file anyway. Also, you’re free to use/not use the wizard as you see fit — for most users, using the wizard seems to be the best solution, which is why it’s started by default. > > - Coming from Notion, I would have expected the default window layout > to be tabbed. At first I thought that i3 didn't support a tabbed > layout, because when I first started it (with killall notion; i3), I > ended up with 10 unusably-narrow windows. I still don't know how to > make tabbing the default - when I open windows on a new workspace, > they always come up split. If I kill and restart i3, then everything > comes up split (and uselessly narrow). > Does “workspace_layout tabbed” do what you want? > > - I had to ask the IRC channel for the name of the key binding to turn > a dialog box into a window - perhaps the documentation should be > improved so new users can avoid this hurdle (e.g. under TERMINOLOGY > in the man page, there could be an entry explaining that a "Floating > Window" is something like a dialog box). > Can you please send a pull request for https://github.com/i3/i3 which adds an explanation where you think it makes sense? > > - Even after learning the "floating toggle" binding it sometimes > becomes annoying or confusing to have to press it each time - for > instance if I have to print a lot of stuff in Firefox, but I > sometimes want to navigate to other windows when the print dialog is > open. I also sometimes accidentally turn Firefox into a floating > window when I'm doing this, and then I wonder where all the other > windows went I would appreciate an option to have dialogs always > come up as windows by default. > If the print dialog is clearly meant to be floating, Firefox should set the appropriate window hints. Since you describe you have to manually make it floating, apparently Firefox doesn’t. You should file a Firefox bug, but you can work around this with a for_window rule, see http://i3wm.org/docs/userguide.html#_arbitrary_commands_for_specific_windows_for_window > > - "focus right" is not always the reverse of "focus left". For > instance, if the rightmost tab is split horizontally, then one > command will cycle through all the windows, but the other will get > stuck cycling through the children of the tab which has been split. > Same with "focus up" and "focus down" in the stacking layout, when a > child is split vertically. It seems it would be cleaner to have > these pairs be strict opposites. > There are several places where the directional commands don’t strictly operate on the tree and hence focus left/right are not always direct opposites. We believe that bottomline, this makes it easier for users. Even if it didn’t make it easier for users, changing it now would be very disruptive to existing users, so I don’t think we can do much about it. If you feel strongly, you might be able to implement your own logic using the IPC interface: http://i3wm.org/docs/ipc.html > > - I like that "i3-nagbar" is available to display error messages, but > I don't know how to close it with my keyboard... seems like I have > to use my mouse to close it. I'd prefer to avoid the mouse...! > It’s designed to nag you, so this is working as intended :). > > > Well, I hope this isn't too much stuff at once. I'm happy with i3 so > even if you don't fix any of these problems, I'll still use it. As I > mentioned above, I just wanted to report back since it's not always > easy to anticipate how new users will experience a piece of software. > > Thanks for all your hard work in developing i3! > > Best wishes, > > Frederik > -- Best regards, Michael
Re: [i3] Problems getting Ubuntu repository working
http://i3wm.org/docs/repositories.html lists: # echo "deb http://debian.sur5r.net/i3/ $(lsb_release -c -s) universe" >> /etc/apt/sources.list That command has to be executed. The $(lsb_release -c -s) part will be replaced by your Ubuntu version when you do that. It seems like you have not properly executed the command, based on the -c and -s flags showing up in your sources.list. On Tue, Oct 13, 2015 at 5:31 AM, Matt Ilacquawrote: > Realized my version of i3 is 4.7.2 and that the sur5r repository wasn't > working for me. I'm using xubuntu 14.04 LTS > > Here's what I see with apt-get update: > > Ign http://debian.sur5r.net -c InRelease > > Ign http://debian.sur5r.net -c Release.gpg > Ign http://debian.sur5r.net -c Release > Err http://debian.sur5r.net -c/-s) i386 Packages > 404 Not Found [IP: 217.8.49.41 80] > Err http://debian.sur5r.net -c/universe i386 Packages > 404 Not Found [IP: 217.8.49.41 80] > Ign http://debian.sur5r.net -c/-s) Translation-en_US > Ign http://debian.sur5r.net -c/-s) Translation-en > Ign http://debian.sur5r.net -c/universe Translation-en_US > > Ign http://debian.sur5r.net -c/universe Translation-en > > W: Failed to fetch > http://debian.sur5r.net/i3/dists/-c/-s)/binary-i386/Packages 404 Not > Found [IP: 217.8.49.41 80] > > W: Failed to fetch > http://debian.sur5r.net/i3/dists/-c/universe/binary-i386/Packages 404 > Not Found [IP: 217.8.49.41 80] > > E: Some index files failed to download. They have been ignored, or old > ones used instead. > > And in my /etc/apt/sources.list file I have: > > deb http://debian.sur5r.net/i3/ -c -s) universe > > I also tried directly copying "deb http://debian.sur5r.net/i3/ $(lsb_release > -c -s) universe" right into sources.list and am still getting 404's in my > sudo apt-get update. > > Any info or suggestions would be appreciated. Thanks! > -- Best regards, Michael
Re: [i3] Mouse capture problem i3 and OBS
Have you tried reproducing this problem with any other window manager that offers a tabbed mode? On Thu, Oct 1, 2015 at 12:36 PM, Zennywrote: > Hi, > > Having problem with redundant mouse capture in OBS running with i3-wm. > > When the mouse is moved to change some recording settings in the OBS > interface at the bottom or in the canvas, the mouse movement for those > modifications gets displayed in the canvas and gets recorded in the > final input, even when there is no source of screen capture of the > machine in which OBS is running. > > This problem is only when in the tabbed mode, but not in the tiling > mode of i3-wm. By changing the tabbed mode ($MOD+w) to tiling mode > ($MOD+e), the mouse movements for OBS settings modifications > disappears and that is what actually desired. > > Posted a bug report to OBS guys: > https://obsproject.com/mantis/view.php?id=340 and posting here if that > has to anything with i3-wm? > > Thanks! > > /z > -- Best regards, Michael
Re: [i3] How to display in `i3bar` (via `i3status`) the amount of free memory
On Wed, Sep 16, 2015 at 2:22 PM, Ciprian Dorin Craciun <ciprian.crac...@gmail.com> wrote: > On Wed, Sep 16, 2015 at 2:26 PM, Michael Stapelberg <mich...@i3wm.org> wrote: >> The recommended way is to wrap i3status as described in its manpage. > > The whole purpose of `i3status` is that it's lightweight both in terms > of resources and OS calls. Wrapping it in a script that each second > spawns a bunch of processes just to add memory usage is counter to its > purpose... You can use a higher-level language to wrap i3status. > > But anyway, as this is an open-source project where development is > done voluntarily (and for free), and as I don't have time right now to > patch it, I'll live it at this... (Moreover as with the previous > patches there is a high chance the patch won't be accepted in > upstream, leaving me to maintain my own fork of it, which I have even > less time for...) :) > > However I would like to ask the developers to please reconsider adding > such a basic and useful piece of information. (But as said I'll live > this here.) We don’t have a great mental framework for deciding what goes into i3status and what doesn’t. The current state of affairs is that things that I deemed useful 7 years ago (wow, time flies) are in i3status, and we’re very conservative when it comes to adding new things (or even removing things that I wouldn’t add if I were to start from scratch, like cpu temperature). Other status bars (j4status, py3status, etc.) might be better suited for your use-case. -- Best regards, Michael
Re: [i3] resize with mouse
I haven’t done much with Xfixes, so I’m not sure, but it sounds like you have a concrete idea in mind. Feel free to reopen #706 and prove me wrong :). On Fri, Sep 11, 2015 at 9:38 PM, Ingo Bürk <ad...@airblader.de> wrote: > Michael, are we sure that using Xfixes wouldn't make this a whole lot > easier? I'm not familiar with the resizing code, really, but I didn't > quite understand in that issue (#706) why we need separate windows? > > On 09/11/2015 07:24 PM, Michael Stapelberg wrote: >> On Fri, Sep 11, 2015 at 7:18 PM, Jeff Abrahamson <j...@purple.com> wrote: >>> I was not aware of Mod + RightClick. That's cool. Thanks. And in that >>> context the warp to boundary makes sense: it makes clear what I'm about to >>> do. >>> >>> Mod + RightClick also works for both H and V resize. >>> >>> So this leaves two questions, since maybe they are bugs, maybe not: >>> >>> 1. Is it intentional, given that non-mod LeftClick can resize, that there >>> is no feedback on hovering over a window edge? >> https://github.com/i3/i3/issues/706 >> >>> 2. And is it a bug that vertical resize doesn't work without Mod? >> Not sure what you mean by that. I can resize windows in any direction just >> fine. >> >>> I haven't seen fit to restart i3 today (work to do), although I grabbed >>> sources to compile from git master. I'll check once I've compiled and >>> restarted. >>> >>> Jeff Abrahamson >>> +33 6 24 40 01 57 >>> +44 7920 594 255<-- only if I'm in the UK >>> >>> http://jeff.purple.com/ >>> http://blog.purple.com/jeff/ >>> >>> On 11 September 2015 at 19:04, Micah Elliott <m...@micahelliott.com> wrote: >>>>> The target seems to be three pixels wide >>>> It's not clear if you're aware of the incredibly convenient "Mod + >>>> RightClick" to drag window resizing. Then you can quickly click just >>>> about anywhere on the screen and be grabbing an edge. The feature may >>>> render your concerns moot. >>>> >>>> -- >>>> twitter:@MicahElliott | email:m...@micahelliott.com | >>>> http://membean.com >>>> Remember your words with Membean! >>> > -- Best regards, Michael
Re: [i3] resize with mouse
On Fri, Sep 11, 2015 at 7:18 PM, Jeff Abrahamsonwrote: > I was not aware of Mod + RightClick. That's cool. Thanks. And in that > context the warp to boundary makes sense: it makes clear what I'm about to > do. > > Mod + RightClick also works for both H and V resize. > > So this leaves two questions, since maybe they are bugs, maybe not: > > 1. Is it intentional, given that non-mod LeftClick can resize, that there > is no feedback on hovering over a window edge? https://github.com/i3/i3/issues/706 > > 2. And is it a bug that vertical resize doesn't work without Mod? Not sure what you mean by that. I can resize windows in any direction just fine. > > I haven't seen fit to restart i3 today (work to do), although I grabbed > sources to compile from git master. I'll check once I've compiled and > restarted. > > Jeff Abrahamson > +33 6 24 40 01 57 > +44 7920 594 255<-- only if I'm in the UK > > http://jeff.purple.com/ > http://blog.purple.com/jeff/ > > On 11 September 2015 at 19:04, Micah Elliott wrote: >> >> > The target seems to be three pixels wide >> >> It's not clear if you're aware of the incredibly convenient "Mod + >> RightClick" to drag window resizing. Then you can quickly click just >> about anywhere on the screen and be grabbing an edge. The feature may >> render your concerns moot. >> >> -- >> twitter:@MicahElliott | email:m...@micahelliott.com | >> http://membean.com >> Remember your words with Membean! > > -- Best regards, Michael
Re: [i3] Keep windows focused on workspace move
Yeah, but bindsym doesn’t match anything. You need to use criteria to match windows. On Thu, Sep 3, 2015 at 8:44 PM, Ingo Bürk <ad...@airblader.de> wrote: > It should work with just "focus" because the separation with a comma > means the focus command will still be ran on the matched window. > > On 09/03/2015 08:40 PM, Michael Stapelberg wrote: >> What are you trying to accomplish with “exec i3-msg workspace $WS1”? >> This is equivalent to just “workspace $WS1”, but will be executed >> out-of-order because it spawns a new process in the background which >> sends the command. >> >> Also, I think the “focus” command used on its own (i.e. without any >> criteria) is a no-op. >> >> The previously mentioned “move container to workspace 1, workspace 1” >> command is the way to go. >> >> On Wed, Sep 2, 2015 at 4:59 PM, Serge Kroes <se...@kroescontrol.nl> wrote: >>> Hi >>> >>> i'm using this: >>> bindsym $mod+Shift+1 move container to workspace $WS1, exec i3-msg workspace >>> $WS1, focus >>> >>> >>> On Wed, Sep 2, 2015 at 4:38 PM, Florian Lindner <mailingli...@xgm.de> wrote: >>>> Hello, >>>> >>>> Am Mittwoch, 2. September 2015, 16:17:56 schrieb Mateusz Poszwa: >>>>> Je 2015-09-02 16:06:41 >>>>> Florian Lindner <mailingli...@xgm.de> skribis: >>>>> >>>>>> Hello, >>>>>> >>>>>> when I move a window from a workspace to another (mod + shift + num) >>>>>> it looses the focus and a window (or parent) of the originating >>>>>> workspace is >>>>>> focused. >>>>>> >>>>>> How can I have the window to stay focused when moved across >>>>>> workspaces? >>>>>> >>>>>> Use case: >>>>>> I have a conversation open on the small and farer away laptop screen. >>>>>> I see activity there and I move it to one of my main screens. I want it >>>>>> to >>>>>> keep focused. >>>>>> >>>>>> Best Regards, >>>>>> Florian >>>>> Hello. >>>>> >>>>> Try to change your binding from >>>>> move workspace «X» >>>>> to >>>>> move workspace «X», focus workspace «X» >>>> I have set it to: >>>> >>>> bindsym $mod+Shift+1 move container to workspace 1, focus workspace 1 >>>> bindsym $mod+Shift+2 move container to workspace 2, focus workspace 2 >>>> bindsym $mod+Shift+3 move container to workspace 3, focus workspace 3 >>>> bindsym $mod+Shift+4 move container to workspace 4, focus workspace 4 >>>> [...] >>>> >>>> but that shows no effect. >>>> >>>> Thanks, >>>> Florian >>> >>> >>> >>> -- >>> Serge Kroes | Kroescontrol | LinkedIn | Twitter >> >> > -- Best regards, Michael
Re: [i3] Keep windows focused on workspace move
What are you trying to accomplish with “exec i3-msg workspace $WS1”? This is equivalent to just “workspace $WS1”, but will be executed out-of-order because it spawns a new process in the background which sends the command. Also, I think the “focus” command used on its own (i.e. without any criteria) is a no-op. The previously mentioned “move container to workspace 1, workspace 1” command is the way to go. On Wed, Sep 2, 2015 at 4:59 PM, Serge Kroeswrote: > Hi > > i'm using this: > bindsym $mod+Shift+1 move container to workspace $WS1, exec i3-msg workspace > $WS1, focus > > > On Wed, Sep 2, 2015 at 4:38 PM, Florian Lindner wrote: >> >> Hello, >> >> Am Mittwoch, 2. September 2015, 16:17:56 schrieb Mateusz Poszwa: >> > Je 2015-09-02 16:06:41 >> > Florian Lindner skribis: >> > >> > > Hello, >> > > >> > > when I move a window from a workspace to another (mod + shift + num) >> > > it looses the focus and a window (or parent) of the originating >> > > workspace is >> > > focused. >> > > >> > > How can I have the window to stay focused when moved across >> > > workspaces? >> > > >> > > Use case: >> > > I have a conversation open on the small and farer away laptop screen. >> > > I see activity there and I move it to one of my main screens. I want it >> > > to >> > > keep focused. >> > > >> > > Best Regards, >> > > Florian >> > >> > Hello. >> > >> > Try to change your binding from >> > move workspace «X» >> > to >> > move workspace «X», focus workspace «X» >> >> I have set it to: >> >> bindsym $mod+Shift+1 move container to workspace 1, focus workspace 1 >> bindsym $mod+Shift+2 move container to workspace 2, focus workspace 2 >> bindsym $mod+Shift+3 move container to workspace 3, focus workspace 3 >> bindsym $mod+Shift+4 move container to workspace 4, focus workspace 4 >> [...] >> >> but that shows no effect. >> >> Thanks, >> Florian > > > > > -- > Serge Kroes | Kroescontrol | LinkedIn | Twitter -- Best regards, Michael
Re: [i3] Killing of floating windows with mouse
On Mon, Aug 31, 2015 at 9:37 AM, Florian Lindner <mailingli...@xgm.de> wrote: > Took some days, but here it is https://github.com/i3/i3/issues/1882 > > Logs will be added as soon as I can restart my X session. Are you aware of http://i3wm.org/docs/userguide.html#shmlog? You don’t need to restart your X session. > > Florian > > Am Freitag, 28. August 2015, 08:42:57 schrieb Michael Stapelberg: >> Sounds like a bug to me. Please report it at https://github.com/i3/i3 >> >> On Thu, Aug 27, 2015 at 9:21 AM, Florian Lindner <mailingli...@xgm.de> wrote: >> > Hello, >> > >> > I have that line in my i3 config: >> > >> > # The middle button over a titlebar kills the window >> > bindsym --release button2 kill >> > >> > Which works perfectly on tiling windows, but not on floating windows. >> > Instead I can grabe and move the window with the middle mouse button. >> > >> > There is no other line containing "button2" in my config. >> > >> > Thanks, >> > Florian >> >> >> >> -- Best regards, Michael
Re: [i3] Killing of floating windows with mouse
Sounds like a bug to me. Please report it at https://github.com/i3/i3 On Thu, Aug 27, 2015 at 9:21 AM, Florian Lindner mailingli...@xgm.de wrote: Hello, I have that line in my i3 config: # The middle button over a titlebar kills the window bindsym --release button2 kill Which works perfectly on tiling windows, but not on floating windows. Instead I can grabe and move the window with the middle mouse button. There is no other line containing button2 in my config. Thanks, Florian -- Best regards, Michael
Re: [i3] GLFW_FLOATING window
On Tue, Aug 25, 2015 at 5:53 PM, Kevin J jkev...@umbc.edu wrote: Michael: The reason I want the window to float is if I want a specific resolution for the window (I'm working on an OpenGL project). Especially if the window is Use for_window with floating enable: http://i3wm.org/docs/userguide.html#_arbitrary_commands_for_specific_windows_for_window set to be not user-resizeable, i3 will still resize it to fit it to a tile. Yes, and that’s intentional. You can resize your tiles to show as much of the window content as you need, and application authors should not have a say on how you think arranging your workspace is best. I had read that and thought that maybe that wouldn't be the correct atom to use, but none of the ones i3 uses to determine whether to make a window floating seem correct either (MODAL, DIALOG, UTILITY, TOOLBAR, and SPLASH) Ingo: Thanks, I will look into that once I get back from work. Also instead use a more suitable atom do you know of any that would work? Otherwise should this atom be added to i3's floating window detection? I don’t think it should be added to the floating window detection. In fact, I don’t think the window you are describing should be floating, unless users explicitly set it to floating. On Tue, Aug 25, 2015 at 11:44 AM, Ingo Bürk ad...@airblader.de wrote: Hi Michael, I agree that there are better choices. On a side note, I noticed the other day that Google Hangout screen sharing opens a window to offer ending the screen share session with this very atom. That window definitely needs to float, though it's easy to argue that Chrome is at fault here and should use a more suitable atom. Either way, i3 doesn't claim to support this atom and that alone should cause applications to not rely on it and instead use a more suitable atom. Ingo Sent from TypeMail On Aug 25, 2015, at 17:40, Michael Stapelberg mich...@i3wm.org wrote: http://standards.freedesktop.org/wm-spec/1.3/ar01s05.html contains: _NET_WM_STATE_ABOVE indicates that the window should be on top of most windows (see the section called “Stacking order” for details). _NET_WM_STATE_BELOW indicates that the window should be below most windows (see the section called “Stacking order” for details). _NET_WM_STATE_ABOVE and _NET_WM_STATE_BELOW are mainly meant for user preferences and should not be used by applications e.g. for drawing attention to their dialogs (the Urgency hint should be used in that case, see the section called “Urgency”). From that, I don’t think using _NET_WM_STATE_ABOVE to make a window floating is the correct way. Taking a step back, why does the window need to be floating at all? i3 deliberately only makes dialog windows floating, and if your window is not a dialog window, it not being floating is working as intended. On Tue, Aug 25, 2015 at 5:21 PM, Kevin J jkev...@umbc.edu wrote: Hi everyone, GLFW has a window creation flag to make a window FLOATING, it uses _NET_WM_STATE_ABOVE to do this in x11_window.c. I have tried adding to the if statement in manage.c and the corresponding xmacro to atoms.xmacro, but it still doesn't open as a floating window. After adding this, GLFW's check in x11_init.c works, it didn't before, so it seems to be registered within i3 correctly, but the xcb_reply_contains_atom(state_reply, A__NET_WM_STATE_ABOVE) check still fails. Any idea why this could be happening? Additionally, if I do get it working, would this be something worthy of submitting? or should GLFW be changed to use something other than the br WM_STATE_ABOVE atom to make floating windows? ...although none of the tests used by i3 seem to be the right fit. Thanks, Kevin -- Best regards, Michael
Re: [i3] GLFW_FLOATING window
http://standards.freedesktop.org/wm-spec/1.3/ar01s05.html contains: _NET_WM_STATE_ABOVE indicates that the window should be on top of most windows (see the section called “Stacking order” for details). _NET_WM_STATE_BELOW indicates that the window should be below most windows (see the section called “Stacking order” for details). _NET_WM_STATE_ABOVE and _NET_WM_STATE_BELOW are mainly meant for user preferences and should not be used by applications e.g. for drawing attention to their dialogs (the Urgency hint should be used in that case, see the section called “Urgency”). From that, I don’t think using _NET_WM_STATE_ABOVE to make a window floating is the correct way. Taking a step back, why does the window need to be floating at all? i3 deliberately only makes dialog windows floating, and if your window is not a dialog window, it not being floating is working as intended. On Tue, Aug 25, 2015 at 5:21 PM, Kevin J jkev...@umbc.edu wrote: Hi everyone, GLFW has a window creation flag to make a window FLOATING, it uses _NET_WM_STATE_ABOVE to do this in x11_window.c. I have tried adding to the if statement in manage.c and the corresponding xmacro to atoms.xmacro, but it still doesn't open as a floating window. After adding this, GLFW's check in x11_init.c works, it didn't before, so it seems to be registered within i3 correctly, but the xcb_reply_contains_atom(state_reply, A__NET_WM_STATE_ABOVE) check still fails. Any idea why this could be happening? Additionally, if I do get it working, would this be something worthy of submitting? or should GLFW be changed to use something other than the WM_STATE_ABOVE atom to make floating windows? ...although none of the tests used by i3 seem to be the right fit. Thanks, Kevin -- Best regards, Michael
Re: [i3] append layout works from commandline but not from .i3/config
On Tue, Aug 25, 2015 at 12:53 PM, i3.theg...@spamgourmet.com wrote: Hello Michael! Please don’t break threading in your replies, that makes it hard for people to follow the discussion. Ups, I'm sorry. It seems that using spamgourmet on the list might not be the best idea... I hope, the thread isn't broken this time...? It’s broken again at least in gmail, and you didn’t have a To: address set, which mailman didn’t like. Hope, that's in one line now: exec --no-startup-id i3-msg 'workspace $wsp3; append_layout /home/markus/.i3/emacs.json' See http://i3wm.org/docs/debugging.html for how to look at i3’s log. It should give you some more details about what’s going on. Now I had the opportunity to follow those instructions. This is the log: http://logs.i3wm.org/logs/5665370564198400.bz2 I had a look at it - but the data is a bit too much and I couldn't find any hint. Maybe you could help me? To remind you: the line mentioned above works fine when started from a terminal (without exec... of course), but when called from the config file, the placeholder for the window to the right of the emacs terminal is missing... Can you also provide the contents of /home/markus/.i3/emacs.json please? Also, a screenshot of the working/non-working version would be helpful. While you’re at it, please file this as a bug at https://github.com/i3/i3, so that we have all bugs in one place. Thanks. Thanks for your help! (And if the threading is broken again, I'll re-subscribe without spamgourmet) cu -- Markus Grunwald https://www.the-grue.de Fragen zur Mail? https://www.the-grue.de/mail_und_co https://www.the-grue.de/~markus/markus_grunwald.gpg -- Best regards, Michael
Re: [i3] Make disabling output config option
On Wed, Aug 19, 2015 at 10:08 PM, Andreas Herz a...@geekosphere.org wrote: FYI: i just had to put workspace 3: multimedia output DP-1 into my config, so the workspace is moved to that output when it's back. That sounds like a good solution to me. On 17/08/15 at 09:47, Andreas Herz wrote: With 4.10.3 this fix was introduced: https://github.com/i3/i3/commit/14e95e765eeb1fd103ee8821656b43bf69c5519d This makes total sense, but in some cases it might be annoying. I have a setup with 3 LCDs (all the same HP ZR24w) connected to an nvidia gpu. 2 LCDs are connected via DVI and the 3rd one is connected via DP. I let my workstation run 24/7 so i just turn the screens on/off. While the 2 LCDs on DVI are staying connected in the xrandr output when turned off, the LCD on DP is disconnected (althought still physical attached). So the workspaces from the 3rd LCD (DP) are moved to the other ones, so i have to move them back to the 3rd LCD everytime i get back home and turn the LCDs on again. So it might be an idea to add an option to disable this feature. I’m not convinced i3 is the right layer to introduce options for this. It sounds to me like your graphics driver incorrectly detects a display as disconnected when you are using DisplayPort and the display is turned off. Consider filing a bug against your graphics driver :). -- Best regards, Michael
Re: [i3] append layout works from commandline, (i3: to exclusive) but not from .i3/config
Please don’t break threading in your replies, that makes it hard for people to follow the discussion. On Tue, Aug 11, 2015 at 7:17 PM, i3.theg...@spamgourmet.com wrote: Hello Michael, What am I doing wrong? append_layout is a command, not a configuration directive. Just like the workspace command you are using a line above, you’ll need to use i3-msg to send it. Sorry, my fault: the statement above is in one line (the tickmarks might be a hint that's easily overlooked... Hope, that's in one line now: exec --no-startup-id i3-msg 'workspace $wsp3; append_layout /home/markus/.i3/emacs.json' See http://i3wm.org/docs/debugging.html for how to look at i3’s log. It should give you some more details about what’s going on. -- Markus Grunwald https://www.the-grue.de Fragen zur Mail? https://www.the-grue.de/mail_und_co https://www.the-grue.de/~markus/markus_grunwald.gpg -- Best regards, Michael
Re: [i3] append layout works from commandline, but not from .i3/config
On Tue, Aug 11, 2015 at 6:37 PM, i3.theg...@spamgourmet.com wrote: Hello, I have a layout stored in emacs.json (attached). When I run this command from the commandline, everything works fine: markus@haktar % i3-msg 'append_layout /home/markus/.i3/emacs.json' But when I run this command from .i3/config, one placeholder is missing: the one in the horizontal container next to emacs: exec --no-startup-id i3-msg 'workspace $wsp3; append_layout /home/markus/.i3/emacs.json' What am I doing wrong? append_layout is a command, not a configuration directive. Just like the workspace command you are using a line above, you’ll need to use i3-msg to send it. Thanks for your help, -- Markus Grunwald -- Best regards, Michael
Re: [i3] Reloading i3wm and saving layout
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 karol.lang...@gmail.com 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 eduncan...@gmail.com 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 mich...@i3wm.org wrote: Which version of i3 are you using? On Sat, Jul 4, 2015 at 6:34 AM, Eric Duncan eduncan...@gmail.com 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] i3 4.10.2 i3-save-tree perl module missing
On Thu, Jun 18, 2015 at 4:43 PM, Sargrad, Dave dave.sarg...@saabsensis.com wrote: 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) The error message mentions that you should install the AnyEvent::I3 module, and http://packages.ubuntu.com/search?suite=trustysearchon=nameskeywords=anyevent reveals libanyevent-i3-perl, so try installing that. The package http://packages.ubuntu.com/trusty/i3-wm also recommends libanyevent-i3-perl, so please don’t turn off the installation of recommended packages if you’re not willing to do this kind of digging yourself :). (@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. * -- Best regards, Michael
[i3] faq.i3wm.org logins via Google accounts broken
Hey, We’ve migrated faq.i3wm.org to a newer version of Askbot. Since about a week, OpenID (what was used for logins via Google accounts previously) is deprecated and developers should switch to the Google+ API. The update of Askbot was necessary in order to use the new API. However, the migration was everything but smooth. See the following FAQ post for details: https://faq.i3wm.org/question/5903/why-can-i-not-log-in-using-my-google-account/?answer=5904#post-id-5904 -- Best regards, Michael
Re: [i3] window assigned workspace and high cpu usage
It could be that the application in question is busylooping until it receives the MapNotify event. Perhaps for_window [class=Emacs] move to workspace 2, workspace 2, workspace back_and_forth works? (but it will flicker) If so, file a bug upstream with the application(s) in question. On Mon, Apr 27, 2015 at 7:48 PM, Antonio-M. Corbi Bellot antonio.co...@ua.es wrote: Hi all, I am currently using i3 version 4.10.2. Since a few months I've been observing a strange behaviour in i3 when I assign a window from emacs or chromium to a specific workspace. The behaviour I'm describing here was also the same with i3 4.[7,8,9].x. For example, I assign emacs to this key combination: bindsym $mod+Shift+m exec emacs And the workspace assignment is this: assign [class=Emacs] 2 Assuming I'm working in workspace 1, when I press $mod+Shift+m (I don't change to ws 2 for the moment), emacs starts in workspace 2 but I see an increment in cpu usage being the main culprits emacs (approx. 60% cpu usage) and xorg (approx. 90% cpu usage). And this cpu usage is sustained...it doesn't slow down until I change to workspace 2 ($mod+2) and then I observe that emacs hasn't finished starting and in the very moment I've changed to workspace 2 it is like it resumes execution and it finishes starting normally. It is then that cpu usage from xorg and emacs slow down to their normal values. I've also observed this behaviour with chromium, no other applications suffer from this 'strange' behaviour, i.e I use claws-mail in workspace 4 and it opens there without a glitch. Also I use glade (3.18.1) in this way, assigned to workspace 2, and it starts nicely. I'm not sure if it is an emacs/chromium bug or an i3 bug or even a xorg bug, but I've observed it only with i3 and these applications. Has anyone observed this? Antonio Corbi. -- Best regards, Michael
Re: [i3] i3 upgrade failure on trusty
sur5r, http://debian.sur5r.net/i3/dists/trusty/universe/binary-amd64/Packages indeed refers to v4.10.1, which is not in pool/ anymore. Could you take a look please? On Sat, Apr 18, 2015 at 8:04 PM, Jeff Bauer jeffru...@gmail.com wrote: Michael, Yes, apt-get update runs and completes without any problems. -Jeff On Sat, Apr 18, 2015 at 07:46:49PM +0200, Michael Stapelberg wrote: Did you try running apt-get update? On Sat, Apr 18, 2015 at 7:26 PM, Jeff Bauer [1]jeffru...@gmail.com wrote: Upgrade failure on Ubuntu 14.04: The following packages will be upgraded: i3 i3-wm 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 697 kB of archives. After this operation, 13.3 kB of additional disk space will be used. Do you want to continue? [Y/n] Err [2]http://debian.sur5r.net/i3/ trusty/universe i3 amd64 4.10.1-1~~trusty1 404 Not Found [IP: [3]217.8.49.41 80] Err [4]http://debian.sur5r.net/i3/ trusty/universe i3-wm amd64 4.10.1-1~~trusty1 404 Not Found [IP: [5]217.8.49.41 80] E: Failed to fetch [6] http://debian.sur5r.net/i3/pool/universe/i/i3-wm/i3_4.10.1-1~~tru sty1_amd64.deb 404 Not Found [IP: [7]217.8.49.41 80] E: Failed to fetch [8] http://debian.sur5r.net/i3/pool/universe/i/i3-wm/i3-wm_4.10.1-1~~ trusty1_amd64.deb 404 Not Found [IP: [9]217.8.49.41 80] Reviewing the [10]http://debian.sur5r.net/i3/pool/universe/i/i3-wm link, I see i3-wm_4.10.2-1~~trusty1_amd64.deb, but not i3-wm_4.10.1-1~~trusty1_amd64.deb. Best workaround? -Jeff -- Best regards, Michael References 1. mailto:jeffru...@gmail.com 2. http://debian.sur5r.net/i3/ 3. tel:217.8.49.41 80 4. http://debian.sur5r.net/i3/ 5. tel:217.8.49.41 80 6. http://debian.sur5r.net/i3/pool/universe/i/i3-wm/i3_4.10.1-1~~trusty1_amd64.deb 7. tel:217.8.49.41 80 8. http://debian.sur5r.net/i3/pool/universe/i/i3-wm/i3-wm_4.10.1-1~~trusty1_amd64.deb 9. tel:217.8.49.41 80 10. http://debian.sur5r.net/i3/pool/universe/i/i3-wm -- Best regards, Michael
Re: [i3] i3 upgrade failure on trusty
Did you try running apt-get update? On Sat, Apr 18, 2015 at 7:26 PM, Jeff Bauer jeffru...@gmail.com wrote: Upgrade failure on Ubuntu 14.04: The following packages will be upgraded: i3 i3-wm 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 697 kB of archives. After this operation, 13.3 kB of additional disk space will be used. Do you want to continue? [Y/n] Err http://debian.sur5r.net/i3/ trusty/universe i3 amd64 4.10.1-1~~trusty1 404 Not Found [IP: 217.8.49.41 80] Err http://debian.sur5r.net/i3/ trusty/universe i3-wm amd64 4.10.1-1~~trusty1 404 Not Found [IP: 217.8.49.41 80] E: Failed to fetch http://debian.sur5r.net/i3/pool/universe/i/i3-wm/i3_4.10.1-1~~trusty1_amd64.deb 404 Not Found [IP: 217.8.49.41 80] E: Failed to fetch http://debian.sur5r.net/i3/pool/universe/i/i3-wm/i3-wm_4.10.1-1~~trusty1_amd64.deb 404 Not Found [IP: 217.8.49.41 80] Reviewing the http://debian.sur5r.net/i3/pool/universe/i/i3-wm link, I see i3-wm_4.10.2-1~~trusty1_amd64.deb, but not i3-wm_4.10.1-1~~trusty1_amd64.deb. Best workaround? -Jeff -- Best regards, Michael
Re: [i3] Detecting screen locked
Yes, but also use -f (to follow child processes) and -s 2048 (to increase the size of strings) and -tt (to get timing). On Fri, Apr 17, 2015 at 9:23 AM, Jeff Abrahamson j...@purple.com wrote: Sure thing. Just to be clear, do you mean that instead of launching i3lock .. I substitute strace -o/tmp/i3lock-log-$(date +%s) i3lock ...? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ On 17 April 2015 at 09:19, Michael Stapelberg mich...@i3wm.org wrote: i3lock shouldn’t hang around. Can you start stracing all your i3lock instances automatically and provide the corresponding strace output of a hung instance in a bugreport? On Fri, Apr 17, 2015 at 9:04 AM, Jeff Abrahamson j...@purple.com wrote: I have a maintenance function that ought not bother spinning the CPU if the screen is locked. It checks this thus: if pidof i3lock /dev/null; then ... This is i3-specific, which is sad, but not a huge problem. What is a problem is that i3lock sometimes hangs around even though I think it should exit on unlock. And, indeed, most of the time it does exit on unlock. Once in a while, I find I have one or even several i3lock processes hanging around. I either lock my screen explicitly bindsym $mod+Control+L exec i3lock --dpms --inactivity-timeout 10 --color=220022 or else it's done by inactivity xautolock -detectsleep \ -time 3 -locker i3lock --dpms --color=220022 --inactivity-timeout 10 --nofork This question thus has two parts: 1. Am I doing something wrong that I sometimes have multiple i3lock instances? 2. Is there a better way to detect screen lock than pidof i3lock? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ -- Best regards, Michael -- Best regards, Michael
Re: [i3] Detecting screen locked
Ugh, then you’re running it in a setuid setup. You’ll need to start i3lock and then attach strace afterwards using -p. On Fri, Apr 17, 2015 at 9:56 AM, Jeff Abrahamson j...@purple.com wrote: I invoke i3lock at the commandline thus: [S-18]jeff@siegfried:gtd $ strace -o/tmp/i3lock-log-$(date +%s) -f -s 2048 -tt i3lock --dpms --inactivity-timeout 10 --color=220022 [S-18]jeff@siegfried:gtd $ and the result is that i3lock does not recognize my password. It does echo my typing, it just always says fail. I switch to a vt, login, and kill it. Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ On 17 April 2015 at 09:39, Michael Stapelberg mich...@i3wm.org wrote: Yes, but also use -f (to follow child processes) and -s 2048 (to increase the size of strings) and -tt (to get timing). On Fri, Apr 17, 2015 at 9:23 AM, Jeff Abrahamson j...@purple.com wrote: Sure thing. Just to be clear, do you mean that instead of launching i3lock .. I substitute strace -o/tmp/i3lock-log-$(date +%s) i3lock ...? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ On 17 April 2015 at 09:19, Michael Stapelberg mich...@i3wm.org wrote: i3lock shouldn’t hang around. Can you start stracing all your i3lock instances automatically and provide the corresponding strace output of a hung instance in a bugreport? On Fri, Apr 17, 2015 at 9:04 AM, Jeff Abrahamson j...@purple.com wrote: I have a maintenance function that ought not bother spinning the CPU if the screen is locked. It checks this thus: if pidof i3lock /dev/null; then ... This is i3-specific, which is sad, but not a huge problem. What is a problem is that i3lock sometimes hangs around even though I think it should exit on unlock. And, indeed, most of the time it does exit on unlock. Once in a while, I find I have one or even several i3lock processes hanging around. I either lock my screen explicitly bindsym $mod+Control+L exec i3lock --dpms --inactivity-timeout 10 --color=220022 or else it's done by inactivity xautolock -detectsleep \ -time 3 -locker i3lock --dpms --color=220022 --inactivity-timeout 10 --nofork This question thus has two parts: 1. Am I doing something wrong that I sometimes have multiple i3lock instances? 2. Is there a better way to detect screen lock than pidof i3lock? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ -- Best regards, Michael -- Best regards, Michael -- Best regards, Michael
Re: [i3] Detecting screen locked
See http://superuser.com/a/248127 for why setuid is ignored when running under strace. Given that you run i3lock on linux, it might be PAM which uses setuid in some of its modules. On Fri, Apr 17, 2015 at 1:20 AM, Jeff Abrahamson j...@purple.com wrote: Interesting. How does setuid have this effect on i3lock but only under strace? Any idea where the setuid is coming from or how to find out? The system is pretty vanilla ubuntu 14.10 (they have a good installer) aside from running i3 instead of gnome. The exec path that's visible once I'm logged in is lightdm - lightdm --sesion-child - i3. I see that i3 parents what is executed due to .xsessionrc. I'll try to gather traces with -p, but this will depend on me thinking to trace i3lock from a vt before unlocking the screen. My apologies in advance if I take a long time to catch the occasional errant process that way. And thanks for your ever prompt assistance and insights. Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ On 17 April 2015 at 10:09, Michael Stapelberg mich...@i3wm.org wrote: Ugh, then you’re running it in a setuid setup. You’ll need to start i3lock and then attach strace afterwards using -p. On Fri, Apr 17, 2015 at 9:56 AM, Jeff Abrahamson j...@purple.com wrote: I invoke i3lock at the commandline thus: [S-18]jeff@siegfried:gtd $ strace -o/tmp/i3lock-log-$(date +%s) -f -s 2048 -tt i3lock --dpms --inactivity-timeout 10 --color=220022 [S-18]jeff@siegfried:gtd $ and the result is that i3lock does not recognize my password. It does echo my typing, it just always says fail. I switch to a vt, login, and kill it. Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ On 17 April 2015 at 09:39, Michael Stapelberg mich...@i3wm.org wrote: Yes, but also use -f (to follow child processes) and -s 2048 (to increase the size of strings) and -tt (to get timing). On Fri, Apr 17, 2015 at 9:23 AM, Jeff Abrahamson j...@purple.com wrote: Sure thing. Just to be clear, do you mean that instead of launching i3lock .. I substitute strace -o/tmp/i3lock-log-$(date +%s) i3lock ...? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ On 17 April 2015 at 09:19, Michael Stapelberg mich...@i3wm.org wrote: i3lock shouldn’t hang around. Can you start stracing all your i3lock instances automatically and provide the corresponding strace output of a hung instance in a bugreport? On Fri, Apr 17, 2015 at 9:04 AM, Jeff Abrahamson j...@purple.com wrote: I have a maintenance function that ought not bother spinning the CPU if the screen is locked. It checks this thus: if pidof i3lock /dev/null; then ... This is i3-specific, which is sad, but not a huge problem. What is a problem is that i3lock sometimes hangs around even though I think it should exit on unlock. And, indeed, most of the time it does exit on unlock. Once in a while, I find I have one or even several i3lock processes hanging around. I either lock my screen explicitly bindsym $mod+Control+L exec i3lock --dpms --inactivity-timeout 10 --color=220022 or else it's done by inactivity xautolock -detectsleep \ -time 3 -locker i3lock --dpms --color=220022 --inactivity-timeout 10 --nofork This question thus has two parts: 1. Am I doing something wrong that I sometimes have multiple i3lock instances? 2. Is there a better way to detect screen lock than pidof i3lock? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ -- Best regards, Michael -- Best regards, Michael -- Best regards, Michael -- Best regards, Michael
Re: [i3] i3wm exit session
What’s the problem with this behavior? It surely is technically possible to avoid it, but why bother? On Sun, Apr 5, 2015 at 12:14 AM, Hector c1b3rh...@gmail.com wrote: Dear I3wm list , Recently I was using my laptop with i3wm, my version is 4.8 (2014-06-15, branch 4.8) I run debian testing, I couldn't say that I haven't fallen in love with it,but checking the option to exit from my current session if I press once, I get the normal message set by the default configuration, but if I press many times $mod+Shift+e I get something like in the attached picture. Is there any way to add some snipe of code to solve it if I press many times?. Can anybody confirm this behavior maybe I'm wrong and it just happend to me. Best Regards, Hector. -- Best regards, Michael
Re: [i3] Bug: Window fails to focus after closing matplotlib plot
The mailing list is not a bugtracker. Please report an issue at https://github.com/i3/i3/issues. And upgrade to v4.10.1 first, as we only support the latest major release. On Sun, Apr 5, 2015 at 9:22 AM, Jeff Abrahamson j...@purple.com wrote: I run ipython3, plot something using matplotlib and the Tk backend (default backend, I think), the plot displays. This is normal python. I type C-w to close the plot window, it closes, but the window now displayed (correctly) does not have the focus. Worse, i3 doesn't notice me either. Clicking in the window I think should be active or moving the mouse to trigger a crossing event focuses a window and all is back to normal. This doesn't happen with other windows/programs. I am using i3 4.8. [S-20]jeff@nantes:~ $ i3 --version i3 version 4.8 (2014-06-15, branch 4.8) © 2009-2014 Michael Stapelberg and contributors [S-20]jeff@nantes:~ $ Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ -- Best regards, Michael
Re: [i3] Split-Views in Tabs: Display Window Titles, not process name
Technically, what you want is easily achieved. The relevant code is con_get_tree_representation() in src/con.c. However, I’m not convinced using the window titles makes sense. Titles very quickly exceed the screen space you have in a tabbed container, so keeping the description as short as possible makes it more useful. Personally, I am typically interested in the full window titles, which is why I use stacked mode instead of tabbed mode. On Fri, Mar 20, 2015 at 5:07 PM, Stefano Ghirlanda dr.ghirla...@gmail.com wrote: I was also thinking the same thing a few days ago! It would be a useful feature. S On Fri, Mar 20, 2015 at 12:01 PM, Eric Duncan eduncan...@gmail.com wrote: 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 -- Stefano Ghirlanda - www.intercult.su.se/~stefano - drghirlanda.com Full Professor of Psychology, Biology, and Anthropology, Brooklyn College Founder and Fellow, Stockholm University Centre for the Study of Cultural Evolution -- Best regards, Michael
Re: [i3] i3-discuss Digest, Vol 59, Issue 6
Please avoid using the digest mailing list feature, as it breaks threading, which is annoying for people who are trying to help you. Also, when talking about versions of software, _always_ include the copypasted output of what the program says, never say “latest” because that can mean a number of things (latest version available in your distribution, latest version announced on the website, latest version available in git, latest version in a specific branch…). status_chr has been introduced relatively recently and is not in any released version. I still think your version is not recent enough. On Fri, Mar 13, 2015 at 1:00 PM, Giuseppe Silletti sillet...@gmail.com wrote: Thank you for answers! I've check my version and it is the last one. I'll try to be more precise: I want to put in the i3bar icons that tell when the battery is charging or not for example. If in the battery section of the i3status.conf file I put status_chr for example, if I restart i3 this message appears: Error: status_command process exited unexpectedly (exit 1). That's it :) 2015-03-13 11:00 GMT+00:00 i3-discuss-requ...@i3.zekjur.net: 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. Problems with some attributes in i3 bar config file (Giuseppe Silletti) 2. Re: Problems with some attributes in i3 bar config file (Hector) 3. Re: Problems with some attributes in i3 bar config file (Michael Stapelberg) -- Message: 1 Date: Thu, 12 Mar 2015 22:21:25 + From: Giuseppe Silletti sillet...@gmail.com To: i3-discuss@i3.zekjur.net Subject: [i3] Problems with some attributes in i3 bar config file Message-ID: cabyv-pn2rcbxwtmaw0eavzapyf9csf3qu_9cx8g47hmzjsr...@mail.gmail.com Content-Type: text/plain; charset=utf-8 Hi everyone! I'm new on i3 and I'm having some problems with some attributes in i3 bar config file. For example the volume section doesn't appear, even if I've put it in the config file. Also, some attributes like status_chr of battery section make my bar having an error and not showing. Can someone help me please? -- next part -- An HTML attachment was scrubbed... URL: http://infra.in.zekjur.net/pipermail/i3-discuss/attachments/20150312/3853e330/attachment-0001.html -- Message: 2 Date: Thu, 12 Mar 2015 22:57:20 -0500 From: Hector c1b3rh...@gmail.com To: Discussions/Questions about the i3 window manager i3-discuss@i3.zekjur.net Subject: Re: [i3] Problems with some attributes in i3 bar config file Message-ID: 20150313035720.GA4723@D3v1l.PereiraSecTeam Content-Type: text/plain; charset=us-ascii Hi you could check the documentation of i3status to see if it's there any problem check with the default options of i3[1] also to help you, you need to be more specific or visit[2]. [1] http://i3wm.org/docs/userguide.html#_configuring_i3bar [2] https://faq.i3wm.org/questions/ Best Regards. On Thu, Mar 12, 2015 at 10:21:25PM +, Giuseppe Silletti wrote: Hi everyone! I'm new on i3 and I'm having some problems with some attributes in i3 bar config file. For example the volume section doesn't appear, even if I've put it in the config file. Also, some attributes like status_chr of battery section make my bar having an error and not showing. Can someone help me please? -- Message: 3 Date: Fri, 13 Mar 2015 08:35:38 +0100 From: Michael Stapelberg mich...@i3wm.org To: Discussions/Questions about the i3 window manager i3-discuss@i3.zekjur.net Subject: Re: [i3] Problems with some attributes in i3 bar config file Message-ID: CANnVG6=RG0bO885U5NXmKn_zGNWvdcZEdizrEjDOKBOP=ff...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 My first guess would be that the version of i3status you are having is too old. On Thu, Mar 12, 2015 at 11:21 PM, Giuseppe Silletti sillet...@gmail.com wrote: Hi everyone! I'm new on i3 and I'm having some problems with some attributes in i3 bar config file. For example the volume section doesn't appear, even if I've put it in the config file. Also, some attributes like status_chr of battery section make my bar having an error and not showing. Can someone help me please? -- Best regards, Michael -- Subject: Digest Footer ___ i3-discuss mailing list i3-discuss@i3.zekjur.net
Re: [i3] workspaces and multiple monitors
https://faq.i3wm.org/question/949/dont-share-workspaces-between-monitors/ On Thu, Mar 5, 2015 at 9:38 AM, Jeff Abrahamson j...@purple.com wrote: On my laptop I find it quite nice that workspaces are bound to monitors (outputs). My monitors have different sizes and often (presentations) different uses. On my desktop, I typically pair workspaces, and if I change the left one, I'm about to change the right one. Does i3 have native support for this? (I don't see it?) Or should I write a script that does both changes for me (not hard)? Or is there a better way? Thanks. Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ -- Best regards, Michael
Re: [i3] Call for testing: upcoming i3 4.9 release
Yes, we already spoke about it in this thread. On Wed, Feb 25, 2015 at 9:43 AM, David Coppa dco...@gmail.com wrote: On Sun, Feb 22, 2015 at 1:01 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Works great on FreeBSD thanks ! And on OpenBSD too. There's a new dependency on libxkbcommon, is it right? Cheers! David -- If you try a few times and give up, you'll never get there. But if you keep at it... There's a lot of problems in the world which can really be solved by applying two or three times the persistence that other people will. -- Stewart Nelson -- Best regards, Michael
Re: [i3] Call for testing: upcoming i3 4.9 release
Not that I know of. I might create a backport once 4.9 is actually released. On Sun, Feb 22, 2015 at 11:20 AM, Frank Haun f...@fhaun.de wrote: Michael Stapelberg mich...@i3wm.org writes: If you are not running a version of i3 built from the “next” branch, please upgrade and help us test :). Is there a quick solution to compile the latest i3 on debian/wheezy? | ../i3/src/bindings.c:11:33: fatal error: xkbcommon/xkbcommon.h: Datei | oder Verzeichnis nicht gefunden Seems xkbcommon is not available for wheezy and there is no backport. Frank -- Best regards, Michael
Re: [i3] Assign workspaces to outputs dynamically.
On Sat, Feb 21, 2015 at 11:40 AM, Layus layus...@gmail.com wrote: Hi, The configuration directive workspace 1 output DP1-1 seems to have no “command” counterpart. (i.e. i3-msg workspace 1 output DP1-1 creates a new workspace named “1 output DP1-1”) This means that I am unable to remap dynamically workspaces to outputs. Am I missing some option or should I fill a feature request/provide a patch ? It does, see http://i3wm.org/docs/userguide.html#_moving_containers_workspaces_to_randr_outputs @Serge: Thank you for your response. I have looked into autorandr, and it does indeed provide a postswitch hook. I have added some reconfiguration for i3 there (see my postswitch file https://gist.github.com/layus/89a6bb8feebe6c1f96d2) Regards, Layus Le 17/02/15 21:31, Serge van Ginderachter a écrit : 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 layus...@gmail.com 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 x output command to support multiple outputs in order of preference. for example, worspace 0 output(s) VGA1 eDP1 would place workspace 0 on the projector when available, and on eDP1 otherwise. Do you find this useful ? Layus. -- Best regards, Michael
Re: [i3] Code for titlebar borders
Are you aware of http://i3wm.org/docs/userguide.html#_border_style_for_new_windows, specifically something like “new_window pixel 4”? To answer your actual question: I think https://github.com/i3/i3/blob/fbe25297b7921c390bcdac846710667fc04569f8/src/con.c#L1130 is what you’re looking for. On Fri, Feb 20, 2015 at 5:16 PM, Bigby James bigby.ja...@dimthoughts.com wrote: Howdy-ha, all. This message is basically a rehash of a question I asked on the FAQ.[1] It didn't get any responses, so I'm just giving this list a shot to see if anyone can point me in the right direction. I'm looking for the portion of the i3 source code that controls the thickness (height) of the titlebar borders, in the hopes of increasing that thickness. The goal is to make the border slight thicker in order to make it more prominent, making it another indicator of the focus status of a window rather than a mere aesthetic supplement to the background color of the window's titlebar (although I also think it would look nice; it's not *just* a practical thing ;) ). I'm not much of a coder, so the closest related thing I've found that seems relevant is the following snippet from 'i3_source_root/src/x.c': /* 5: draw two unconnected horizontal lines in border color */ xcb_change_gc(conn, parent-pm_gc, XCB_GC_FOREGROUND, (uint32_t[]) {p-color-border}); Rect *dr = (con-deco_rect); int deco_diff_l = 2; int deco_diff_r = 2; if (parent-layout == L_TABBED) { if (TAILQ_PREV(con, nodes_head, nodes) != NULL) deco_diff_l = 0; if (TAILQ_NEXT(con, nodes) != NULL) deco_diff_r = 0; } xcb_segment_t segments[] = { {dr-x, dr-y, dr-x + dr-width - 1, dr-y}, {dr-x + deco_diff_l, dr-y + dr-height - 1, dr-x - deco_diff_r + dr-width - 1, dr-y + dr-height - 1}}; xcb_poly_segment(conn, parent-pixmap, parent-pm_gc, 2, segments); This mostly seems to control the position and padding of the border, but not its thickness/height, so I feel like it's the wrong place to look. If anyone can either correct me if I'm wrong or let me know where in the code to look, I'd appreciate it. Thanks for your time; take care. - Bigby [1]: https://faq.i3wm.org/question/5385/code-for-window-title-border/ -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams -- Best regards, Michael
Re: [i3] Assign workspaces to outputs dynamically.
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 layus...@gmail.com 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 se...@vanginderachter.be 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 layus...@gmail.com 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 x output command to support multiple outputs in order of preference. for example, worspace 0 output(s) VGA1 eDP1 would place workspace 0 on the projector when available, and on eDP1 otherwise. Do you find this useful ? Layus. -- Best regards, Michael
Re: [i3] I3 and emacs
See https://faq.i3wm.org/question/360/emacs-like-keybinding/ On Sat, Feb 21, 2015 at 8:45 AM, Jeff Abrahamson j...@purple.com wrote: I'd like to use I3 and emacs. I don't have a spare modifier key on my keyboard, so I'd like to use a prefix key. Maybe I missed it in the docs, in which case, please accept my apologies. (I've only just begun to look at the source.) 1. Is there support for this currently in I3? 2. If not, is there interest in a patch? Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255-- only if I'm in the UK http://jeff.purple.com/ http://blog.purple.com/jeff/ -- Best regards, Michael
[i3] Call for testing: upcoming i3 4.9 release
Hey, it’s been quite a while since the i3 4.8 release, so it’s time to do another release soon :). If you are not running a version of i3 built from the “next” branch, please upgrade and help us test :). You can check which version you are running by using i3 --moreversion. See also http://i3wm.org/docs/debugging.html To obtain a version built from “next”, check out http://i3wm.org/docs/repositories.html if you are using Debian or a derivative. For Arch Linux (and possibly others), install i3-git. In case you encounter any bug that wasn’t there in 4.8, please report it at https://github.com/i3/i3 I’m planning to release in a week from now, i.e. on 2015-02-28. Thanks! -- Best regards, Michael
Re: [i3] Code for titlebar borders
I see. But then you’ve been looking at the right thing all along. On Sat, Feb 21, 2015 at 7:48 PM, Bigby James bigby.ja...@dimthoughts.com wrote: On 02/21, Michael Stapelberg wrote: Are you aware of http://i3wm.org/docs/userguide.html#_border_style_for_new_windows, specifically something like “new_window pixel 4”? Yes I am. I'm referring to the two horizontal lines drawn across the top and bottom edges of the titlebar (affected by the border color setting), *not* the container frame (affected by the background color setting). Confusion no doubt arises from the fact that border has two distinct meanings in i3 parlance. -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams -- Best regards, Michael
[i3] All i3 git repositories are now on GitHub
Hey, For various reasons, I’d like to minimize the number of critical services I host (and the number of custom solutions for common tasks). Therefore, I’ve moved all i3 repositories to GitHub. Instead of submitting patches on cr.i3wm.org, please send a pull request for the corresponding repository on https://github.com/i3. http://bugs.i3wm.org is now a redirect to https://github.com/i3/i3/issues, and all existing tickets have been imported. I’ll keep the existing repository locations around as best-effort mirrors (which automatically pull from GitHub). All past reviews on cr.i3wm.org are kept so that history stays available. -- Best regards, Michael
[i3] Putting i3lock/i3status on github
Hey, For various reasons, I’d like to minimize the number of critical services I host (and the number of custom solutions for common tasks). Therefore, I’m moving the i3status and i3lock repositories to GitHub as a test to see how well it works for our workflow/community/… Instead of submitting patches for i3lock/i3status on cr.i3wm.org, please send a pull request on https://github.com/i3/i3lock and https://github.com/i3/i3status respectively. I’ve disabled issues and wikis, as we’ll keep those at the current locations for now. I’ll keep the existing repository locations around as best-effort mirrors (which automatically pull from GitHub). -- Best regards, Michael
Re: [i3] i3bar multi-monitor setup
On Sun, Nov 23, 2014 at 7:37 AM, Marco Hunsicker i...@hunsicker.de wrote: Hello Michael, Remove the fake-outputs option and the i3bar configuration will work. Thinking about it again, perhaps what you are looking for are the output names “fake-0”, “fake-1”, etc. Those are what i3bar will see when you use fake-outputs. After altering my i3 config to use the suggested names, it's working :) Thanks very much for your help! May I ask why you are opposed to officially support such configurations? In the FAQ one can find mention of the fakeoutputs option. IMHO the use case does not seem entirely esoteric. Well, ideally, things should just work out of the box, and you would not need that option at all, right? ;) The problem with fake-outputs is that it (just like Xinerama) circumvents RandR support in i3 entirely, meaning i3 will not react to disabling outputs (re-assigning workspaces to other outputs) or enabling new outputs (such as connecting a video projector). Those are significant problems, and I don’t want to support people actively breaking important parts of i3. I realize that one could argue that when people use it, it’s their own fault that other features break, but still, it’s not something I want to endorse in any way :). -- Best regards, Michael
Re: [i3] i3bar multi-monitor setup
On Fri, Nov 21, 2014 at 7:10 PM, Marco Hunsicker i...@hunsicker.de wrote: Hello Michael, thanks for your quick action. I'm running a somewhat unusual setup with 3 monitors in pivot mode. Total screen size is 3600x1920, but in order to be able to stretch my IDE across 2 monitors I'm using the fake-outputs option to form just 2 workspaces: fake-outputs 1200x1920+0+0,2400x1920+1200+0 This is the problem. There is a reason this option is not documented: it’s not supported and not intended to be used at all. It exists for our testsuite only. Remove the fake-outputs option and the i3bar configuration will work. Thinking about it again, perhaps what you are looking for are the output names “fake-0”, “fake-1”, etc. Those are what i3bar will see when you use fake-outputs. That's the answer I feared ;) I understand that this mode is not supported, but besides the i3bar glitch it works wonderful with said configuration and provides a great deal of flexibility with minimal effort. As I have a few applications that don't fit into just one workspace, having three independent workspaces would complicate application switching and especially startup. I guess the application switching could be solved with some scripting to keep workspaces in sync (or is there already support for this?). But at least Eclipse does not seem to be able restore a window configuration that has been split to different workspaces across sessions. Hm, maybe I could somehow automate the process of detaching and moving the different views as well. Still, would you be open to receive a patch to make i3bar work? I’ll definitely not accept a patch that makes i3bar use non-fake output names when using fake-outputs, as that defeats the entire purpose. But see above, maybe you can make use of the fake output names. Anyway, thanks much for your feedback and for supporting a very useful piece of software. Have a great weekend. Cheers, Marco -- Best regards, Michael
Re: [i3] i3bar multi-monitor setup
On Thu, Nov 20, 2014 at 3:50 PM, Marco Hunsicker i...@hunsicker.de wrote: Howdy, I have a question regarding the configuration of i3bar with multiple monitors. I'm running a somewhat unusual setup with 3 monitors in pivot mode. Total screen size is 3600x1920, but in order to be able to stretch my IDE across 2 monitors I'm using the fake-outputs option to form just 2 workspaces: fake-outputs 1200x1920+0+0,2400x1920+1200+0 This is the problem. There is a reason this option is not documented: it’s not supported and not intended to be used at all. It exists for our testsuite only. Remove the fake-outputs option and the i3bar configuration will work. This works really great for the most part, but duplicates the output of the i3bar configuration to a certain degree across the monitors. The date is displayed twice etc. That's why I wanted to use different i3bar instances for the different outputs. xrandr reveals: Screen 0: minimum 8 x 8, current 3600 x 1920, maximum 16384 x 16384 DVI-I-0 disconnected DVI-I-1 connected 1200x1920+1200+0 left [...] HDMI-0 connected 1200x1920+0+0 left [...] HDMI-1 disconnected DVI-D-0 connected 1200x1920+2400+0 left [...] So, HDMI-0 is the leftmost monitor. DVI-I-1 and DVI-D-0 are the 2 other monitors that form a single workspace. According to the documentation I was thinking that adding the output option to the bar section would limit i3bar to that output. But I can't get it to work. If I try to limit the output to just the leftmost output like this: bar { output HDMI-0 ... } the bar disappears completely! No matter what I tried, adding an output option always leaves me with i3bar disappearing! Am I doing something wrong? Or is this kind of setup not possible? I'm using i3 version 4.8 (2014-06-15, branch 4.8) running the Nvidia binary driver 340.58 on Debian Wheezy. If any further information is required, just let me know. Thanks in advance. Cheers, Marco -- Best regards, Michael
Re: [i3] memory display
Yeah, look at /proc/sys/vm/overcommit_memory and understand the pros/cons of that behavior :). Exactly this type of subtleties is why i3status is memory-agnostic. On Sun, Nov 16, 2014 at 8:43 PM, Sean Reifschneider j...@jafo.ca wrote: On 11/16/14 09:02, Michael Stapelberg wrote: I’d argue that you should disable swap entirely, so that the graphics application in question can detect an out of memory situation and It would be nice if it worked that way, but regretfully it does not. I don't know exactly what the situation is, but we had some servers that would have a process periodically run out of control on memory, and disabling swap made the problem worse if anything. To achieve this you probably need to tweak settings in /proc rather than just shut off swap. Sean -- Best regards, Michael
Re: [i3] Systray not shown after 4.8
On Fri, Nov 14, 2014 at 6:22 AM, avinash r nashp...@gmail.com wrote: Hi, After updating to i3 4.8 (4.8-34-gfa41ad7) I am not able to see the systray anymore. In my i3 config file, I have the following configuration for the Which was the last i3 version with which it worked? Did you only update i3 or also other software? bar: bar { status_command i3status -c ~/.i3/status.conf tray_output primary Try setting an output as primary explicitly with “xrandr --output LVDS1 --primary” (and possibly restarting i3 afterwards), or removing “tray_output primary”. } I have another laptop with same version of i3 running ubuntu where the systray works flawlessly. Any idea on how to fix this? PS: I had used i3blocks for the status command previously to this, which i removed before updating. Can this be causing the issue? i3blocks being the culprit sounds very unlikely. -- Best regards, Michael
Re: [i3] startup some apps on specified workspaces in stacked mode
On Tue, Nov 11, 2014 at 10:09 AM, Robert Bude i...@rupat.de wrote: Hi, my config is like the following: cat ~/.i3/config | tail -n 1 exec ~/bin/i3startup.sh cat ~/bin/i3startup.sh #!/bin/bash # execute some apps on specific workspaces i3-msg 'workspace 1; exec google-chrome; exec i3-sensible-terminal; layout stacked; workspace 1' Note that “exec” is not blocking, i.e. this will start google-chrome and then immediately continue the execution of commands. Your “layout stacked” will therefore be run when there are not yet any windows on the screen, I think. There is https://github.com/drbig/i3-exec-wait which works around this in a way that is possibly the most simple to implement with the script you currently have. However, I think the much cleaner solution is to use http://i3wm.org/docs/layout-saving.html, which was introduced with i3 v4.8. In the layout, you can specify placeholders in the correct layout (and much more) for chrome, your terminal, etc. Then, restore the layout file on the appropriate workspace in a script, much like the script you currently have, and start the appropriate applications. i3-msg 'workspace 2; exec pgadmin3; exec software/SoapUI-Pro-5.1.2/bin/soapui-pro.sh; layout stacked; workspace 1' i3-msg 'workspace 3; exec icedove; workspace 1' As you see i want on desktop 1: a terminal and google chrome stacked chrome and terminal opens in default layout (i also tried layout stacked before exec the apps.) the same behaviour on workspace 2. any hints ? Thanks Robert PS: here is the log grep 11.11.2014 09:51:44 - executing: ~/bin/i3startup.sh .i3/logfile -A 300 11.11.2014 09:51:44 - executing: ~/bin/i3startup.sh 11.11.2014 09:51:44 - Starting bar process: i3bar --bar_id=bar-0 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - executing: i3bar --bar_id=bar-0 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - Starting bar process: i3bar --bar_id=bar-1 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - executing: i3bar --bar_id=bar-1 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - handlers.c:handle_destroy_notify_event:526 - destroy notify for 0x00800056, 0x00800056 11.11.2014 09:51:44 - handlers.c:handle_unmap_notify_event:459 - UnmapNotify for 0x00800056 (received from 0x00800056), serial 629 11.11.2014 09:51:44 - Not a managed window, ignoring UnmapNotify event 11.11.2014 09:51:44 - handlers.c:handle_destroy_notify_event:526 - destroy notify for 0x00800057, 0x00800057 11.11.2014 09:51:44 - handlers.c:handle_unmap_notify_event:459 - UnmapNotify for 0x00800057 (received from 0x00800057), serial 638 11.11.2014 09:51:44 - Not a managed window, ignoring UnmapNotify event 11.11.2014 09:51:44 - ipc.c:ipc_new_client:994 - IPC: new client connected on fd 9 11.11.2014 09:51:44 - IPC: received: *workspace 1; exec google-chrome; exec i3-sensible-terminal; layout stacked; workspace 1* 11.11.2014 09:51:44 - commands_parser.c:parse_command:215 - COMMAND: *workspace 1; exec google-chrome; exec i3-sensible-terminal; layout stacked; workspace 1* 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_workspace_name:1013 - should switch to workspace 1 11.11.2014 09:51:44 - commands.c:maybe_back_and_forth:112 - This workspace is already focused. 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_exec:1356 - should execute google-chrome, no_startup_id = 0 11.11.2014 09:51:44 - startup id = i3/google-chrome/31929-2-assek-team_TIME92352682 11.11.2014 09:51:44 - executing: google-chrome 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_exec:1356 - should execute i3-sensible-terminal, no_startup_id = 0 11.11.2014 09:51:44 - startup id = i3/i3-sensible-terminal/31929-3-assek-team_TIME92352682 11.11.2014 09:51:44 - executing: i3-sensible-terminal 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_layout:1604 - changing layout to stacked (1) 11.11.2014 09:51:44 - con.c:con_set_layout:1232 - con_set_layout(0xe29f40, 1), con-type = 4 11.11.2014 09:51:44 - con.c:con_set_layout:1253 - Setting workspace_layout to 1 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_workspace_name:1013 - should switch to workspace 1 11.11.2014 09:51:44 - commands.c:maybe_back_and_forth:112 - This workspace is already focused. 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - tree.c:tree_render:511 - -- BEGIN RENDERING -- 11.11.2014 09:51:44 -
Re: [i3] startup some apps on specified workspaces in stacked mode
On Fri, Nov 14, 2014 at 2:35 AM, Robert Bude i...@rupat.de wrote: The Problem on Layout saving/loading is, that i have to edit the layouts everytime i change the startup of my session i have to save the layout, edit the layout, edit startup (to start new app oder remove some app Yeah, but these edits should be fairly simple. You may even be able to automate them. so for my feeling starting and building layout live is cleaner ;) after checkout the i3-exec-wait i tried to compile but it throws an error make gcc -Wall -g -lyajli3-exec-wait.c -o i3-exec-wait i3-exec-wait.c:19:28: fatal error: yajl/yajl_tree.h: Datei oder Verzeichnis nicht gefunden compilation terminated. make: *** [i3-exec-wait] Fehler 1 Install libyajl-dev (on Debian(-derived) distributions) hav checked out yajl and copied to the given place but another error is thrown make gcc -Wall -g -lyajli3-exec-wait.c -o i3-exec-wait In file included from i3-exec-wait.c:19:0: yajl/yajl_tree.h:34:25: fatal error: yajl_common.h: Datei oder Verzeichnis nicht gefunden compilation terminated. make: *** [i3-exec-wait] Fehler 1 any help were good thx to you On Fri, 14 Nov 2014 10:16:00 +0100, Michael Stapelberg mich...@i3wm.org wrote: On Tue, Nov 11, 2014 at 10:09 AM, Robert Bude i...@rupat.de wrote: Hi, my config is like the following: cat ~/.i3/config | tail -n 1 exec ~/bin/i3startup.sh cat ~/bin/i3startup.sh #!/bin/bash # execute some apps on specific workspaces i3-msg 'workspace 1; exec google-chrome; exec i3-sensible-terminal; layout stacked; workspace 1' Note that “exec” is not blocking, i.e. this will start google-chrome and then immediately continue the execution of commands. Your “layout stacked” will therefore be run when there are not yet any windows on the screen, I think. There is https://github.com/drbig/i3-exec-wait which works around this in a way that is possibly the most simple to implement with the script you currently have. However, I think the much cleaner solution is to use http://i3wm.org/docs/layout-saving.html, which was introduced with i3 v4.8. In the layout, you can specify placeholders in the correct layout (and much more) for chrome, your terminal, etc. Then, restore the layout file on the appropriate workspace in a script, much like the script you currently have, and start the appropriate applications. i3-msg 'workspace 2; exec pgadmin3; exec software/SoapUI-Pro-5.1.2/bin/soapui-pro.sh; layout stacked; workspace 1' i3-msg 'workspace 3; exec icedove; workspace 1' As you see i want on desktop 1: a terminal and google chrome stacked chrome and terminal opens in default layout (i also tried layout stacked before exec the apps.) the same behaviour on workspace 2. any hints ? Thanks Robert PS: here is the log grep 11.11.2014 09:51:44 - executing: ~/bin/i3startup.sh .i3/logfile -A 300 11.11.2014 09:51:44 - executing: ~/bin/i3startup.sh 11.11.2014 09:51:44 - Starting bar process: i3bar --bar_id=bar-0 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - executing: i3bar --bar_id=bar-0 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - Starting bar process: i3bar --bar_id=bar-1 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - executing: i3bar --bar_id=bar-1 --socket=/tmp/i3-rbu.IOOJHK/ipc-socket.31929 11.11.2014 09:51:44 - handlers.c:handle_destroy_notify_event:526 - destroy notify for 0x00800056, 0x00800056 11.11.2014 09:51:44 - handlers.c:handle_unmap_notify_event:459 - UnmapNotify for 0x00800056 (received from 0x00800056), serial 629 11.11.2014 09:51:44 - Not a managed window, ignoring UnmapNotify event 11.11.2014 09:51:44 - handlers.c:handle_destroy_notify_event:526 - destroy notify for 0x00800057, 0x00800057 11.11.2014 09:51:44 - handlers.c:handle_unmap_notify_event:459 - UnmapNotify for 0x00800057 (received from 0x00800057), serial 638 11.11.2014 09:51:44 - Not a managed window, ignoring UnmapNotify event 11.11.2014 09:51:44 - ipc.c:ipc_new_client:994 - IPC: new client connected on fd 9 11.11.2014 09:51:44 - IPC: received: *workspace 1; exec google-chrome; exec i3-sensible-terminal; layout stacked; workspace 1* 11.11.2014 09:51:44 - commands_parser.c:parse_command:215 - COMMAND: *workspace 1; exec google-chrome; exec i3-sensible-terminal; layout stacked; workspace 1* 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_workspace_name:1013 - should switch to workspace 1 11.11.2014 09:51:44 - commands.c:maybe_back_and_forth:112 - This workspace is already focused. 11.11.2014 09:51:44 - commands.c:cmd_criteria_init:266 - Initializing criteria, current_match = 0x6505c0 11.11.2014 09:51:44 - commands.c:cmd_exec:1356 - should execute google-chrome, no_startup_id = 0 11.11.2014 09:51:44 - startup id = i3/google-chrome/31929-2-assek
Re: [i3] i3 4.8 layout file hides my status bar and floating windows
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, 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
Re: [i3] i3-msg - move all/some workspaces to another output
Have you tried assigning the workspaces to VGA1? See http://i3wm.org/docs/userguide.html#workspace_screen. When the output is unavailable, workspaces get moved to another output, which in your case is LVDS1. On Tue, Oct 14, 2014 at 8:34 PM, Fabian Raetz fabian.ra...@gmail.com wrote: On Tue, Oct 14, 2014 at 10:55:07AM -0500, Bigby James wrote: On 10/14, Fabian Raetz wrote: Hi all, i am looking for a way to move all (or some) of my workspaces to another output. Something like in the following shell script would be nice: - #!/bin/sh WS=2 3 4 5 6 OUTPUT=VGA1 for W in $WS; do i3-msg move workspace $W to output $OUTPUT done - Is there an easy solution i have overseen? Regards, Fabian An active monitor *must* have a workspace on it, and a workspace only exists after being explicitly created. So you can't move all currently existing workspaces to another monitor simultaneously. You'd need to first create a new workspace on the current monitor, then move all the previously created ones to a new monitor. What you can also do is use xrandr to deactivate the current display, which (if you only have two monitors in total) will move all worskpaces to the only active monitor. It's probably worth explaining exactly why you'd want to do this, though, since needing to move everything to another monitor all at once really sounds like a scenario that could be avoided with proper planning. Sure. I am using i3wm on my Notebook which has a small screen resolution (1366x768). So it happens that i have most workspaces on a second output (VGA1). On the first output (LVDS1) is most of the time only workspace 1 and 10 active which shows xconsole/mutt/logs. Before i switch locations i detach the second output (VGA1) and all workspaces move to the first (LVDS1). Then i suspend. So far, so good. Now the problem i am trying to solve: When i resume and plug in a second monitor, i have to manually move all workspaces back to the second output which is a bit frustrating. This happens multiple times a day. I run a script whenever an output changes via an external tool, so i thought i could use the above snippet or something else to move all existing workspaces except 1 and 10 to the second output (VGA1). Any suggestions? Thanks for your time, Fabian -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams -- Best regards, Michael
Re: [i3] i3-msg - move all/some workspaces to another output
No, but there’s a ticket for that: http://bugs.i3wm.org/report/ticket/555 On Tue, Oct 14, 2014 at 9:11 PM, Fabian Raetz fabian.ra...@gmail.com wrote: On Tue, Oct 14, 2014 at 08:53:17PM +0200, Michael Stapelberg wrote: Have you tried assigning the workspaces to VGA1? See http://i3wm.org/docs/userguide.html#workspace_screen. When the output is unavailable, workspaces get moved to another output, which in your case is LVDS1. No, but i am using it right now and it works pretty well. Can i assign a workspace to two outputs like below? Just in case i will use my HDMI port some day :) workspace 2 output VGA1 workspace 2 output HDMI1 Anyway this solves my direct needs. i3 rocks!! Thanks, Fabian On Tue, Oct 14, 2014 at 8:34 PM, Fabian Raetz fabian.ra...@gmail.com wrote: On Tue, Oct 14, 2014 at 10:55:07AM -0500, Bigby James wrote: On 10/14, Fabian Raetz wrote: Hi all, i am looking for a way to move all (or some) of my workspaces to another output. Something like in the following shell script would be nice: - #!/bin/sh WS=2 3 4 5 6 OUTPUT=VGA1 for W in $WS; do i3-msg move workspace $W to output $OUTPUT done - Is there an easy solution i have overseen? Regards, Fabian An active monitor *must* have a workspace on it, and a workspace only exists after being explicitly created. So you can't move all currently existing workspaces to another monitor simultaneously. You'd need to first create a new workspace on the current monitor, then move all the previously created ones to a new monitor. What you can also do is use xrandr to deactivate the current display, which (if you only have two monitors in total) will move all worskpaces to the only active monitor. It's probably worth explaining exactly why you'd want to do this, though, since needing to move everything to another monitor all at once really sounds like a scenario that could be avoided with proper planning. Sure. I am using i3wm on my Notebook which has a small screen resolution (1366x768). So it happens that i have most workspaces on a second output (VGA1). On the first output (LVDS1) is most of the time only workspace 1 and 10 active which shows xconsole/mutt/logs. Before i switch locations i detach the second output (VGA1) and all workspaces move to the first (LVDS1). Then i suspend. So far, so good. Now the problem i am trying to solve: When i resume and plug in a second monitor, i have to manually move all workspaces back to the second output which is a bit frustrating. This happens multiple times a day. I run a script whenever an output changes via an external tool, so i thought i could use the above snippet or something else to move all existing workspaces except 1 and 10 to the second output (VGA1). Any suggestions? Thanks for your time, Fabian -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams -- Best regards, Michael -- Best regards, Michael
Re: [i3] How to move workspace by name to a given named output
On Mon, Sep 22, 2014 at 8:49 AM, Sargrad, Dave dave.sarg...@saabsensis.com wrote: 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 No — section 4 is about configuration, not about commands that you can send at runtime. 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. - -- Best regards, Michael
Re: [i3] Python save/append layout - toolbar auto-hide bug
If you can reproduce this, file a bugreport with the layout file you’re using at http://bugs.i3wm.org/ i3bar is placed in a dock container, perhaps in your situation the container type is not properly set up… On Mon, Sep 22, 2014 at 5:44 AM, Sargrad, Dave dave.sarg...@saabsensis.com wrote: 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. - -- Best regards, Michael
Re: [i3] i3-nagbar and keyboard
On Sun, Sep 21, 2014 at 6:20 AM, grubernd li...@mehrzweckraum.com wrote: On 2014-09-21 05:14, Tony Crisci wrote: Here you go: `bindsym $mod+Escape pkill i3-nagbar`. i have a better hack: sudo mv /usr/bin/i3-nagbar /usr/bin/i3-nagbar-no Yes, nobody likes nagbar. and here we have a misunderstanding. i like nagbar, because it would be a very elegant way of displaying dialogs inside the window manager without resorting to extra tools like dialog, ncurses, gtk, or whatever. Nagbar is meant to be a teaching tool for new users. ouch. see engineering below.. It appears when you have a syntax error in your config file or duplicate binding. It's there to warn you about the default key combination that exits the wm so you don't press it on accident for the first time. If your config file is free of errors, you should never see it. i am really glad that the designers of most software dont follow your line of thought. imagine all software would display funky big bars that *do not follow their own design paradigm* and force you to use a differnt interface than they usually do. One thing that I don't like about some desktop environments is that they are too talky. There is always something flashing in the corner or some popup notification that I don't care about on my screen. i3 is designed to be quiet. yes, and that's a good thing. i dont want i3 to talk more. but here's the thing: i3 already has a method to display user-initiated system dialogs, aka the nagbar, but they do not follow the general design paradigm of keyboard-centered control. and that is the thing i am trying to get across. i3 doesnt follow it's own rules. There is no other window manager meta information that needs to be displayed in nagbar other than config errors. This is good unix engineering. i dont know too much about good _unix_ engineering, but good engineering doesnt get in the way of the user and changes behaviour midway. mind: nagbar should nag. but in my opinion it should not be the only tool that requires a very specific type of hardware to be attached to the computer. that's all i am saying. It doesn’t require a mouse. You can just kill it. Or fix the error in your config file and run “i3 reload”. Or (for the use case of exiting your session) run “i3 exit”, or just shut down your computer, or terminate the X session otherwise. There are plenty of alternatives, but they are not as convenient as just using nagbar when having a mouse attached. Similarly, i3 comes with a resize mode configured by default (keyboard shortcuts), yet resizing with a mouse is typically more convenient. i3’s line of thinking doesn’t dictate the keyboard as the one and only input device in all situations. We encourage you to use whichever input device is the most appropriate. For most window management operations, that’s clearly the keyboard, for resizing that’s most often the mouse, for nagging users that’s clearly the mouse :). Also note that nagbar is _not_ a generic tool to display dialogs that is well integrated into i3. Its purpose really is to nag you about config errors (so that you don’t nag us in our support channels) and before exiting a session accidentally. For the latter, you are expected to eventually change your config to bypass nagbar entirely. I don’t want to shut you up, but after this reply I don’t think there’s a lot to talk about anymore. I get that you don’t like the situation as-is, but the nagbar concept works very well for all other users that I’ve talked to, and it is very unlikely to change. cheers, grubernd -- Best regards, Michael
Re: [i3] i3-nagbar and keyboard
The nagbar should _nag_ you, and obviously it accomplishes its mission, since you are annoyed enough to write to this mailing list :). Read: this is intentional. On Sat, Sep 20, 2014 at 4:04 PM, grubernd li...@mehrzweckraum.com wrote: hi.. i found this a rather strange anachronism that the nagbar cant be navigated with the keyboard. or am i missing something here? is there a full HID support for i3-nagbar planned at some point? just for reference: since i am building a very simplified X11 enviroment only to be run occassionaly on top of a more or less automated headless box on simple hardware like raspberry pi or banana pi or similar: yes, i need and want to exit i3 without shutting down the box. also i want to get by with the least amount of extra tools. i have found an answer to what i am trying to do here: https://faq.i3wm.org/question/1262/exiting-i3-without-mouse-click/ but dmenu doesn't support mouse navigation, doh. so i ended up writing a quick python script with a tk yes/no box for this. still, the anachronism stands: having a WM with full keyboard support, except for the nagbar. cheers, grubernd -- Best regards, Michael
Re: [i3] i3 save/restore bug
This is a duplicate of http://bugs.i3wm.org/report/ticket/1297 On Tue, Sep 16, 2014 at 5:49 PM, Sargrad, Dave dave.sarg...@saabsensis.com wrote: Ok. I've dug further, and am sure that this is a problem with i3-save-tree. The containing workspace (container type = workspace) has some critical information that is stripped away by i3-save-tree. Specifically the workspace container structure (including the splitv layout) is lost as part of the pruning process. I can provide the entire tree associated with the workspace if that would help. But I think perhaps I've given enough detail to understand the issue. Please let me know if I should provide additional diagnostics. -Original Message- From: Sargrad, Dave Sent: Tuesday, September 16, 2014 11:09 AM To: i3-discuss@i3.zekjur.net Subject: 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
Re: [i3] i3-msg focus parent - odd error
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
Re: [i3] using i3-msg to close entire workspace
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
Re: [i3] probleme with i3
Hi emmanuel, Please always send emails to the mailing list. emmanuel kacou emmanuel.ka...@smile.ci writes: Hello , i have install i3 on my desktop but when i type the commande i3-input i got this error using format %s i3-input: Could not connect to i3: No such file or directory i precise that i have generated config file how can i resolve it thank you Which version of i3 is this? Please provide the output of i3 --moreversion -- Best regards, Michael
Re: [i3] restarting i3 when running inside Xephyr
On Fri, Aug 29, 2014 at 8:24 AM, Unmanifest D unmanife...@gmail.com wrote: Hi...I'm using i3 as a WM with Xephyr (as the Xserver). As I resize my main Xephyr window, I need to 'restart' i3 so that my applications resize themselves correctly. Is that expected or is it something else? That is expected. i3 uses RandR for all sorts of “the available outputs have changed” notifications, and nothing else. I think Xephyr does not provide RandR. Why do you use Xephyr in the first place? AIUI, Xephyr is intended to be used by developers to test their applications, not by end users running an actual window manager. From the i3 logs, it does appear that i3 is detecting a change in the size of the root window - I see a bunch of 'root geometry reply: (0, 0) X ' messages. But my applications, don't automatically resize, until I do an i3 restart. $ i3 -v i3 version 4.8-32-g1842dda (2014-07-24, branch master) © 2009-2014 Michael Stapelberg and contributors Thanks
Re: [i3] i3 colors on minimal x11
Hi grubernd, grubernd li...@mehrzweckraum.com writes: finally getting more playtime with i3. it behaves marvellously fast on a RaspberryPi with Arch Linux underneath. i try to build a very minimal system there, so i3 runs directly from .xinitrc and my .Xresources just contains two settings for xterm (locale and a font). I’ve noticed this on a Raspberry Pi as well. i3 only supports truecolor, so I suspect the graphics driver on the Raspberry Pi that you are using does not support truecolor. See also http://bugs.i3wm.org/report/ticket/434 -- Best regards, Michael
Re: [i3] Dynamically create placeholder
Hi Mateusz, Mateusz Poszwa o...@o2.pl writes: I think the „open” command is what you're looking for. I wonder why is it not documented… It’s not documented because it’s not intended for end users. There are most likely rendering glitches when using it. Its only use case is for the test suite. Using terminal windows as placeholders is the recommended way. I don’t think we should add something more tailored to your needs to i3. Why do you not just bind loading a placeholder-layout to a key and be done with it? -- Best regards, Michael
Re: [i3] Backported version [Was: Re: i3 wm problem.]
Hi Veljko, Veljko velj...@gmail.com writes: On 2014-Jul-29 09:23, Michael Stapelberg wrote: Also note that we have 4.8 in Debian, In Debian stable there is 4.2, but I'm using backported 4.7.2. Will 4.8 be available in backports repository? I just uploaded 4.8 to wheezy-backports. It should be available within a couple of hours. -- Best regards, Michael
Re: [i3] having trouble installing stable on ubuntu
Hi grubernd, grubernd li...@mehrzweckraum.com writes: maybe using ubuntu raring (13.04) isnt the ideal choice for the development version anymore - unless the website is outdated: http://i3wm.org/docs/repositories.html Updated it. Ubuntu releases too often, it’s impossible to keep up :p. Development versions are only available for the latest version of Ubuntu, which is raring at the moment. because that line was the reason i thought the update inside 13.04 would work in the first place. Note that the version you are using is _not_ the development version. You’re installing stable. Not sure why you read a paragraph about the development version and then deduce anything related to stable from that :). -- Best regards, Michael
Re: [i3] having trouble installing stable on ubuntu
Hi grubernd, grubernd li...@mehrzweckraum.com writes: Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: dunst libanyevent-i3-perl libanyevent-perl libcommon-sense-perl libjson-xs-perl libxcb-cursor0 libxcb-render-util0 libxdg-basedir1 Suggested packages: libasync-interrupt-perl libev-perl libevent-perl libguard-perl libio-async-perl libpoe-perl libtask-weaken-perl perl-tk Recommended packages: fonts-dejavu-core The following NEW packages will be installed: dunst libanyevent-i3-perl libanyevent-perl libcommon-sense-perl libjson-xs-perl libxcb-cursor0 libxcb-render-util0 libxdg-basedir1 The following packages will be upgraded: i3 i3-wm 2 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. Need to get 535 kB/1.433 kB of archives. After this operation, 1.636 kB of additional disk space will be used. Do you want to continue [Y/n]? WARNING: The following packages cannot be authenticated! libxcb-render-util0 libanyevent-perl libcommon-sense-perl libjson-xs-perl libanyevent-i3-perl libxdg-basedir1 dunst Install these packages without verification [y/N]? y Err http://at.archive.ubuntu.com/ubuntu/ raring/universe libanyevent-perl all 7.040-1 404 Not Found [IP: 83.164.133.196 80] Err http://at.archive.ubuntu.com/ubuntu/ raring/main libjson-xs-perl amd64 2.330-1 404 Not Found [IP: 83.164.133.196 80] Err http://at.archive.ubuntu.com/ubuntu/ raring/universe libanyevent-i3-perl all 0.12-1 404 Not Found [IP: 83.164.133.196 80] Err http://at.archive.ubuntu.com/ubuntu/ raring/universe dunst amd64 0.2.0-3 404 Not Found [IP: 83.164.133.196 80] Failed to fetch http://at.archive.ubuntu.com/ubuntu/pool/universe/liba/libanyevent-perl/libanyevent-perl_7.040-1_all.deb 404 Not Found [IP: 83.164.133.196 80] Failed to fetch http://at.archive.ubuntu.com/ubuntu/pool/main/libj/libjson-xs-perl/libjson-xs-perl_2.330-1_amd64.deb 404 Not Found [IP: 83.164.133.196 80] Failed to fetch http://at.archive.ubuntu.com/ubuntu/pool/universe/liba/libanyevent-i3-perl/libanyevent-i3-perl_0.12-1_all.deb 404 Not Found [IP: 83.164.133.196 80] Failed to fetch http://at.archive.ubuntu.com/ubuntu/pool/universe/d/dunst/dunst_0.2.0-3_amd64.deb 404 Not Found [IP: 83.164.133.196 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? That’s odd. Your system seems to be lacking the signing keys for the Ubuntu package sources. In addition (perhaps caused by that), your package lists seem outdated (which is why you get the 404s). I’d suggest deleting /var/lib/apt/lists/*, followed by apt-get update. If apt-get update complains, fix the signature problem. Get help about how to do that elsewhere please since that’s not an i3 problem. Afterwards, it should just work. -- Best regards, Michael
Re: [i3] having trouble installing stable on ubuntu
Hi grubernd, grubernd li...@mehrzweckraum.com writes: The following packages have been kept back: i3 i3-wm What does “apt-cache policy i3-wm” say? and the visual update-manager refuses to upgrade from un-authenticated sources. Why is the source unauthenticated? Did you not follow the instructions about installing the sur5r-keyring package? -- Best regards, Michael
Re: [i3] having trouble installing stable on ubuntu
[please don’t drop i3-discuss from cc when replying] Hi grubernd, grubernd li...@mehrzweckraum.com writes: i3-wm: Installed: 4.2-2 Candidate: 4.8-1raring1 That looks reasonable to me. Version table: 4.8-1raring1 0 500 http://debian.sur5r.net/i3/ raring/universe amd64 Packages *** 4.2-2 0 500 http://at.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages 100 /var/lib/dpkg/status Why is the source unauthenticated? Did you not follow the instructions about installing the sur5r-keyring package? i did, i followed the instructions by the letter. maybe because 4.2 was installed *before* i did that? That should not matter. What’s the output of “apt-get install i3-wm i3”? Also, what’s the output of “apt-get install i3-wm=4.8-1raring1”? -- Best regards, Michael
Re: [i3] Question about styling i3 scratchpad
Hi Charles, Charles Leifer colei...@gmail.com writes: I was wondering if there was any way to apply special styling to the scratchpad window? Special border, special title, whatever. Windows that are in the scratchpad are just floating windows. Therefore, you can apply the same styling to them as to any other floating window in terms of borders and color configuration. There is no way to distinguish windows that are in the scratchpad from other windows. -- Best regards, Michael
Re: [i3] Call for testing for the 4.8 release
Hi, Marius Muja mariusm...@gmail.com writes: I can confirm a focusing issue with intellij. I can reproduce it by doing Navigate - Line and when the editor jumps to some line I cannot type in although the window has focus. If I move the focus out and back in the cursor appears and I can type. We’ve been having issues with java for as long as the project lives. These are not new problems and hence not blocking the upcoming release. Thanks to everyone for testing, please update and continue testing so that we can release (this weekend probably) :). -- Best regards, Michael
Re: [i3] Call for testing for the 4.8 release
Hi Anders, Anders Aagaard aagaa...@gmail.com writes: Java focus issues isn't what I originally reported though. Me typing stuff and it ending up in a different (non Java) window is definitely a regression. You were mentioning IntelliJ as one of the windows, and IntelliJ is written in Java. Not sure how this is not java-related. In any case, try upgrading to the latest commit (8ece9950012e0a2d20db9d4d15bc3a3e30b96121 at the time of writing), that may fix the issue(s). -- Best regards, Michael
[i3] Call for testing for the 4.8 release
Hi, I want to release i3 v4.8 soon, so here is a call for testing. If you haven’t, please use an i3 build from the “next” git branch. For Debian and Ubuntu, we have http://i3wm.org/docs/repositories.html with that version so that you don’t need to compile it yourself. In case you notice a grave problem, please report a bug at http://bugs.i3wm.org/ as usual. If nothing shows up, I’ll make a release within the next few days. (FYI: This also means only urgent bugfix patches will be merged until the release is done.) -- Best regards, Michael
Re: [i3] Call for testing for the 4.8 release
Hi berenger, berenger.mo...@neutralite.org writes: Just to be sure, is the version 4.7.3-1+g4.7.2-189-g6fe44d81 the version you speak about? Just wanted to be sure, since unlike for Ubuntu there is only one repo. That’s exactly the one, yeah. -- Best regards, Michael
Re: [i3] Retina/HiDPI: Querying DPI
Hi Alexander, Alexander Berntsen alexan...@plaimi.net writes: the next release of i3 should behave correctly on Retina/HiDPI displays. It isn't already? Works fine here. What's wrong? I don't understand why i3 should care about PPI. No, it doesn’t work correctly in 4.7.2, the latest stable version: All pixel values, such as paddings, borders, etc., are designed for 96dpi displays and are not scaled up. E.g., for a 2 px window border, you need 5 px on a retina display to achieve the same physical width. I think the effect is very very easy to spot when comparing 4.7.2 with a build from the “next” branch. Once you restart into the new version, you’ll see how it just feels right again :). -- Best regards, Michael
Re: [i3] Google hangouts extension
Hi Anders, Anders Aagaard aagaa...@gmail.com writes: Alternately I could add some code to start sending events for con_set_urgency (since focus request that fails now sets an urgency), but it wouldn't be usable for my use case unless I also add a reason for the urgency change. Which I guess could be demands_attention/focus_request and wm_hints? Not sure about that last one, where it's really coming from ;). I think adding an event for urgency with the reason sounds reasonable. I have the tests working with nvidia 331.67. Can you be more specific about what breaks on your machine? It's an issue with glx, I've got an nvidia optimus setup, so I'm not terribly surprised. I could probably get it working fine by not loading glx, but it was easier to setup a VM for it. (I should point out it fails starting the X session, so it's not the test running part that's broken). It’d be good to fix that. We call Xdummy with -config /dev/null which is supposed to not use the system X11 config at all. If that has changed, it should be updated to continue running in an isolated-enough environment. -- Best regards, Michael
Re: [i3] Google hangouts extension
Hi Anders, Anders Aagaard aagaa...@gmail.com writes: Starting to implement the client side of this I realize it might be good to know the workspace of the window in question. That's easy enough to add. Also technically we could skip the changed field, as the focused field in the container will tell you the same information. I also wouldn't mind knowing the window class. Any technical reason that's not already in the Con class? It is — I think you’re not using the “next” branch, but you should. The “master” branch contains the latest release + bugfixes only, whereas development happens in “next”. On Tue, May 27, 2014 at 7:43 PM, Anders Aagaard aagaa...@gmail.com wrote: Sent a patch to http://cr.i3wm.org/patch/559 now. I unfortunately can't get the tests running. Trying to start up a x session with Xdummy seems to make the nvidia driver explode... I've done some manual testing and I really don't see how this could screw up anything else (.. famous last words I know). I have the tests working with nvidia 331.67. Can you be more specific about what breaks on your machine? -- Best regards, Michael
Re: [i3] Google hangouts extension
Hi Anders, Anders Aagaard aagaa...@gmail.com writes: I'l definitely check out that out. Do you think it would be worth it to add a IPC event for a denied focus request? I can have a go at making a pull request for it if you'd be interested, but it might be a bit of a corner case.. That sounds reasonable. That way, a third-party script can make the decision (based on arbitrarily complex rules) on what to focus. Submit patches at http://cr.i3wm.org/ :). -- Best regards, Michael
Re: [i3] Google hangouts extension
Hi Anders, Anders Aagaard aagaa...@gmail.com writes: Question 1: I regularly use multiple different screens (with different resolutions), I'd love to use for_window to lock the hangouts window to the lower right corner of my screen, but I can't really do this by px, as the resolutions will constantly change. Can I specify move position up 20px, left 20px, with the lower right corner as gravity somehow? Nope. You’ll need a custom script for that using the IPC interface, see http://build.i3wm.org/docs/ipc.html Question 2: Often when clicking on the extension (or a person in the chat) I'll have a window open with that content on another workspace. In those cases chrome will request that window gets focus, but since it's on another workspace I won't see that. Is there any option to either switch me to the workspace/move the window to the current workspace when a window requests focus? (.. and I do realize this option could be absolutely horrid if some random window has bad behavior and requests focus constantly.. :/ ) We intentionally disallow these kinds of focus requests for exactly the reason you cite in your last sentence. src/handlers.c:728 is the place in the code if you want to patch it yourself and see what happens in your setup. -- Best regards, Michael
Re: [i3] Questions regarding bindsym through ipc, tabbed layout, etc.
Hi Thomas, Thomas Sanchez thomas.san...@gmail.com writes: Have you considered generating a configfile and simply issuing the “reload” command? That is actually a good idea but would you consider then adding a directive like `source another_i3_config_file` ? It would also be nice to be able to get the current mapping configured. I think in terms of effects that is equivalent to alerting the configuration at runtime. I.e. it makes debugging equally harder and requires an equal amount of new commands. Given that it doesn’t establish as much as the other directive, I think it doesn’t make sense to be able to source another configuration file. Furthermore, I think that having a single path to read the configuration from is enough from i3’s point of view, and control over how this configuration should be concatenated/generated stays with the user. -- Best regards, Michael
Re: [i3] Questions regarding bindsym through ipc, tabbed layout, etc.
Hi Thomas, Thomas Sanchez thomas.san...@gmail.com writes: * Is there any rational for bindsym not being considered as any other command ? $ i3-msg 'bindsym Mod4+i exec gvim' ERROR: Your command: bindsym Mod4+i exec gvim ERROR: bindsym is not a command, it’s a configuration directive. Implementing a command to add new configuration lines to the current configuration is something I had planned for some time, but I’m not entirely sure it’s a good idea anymore. It’d kill the very clear current mapping from a configuration file on-disk to what i3 keeps in memory. I suppose we’d need a “dump current configuration” command at least. I wrote a set of script ( https://github.com/daedric/i3scripts ) to manage dynamic workspaces according to the project I'm working on. IMO it would make sense to be able to setup some specific binding. Thus, it would make also sense to be able to delete/replace a binding. Have you considered generating a configfile and simply issuing the “reload” command? * Why when I have a splitted workspace with say chromium and a terminal, I can't set the layout to tabbed (or stacked) for the terminal but I can split it ? Because the terminal is not a split container, it’s a leaf node. After you split it, you’ll be able to change the layout, but until you open more windows, you will not see any effects. See also http://www.youtube.com/watch?v=AWA8Pl57UBY for more details. * The following binding, does not show the i3-input on the focused output bindsym $mod+m exec i3-input -P Mark: -F mark %s There’s a bugreport for that: http://bugs.i3wm.org/report/ticket/1058 -- Best regards, Michael
Re: [i3] i3 not capturing key syms
Hi Tobias, Tobias Frilling tob...@frilling-online.de writes: So, does anybody have any idea how I can investigate this any further? I compared your xmodmap -pke output with mine, and it is different like this: (yours:) keycode 10 = 1 degree 1 degree onesuperior onesubscript ordfeminine NoSymbol notsign (mine:) keycode 10 = 1 degree onesuperior onesubscript ordfeminine NoSymbol notsign I’m using revision 2332 of the neo2 xmodmap file to load the layout. Maybe that makes a difference? Also, I’m unclear on whether you have any trouble _within_ i3 or just with i3-config-wizard. If the former: please provide a log, see http://i3wm.org/docs/debugging.html. If the latter: just don’t use i3-config-wizard for now? -- Best regards, Michael
Re: [i3] i3 not capturing key syms
Hi Tobias, Tobias Frilling tob...@frilling-online.de writes: Also, I’m unclear on whether you have any trouble _within_ i3 or just with i3-config-wizard. I'm having trouble within i3. I've got Mod4 as the leader for anything related to moving focus or spawning terminals, so this bug is a deal breaker. If the former: please provide a log, [...] http://codepad.org/HzRDvnkX I'm just starting i3 and pressing Mod4+Return a couple of times. In your logfile, in line 1009, the keybindings are re-grabbed, this time with the correct mapping (presumably you load your layout manually after starting i3). AFAICT, the mapping is correct: 2014-04-14 15:33:30 - config.c:translate_keysyms:156 - Translated symbol Return to 1 keycode […] 2014-04-14 15:33:30 - config.c:grab_keycode_for_binding:34 - Grabbing 36 with modifiers 64 (with mod_mask_lock 66) This is exactly the same line that I get in my log, and it works just fine for me. Are you sure that you have neither caps lock nor num lock pressed by accident? Also, what is the output of “xev” when you start it and press Mod4+Return? I also noticed that the Return keybinding in your “xmodmap -pke” output only has symbols for the first two layers: keycode 36 = Return NoSymbol Return Maybe try defining the upper layers too? For me it looks like this: keycode 36 = Return Return Return Return KP_Enter KP_Enter Return Return Also, maybe try this with a fresh user account, or booting from a live system? I am pretty sure this is a configuration problem of some sort, since there are many many i3 users with strange layouts and there were no bug reports like what you are reporting in the last couple of years. -- Best regards, Michael
Re: [i3] i3 not capturing key syms
Hi Tobias, Tobias Frilling tob...@frilling-online.de writes: I'm currently trying an alternative keyboard layout, Neo2, but I'm having trouble with i3. It seems like i3 isn't capturing any key syms, so no 'bindsym' is triggered. I use neo2 since many years, and all i3 features work perfectly fine for me. Here's the console output from i3-config-wizard for pressing Super_L, Return and a, once as it should be with keymap de, then broken with de-neo: […] Keypress 133, state raw = 16 sym = (0) Modifier keycode for Mod1: 0x40 Modifier keycode for Mod1: 0xcd Modifier keycode for Mod4: 0x85 This is Mod4! Modifier keycode for Mod4: 0x86 Modifier keycode for Mod4: 0xce Modifier keycode for Mod4: 0xcf Keypress 36, state raw = 16 sym = (0) Modifier keycode for Mod1: 0x40 Modifier keycode for Mod1: 0xcd Modifier keycode for Mod4: 0x85 Modifier keycode for Mod4: 0x86 Modifier keycode for Mod4: 0xce Modifier keycode for Mod4: 0xcf Keypress 38, state raw = 16 sym = (0) Modifier keycode for Mod1: 0x40 Modifier keycode for Mod1: 0xcd Modifier keycode for Mod4: 0x85 Modifier keycode for Mod4: 0x86 Modifier keycode for Mod4: 0xce Modifier keycode for Mod4: 0xcf So i3-config-wizard cannot translate the keysyms. This could be a bug in how i3-config-wizard works — keyboard handling in XCB is tricky. Can you test whether i3lock from git (it has to be the git version) works with neo2 for you? Also, which i3 version are you using? And can you append the output of xmodmap -pke? -- Best regards, Michael
Re: [i3] Tooltips etc. showing up on the wrong monitor
Hi Alexander, Alexander Berntsen alexan...@plaimi.net writes: [0] https://secure.plaimi.net/~alexander/tmp/2014-03-18-104845_5120x1600_scrot.png. [1] https://secure.plaimi.net/~alexander/tmp/2014-03-18-104847_5120x1600_scrot.png. The tooltip/popup you are showing in those screenshots are not managed windows, so i3 has nothing to do with them. You’ll need to look at the application in question and/or the toolkit that app uses to figure out what’s going on. -- Best regards, Michael
Re: [i3] [i3status] Update interval alignment glitch
Hi Marco, Marco Hunsicker i...@hunsicker.de writes: I think strategy 3, i.e. refreshing upon SIGUSR1, starting with the intervals from there and still aligning to minutes, sounds like the best option. But it's only a compromise if I understand the intention of the minute aligning correctly. Why is it a compromise? What is the intention behind the minute aligning? I thought it’s to have an update at the beginning of every minute, just as we align on full seconds. This will still be true with the proposed change. And in case people who use minute alignment don’t want to have updates during the minute, they should just not send SIGUSR1 to i3status, right? -- Best regards, Michael
Re: [i3] [i3status] Update interval alignment glitch
Hi Marco, Marco Hunsicker i...@hunsicker.de writes: I'm not sure as no one really explained it. From Gereon's comment regarding ugly numbers my guess is that the alignment should make sure that the refreshes happen in a deterministic way in order to display the time information in a consistent manner. 05s - 10s- 15s - 20s. You never see 01s 02s 03s 11s etc. I see. This will still be true with the proposed change. And in case people who use minute alignment don’t want to have updates during the minute, they should just not send SIGUSR1 to i3status, right? A bit prohibitive to my liking as the signal is very useful and I would rather find a solution that works for all use cases. But then I don't I’m not sure why you say that. No matter what you align on (e.g. 05, 10, 15, as you described), the signal will always _force_ an update right now. If you don’t want that, don’t send the signal. The next update after the signal should happen at the regular interval, i.e. as if the signal was not sent. Personally, I'm fine with the patch. But in order to cater for all needs, I would find a new configuration option worth thinking about. This would enable all parties to choose the policy which makes most sense to them. The new default could be to align only once, but users would be able to disable alignment or enforce it always. I don’t think adding a configuration option for this subtlety is worth it. -- Best regards, Michael
Re: [i3] [new feature proposition] Add an toggle mode for key binding.
Hi Taras, Taras Koroliuk taras.korol...@globallogic.com writes: For example I want to switch between two border styles (normal and 1pixel) for window by pressing one key combination. Proposal syntax for new addition: bindsym $mod+t border normal | border 1pixel What do you think about this? There already is the “border toggle” command. I don’t think there is much value in having a generic toggle command as you propose. The commands for which toggling makes sense already have toggling implemented. In case you need a more advanced toggle logic, you can always use the IPC interface: http://build.i3wm.org/docs/ipc.html -- Best regards, Michael
Re: [i3] KP_Return does not work
Hi berenger, berenger.mo...@neutralite.org writes: I tried to bind the keypad's enter key ( KP_Enter ) to the same command as the normal Return key, but it seems to only work with the number ( 0xff8d ), not with the name. Any idea why? Without a full debug log level logfile, it’s hard to tell. Can you please open a bugreport at http://bugs.i3wm.org/? -- Best regards, Michael
Re: [i3] [i3status] Update interval alignment glitch
Hi Marco, Marco Hunsicker i...@hunsicker.de writes: Would it not be more important to enforce that updates happen (roughly) every 'interval' seconds? Is it really that important to update at the start of a new minute anyway? I don’t understand why you are asking which behavior is more important. Can’t we fix this problem properly and have both? -- Best regards, Michael
Re: [i3] i3 related questions
Hi dharmin, Please direct questions like this to i3-discuss@ (cc'ed), not me personally. dharmin thakkar dharmi...@gmail.com writes: Here I am writing regards to how to setup i3 tiling window manager on my OS. Since I saw this i3 in my tutor's laptop when he was teaching, I have been trying for last few months on how to install this on my OS. But, there is no article or information available on internet as far as my searched went through about how to install i3 on various types of OS and what are the software requirements of the terminal Anyway, I have MacBook pro retina display one has OS 10.9 So could you please help me here with my questions.?? All I want to know in nutshell is if I have OSX 10.9 then what softwares or other OS do I need to run i3?? i3 only works on Linux. I recommend asking your tutor, as in-person help is very valuable and works much better than trying to help other people over the internet. Once you have Linux running on your machine and are somewhat accustomed to it, feel free to install i3 and try to get it running. Note that i3 is _NOT_ recommended for people who are just getting started with Linux. Our target audience is power users and programmers specifically. -- Best regards, Michael
Re: [i3] trying to build default layout at start
Hi, Instead of using sleep commands, why not try the new layout restore functionality we have in our git version? See http://thread.gmane.org/gmane.comp.window-managers.i3.general/1194 -- Best regards, Michael
Re: [i3] [i3status] Support min_width and align options in module definition
Hi Marco, Marco Hunsicker i...@hunsicker.de writes: when using the i3bar output format, I would find it convenient if I could set min_width and align right in a module definition. disk / { format = %avail min_width = 80 align = left } Would this be something worthwhile to add? Thanks. I think so, if you can do it in a sane patch. Also note that min_width supports not only integers, but also text. -- Best regards, Michael
Re: [i3] [i3status] Support min_width and align options in module definition
Hi Marco, Marco Hunsicker i...@hunsicker.de writes: Also note that min_width supports not only integers, but also text. Oh, I did not know that. What string values are to be supported? Is safe to parse them as integers? Thanks. It’s explained in the docs: http://i3wm.org/docs/i3bar-protocol.html -- Best regards, Michael
Re: [i3] [i3status] Don't display vertical separators
Hi Marco, Marco Hunsicker i...@hunsicker.de writes: It this something that sounds acceptable? Thanks. Yeah. -- Best regards, Michael