Re: [i3] New to i3wm

Martin, Ingo, Thanks for the suggestions, clarifications and welcoming! Cheers! 2015-04-05 23:17 GMT+02:00 Martin Cigorraga : > On Sun, Apr 5, 2015 at 5:22 PM, Ingo Bürk wrote: > > > > @Martin > > > > You're confusing a few things here. lifebar is a standalone bar. > > i3blocks, however, is not

Re: [i3] New to i3wm

2015-04-05 22:15 GMT+02:00 Martin Cigorraga : > Bienvenido! > > You might be as well interested in these projects too as they bring > extended usability to this babe: > [0] j4-dmenu-desktop: only shows applications that have a .destkop file; > also it is almost several times faster than traditiona

Re: [i3] New to i3wm

On Sun, Apr 5, 2015 at 5:22 PM, Ingo Bürk wrote: > > @Martin > > You're confusing a few things here. lifebar is a standalone bar. > i3blocks, however, is not a bar, but just a data provider for i3bar (so > it replaces i3status, not i3bar). This also means that "i3blocks has > tray support" doesn't

Re: [i3] New to i3wm

@Martin You're confusing a few things here. lifebar is a standalone bar. i3blocks, however, is not a bar, but just a data provider for i3bar (so it replaces i3status, not i3bar). This also means that "i3blocks has tray support" doesn't really make sense, because the tray support comes from i3bar,

Re: [i3] New to i3wm

Bienvenido! You might be as well interested in these projects too as they bring extended usability to this babe: [0] j4-dmenu-desktop: only shows applications that have a .destkop file; also it is almost several times faster than traditional dmenu (pops out almost instantly); [1] lifebar: a neat,

Re: [i3] i3wm exit session

Hi list, I just reported this issue not just because it bothers me, this was because in my daily usage I've never seen that behavior sorry if this issue is annoying for some developers, apologies. I think that i3wm is really a great piece of software that I've used in my everyday. I would like to

Re: [i3] i3wm exit session

This works bindsym Mod1+Shift+e exec "test -f /tmp/i3-nagbar$DISPLAY.lock || (touch /tmp/i3-nagbar$DISPLAY.lock && i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? This will end your X session.' -b 'Yes, exit i3' 'i3-msg exit' && rm /tmp/i3-nagbar$DISPLAY.lock

Re: [i3] i3wm exit session

The pidof solution also completely disregards the possibility of i3-nagbar being open for a completely different reason, e.g., a configuration error. In that case displaying both makes total sense. On 04/05/2015 06:50 PM, Michael Stapelberg wrote: > To expand a bit on my original post: I thought a

Re: [i3] i3wm exit session

To expand a bit on my original post: I thought about the pidof solution, but that will fail on multi-user systems or when you have a hanging/broken instance of i3-nagbar sticking around. Making this more robust is not as simple as one might think, and that’s why I wanted to clarify what the real p

Re: [i3] i3wm exit session

On 04/05, Tony Crisci wrote: > > Is there any way to add some snipe of code to solve it if I press many > times? > > Change the binding to this > > bindsym Mod1+Shift+e exec "pidof i3-nagbar || i3-nagbar -t warning -m > 'You pressed the exit shortcut. Do you really want to exit i3? This will > en

Re: [i3] i3wm exit session

On Sun, Apr 5, 2015 at 7:33 AM, Ingo Bürk wrote: > @Don > > Alright, then this was a misunderstanding. My apologies. Apology not necessary! Misunderstandings can happen due to problems on the output and/or input sides. Reading my message, I can see how you might have interpreted it as you did. /

Re: [i3] i3wm exit session

@Don Alright, then this was a misunderstanding. My apologies. Ingo On 04/05/2015 01:25 PM, Donald Allen wrote: > On Sun, Apr 5, 2015 at 7:15 AM, Ingo Bürk wrote: >> This is getting meta, but (in a general sense) this: >> >>> don't complain, send a patch >> is a pretty unhelpful reaction in my

Re: [i3] i3wm exit session

On Sun, Apr 5, 2015 at 7:15 AM, Ingo Bürk wrote: > This is getting meta, but (in a general sense) this: > >> don't complain, send a patch > > is a pretty unhelpful reaction in my eyes. So we can't open bugs if we > don't provide the fix as well? We can't ask for features without > implementing it?

Re: [i3] i3wm exit session

This is getting meta, but (in a general sense) this: > don't complain, send a patch is a pretty unhelpful reaction in my eyes. So we can't open bugs if we don't provide the fix as well? We can't ask for features without implementing it? Most of us are busy and to be honest, I don't have the time

Re: [i3] i3wm exit session

On Sun, Apr 5, 2015 at 3:39 AM, Jeff Abrahamson wrote: > (To be clear and before anyone has a chance to remark on it: that was meant > in support of the OP of the question, not meant as a chastisement of > Michael. Sorry if it read a bit as the latter.) Yes, it did read that way, pretty clearly.

[i3] New to i3wm

Oh dear...! I have had the misfortune of meeting i3 on my Easter holidays [?]. I have been a happy bunny playing with the configuration so it maps my (not so different) FVWM config and contributed to i3tree (it did

Re: [i3] i3wm exit session

> Is there any way to add some snipe of code to solve it if I press many times? Change the binding to this bindsym Mod1+Shift+e exec "pidof i3-nagbar || i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? This will end your X session.' -b 'Yes, exit i3' 'i3-msg

Re: [i3] i3wm exit session

(To be clear and before anyone has a chance to remark on it: that was meant in support of the OP of the question, not meant as a chastisement of Michael. Sorry if it read a bit as the latter.) Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255<-- only if I'm in the UK http://jeff.purple.com/

Re: [i3] i3wm exit session

Wait, that's not a very empathetic response. I agree with you, Michael, that this isn't a huge problem functionally, but it *looks* ugly and it *looks* like unintended behavior. And that's reason enough for the OP to raise the issue, in case no one had noticed. >From there, it's certainly reason

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 wrote: > I run ipython3, plot something using matplotlib and the Tk backend (

[i3] Bug: Window fails to focus after closing matplotlib plot

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

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 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

[i3] i3wm exit session

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