On Sat, Mar 09, 2013 at 10:24:13PM +0100, Markus Teich wrote:
> Am 09.03.2013 21:30, schrieb Andreas Amann:
> > On Mon, Mar 04, 2013 at 11:36:57AM +0100, Markus Teich wrote:
> >> Hi,
> >>
> >> a month ago i started using dwm.
> >> In my rules i s
On Mon, Mar 04, 2013 at 11:36:57AM +0100, Markus Teich wrote:
> Hi,
>
> a month ago i started using dwm.
> In my rules i send firefox clients to tag 2.
> Now, after starting dwm i am on tag 1 and after i started firefox via
> dmenu, i automatically get switched to tag 2.
Do you also get switched
On Tue, Feb 12, 2013 at 10:36:27AM +0100, Thomas Dean wrote:
> all the unwanted windows in the list. See the attached scripts. Does anyone
> know a solution for this? Is there an existing tool that lists all
> "visible" windows along with their id?
>
the ids of visible windows is stored in the _
On Thu, Dec 13, 2012 at 04:20:13PM -0500, Manolo MartÃnez wrote:
> Thanks a lot. I will give it a try. I have to ask: how you just come up
> with it, prompted by my question? If so, double thanks.
>
no, I like to go back deep into the focus history myself ;-)
I had previously posted the patch i
On Thu, Dec 13, 2012 at 03:04:01PM -0500, Manolo MartÃnez wrote:
> Hello,
>
> I was wondering if anyone knows of a patch that provides the means to
> return to the previously focused window (if it exists). That is, for
> example, if I'm
> on window1 and launch a window2, MOD+p (say) would take me
Here a patch which adjusts dwm to my personal taste, but maybe others find
it useful as well.
First, I missed a function in dwm which allows me to quickly go back in the
list of windows in the order in which they were focused. Dwm already records
the focus history, but there was no way to access
On Sun, Mar 25, 2012 at 07:47:36PM +0200, Swiatoslaw Gal wrote:
> > You could use the focused window instead (which was what you
> > originally asked about):
> >
> > $ xdotool getwindowfocus
> > 48234505
>
> Yes, this works fine (without any today's patches).
> But the very first answer: XGetInpu
On Sun, Mar 25, 2012 at 04:33:23PM +0300, Ivan Kanakarakis wrote:
> A quick look into the tip of dwm, shows that it is the case for dwm.
> It doesn't set the _NET_ACTIVE_WINDOW property correctly,
> although the atom is there, and included in _NET_SUPPORTED.
>
> To fix that, one must call (suppos
dwm does not always leave the fullscreen mode correctly.
For example, if you use the mouse to resize a fullscreen client, the boarder
does not get painted, which indicates that internally the isfullscreen flag
is still set. A similar effect happens if togglefloat (Alt-Shift-Space) is
applied to
On Sun, Jan 15, 2012 at 06:18:03PM +, Bjartur Thorlacius wrote:
> Should we not patch wmname?
>
As wmname is a hack for broken apps, they will probably break if you
try to fix it.
If you only need to set _NET_WM_NAME, you can also try
xprop -root -f _NET_WM_NAME 8s -set _NET_WM_NAME "LG3D"
On Sun, Jan 15, 2012 at 07:29:13AM +0100, Anselm R Garbe wrote:
> On 15 January 2012 07:27, Anselm R Garbe wrote:
> > On 15 January 2012 00:26, Ivan Kanakarakis wrote:
> >> On 15 January 2012 00:52, Andreas Amann wrote:
> >>> just to ask, do you happen to have the
On Mon, Jan 09, 2012 at 04:55:08PM +0200, Ivan Kanakarakis wrote:
> On 9 January 2012 16:34, Ivan Kanakarakis wrote:
>
>
>
> ow, sorry, cross that out. I misread the question.
> Even with the patch applied, the problem is still there.
> What I meant was, "nope, it doesn't fix it" .
> Sorry for
On Sun, Jan 08, 2012 at 01:50:35PM +0200, Ivan Kanakarakis wrote:
>
> The patch attached to Andreas responce does that
> and also adds support for _NET_CLIENT_LIST
Just to ask, does your other focus problem with Chromium still exist with
that patch applied?
Andreas
On Sun, Jan 08, 2012 at 12:29:38PM +0100, Anselm R Garbe wrote:
> On 8 January 2012 02:03, Andreas Amann wrote:
> >
> > I use the attached patch for this. In addition it also maintains a
> > NetClientList, which exposes the list of managed windows in the ewmh
> > recom
On Sat, Jan 07, 2012 at 10:20:27PM +0200, Ivan Kanakarakis wrote:
> dwm, when it receives a _NET_ACTIVE_WINDOW message, it transfers focus to
> the client that asked for it, but never sets the root window id to that
> window's id. That is ofcourse a choice - the standard doesn't force one to
> do t
> On Wed, 27 Apr 2011 13:55:08 +0200, Kurt Van Dijck
> wrote:
>
>> why not just:
>> dwm
>> kill $statuspid
>>
>> I see no use in backgrounding dwm, and then waiting for it.
>> What did I miss?
>
> Nothing; backgrounding dwm was left from trying a few other ways to do it.
> Thank you.
> T
On Fri, Apr 15, 2011 at 08:07:46AM +, Anselm R Garbe wrote:
>
> I think the approach has a multi-monitor flaw.
>
> The code should rather do:
>
> if(!ISVISIBLE(c)) {
> c->mon->seltags ^= 1;
> c->mon->tagset[c->mon->seltags] = c->tags;
> }
> detac
On Thu, Apr 14, 2011 at 07:21:57PM +0200, Anselm R Garbe wrote:
> I still don't like the fact to call view() with some Arg from within
> dwm, will need to improve this. Arg arguments were only intended for
> config.h, but I think we can improve this.
Maybe the patch below is useful for this?
Andr
On Wed, Apr 13, 2011 at 06:08:42PM -0400, Peter John Hartman wrote:
> On Wed, Apr 13, 2011 at 09:28:19PM +0100, Andreas Amann wrote:
> > WARNING: This e-mail has been altered by MIMEDefang. Following this
> > paragraph are indications of the actual changes made. For more
> &
On Fri, Apr 01, 2011 at 04:32:42PM +0200, pancake wrote:
> we can override those mimetypes to be text/plain so all browsers will
> display it correctly.
>
Or try
https://addons.mozilla.org/en-us/firefox/addon/open-in-browser/
Hi Evgeny,
On Tue, 12 Oct 2010 21:19:32 +0300, Evgeny Grablyk
wrote:
> If you have any comments or suggestions, please share - this is my
> first patch for dwm.
Works well for me. Note however that you cannot switch between tags per
mouse if an alternate layout is activated. The patch below fix
This recent patch
changeset: 1519:72272822ddf2
user:Anselm R Garbe
date:Sun May 30 10:02:56 2010 +0100
summary: implemented better fullscreen handling, please test
gives me troubles because the border around the window is not painted for
all clients. (One particular examp
On Thu, May 27, 2010 at 04:35:29PM +0200, orsch...@googlemail.com wrote:
> Ah sorry my fault, accidentally I broke the line down with \.
>
> Nice your solution is working. :)
>
> But do you have any idea why toggling via evdev doesn't affect the
> xkb_symbols line?
simply because "xkb_symbols" d
On Thu, May 27, 2010 at 03:25:32PM +0200, orsch...@googlemail.com wrote:
> Hello Andreas,
>
> your solution is almost working. The only thing that doesn't fit is
> the length of the output. de/pl should only by two letters but in the
> output there are a plenty of blanks before. I assume this happ
On Thu, May 27, 2010 at 12:49:59PM +0200, orsch...@googlemail.com wrote:
> Thanks for the hint Andreas. xset -q shows a difference between both
> values. I tried to implement it into my statusbar but as I'm not
> familiar with bash scripting it doesn't work. This is my trial:
>
> #set statusbar
>
On Thu, May 27, 2010 at 09:58:55AM +0100, Anselm R Garbe wrote:
> On 27 May 2010 09:54, wrote:
> > Oh dear how bad has my english to be since nobody is understanding me
> > right. *g*
> >
> > Well second approach. Currently I'm using the following code to
> > generate my statusbar:
> >
> > #set
> you may missunderstand my question.
>
> I'm looking for a possibility to display the used layout (in my case
> either de or pl) via xsetroot in the statusbar of dwm.
>
> Do you have any idea how to achieve that?
>
I also do not know of a direct way to read out the current layout. But here
is
On Wed, May 26, 2010 at 01:08:27AM +0200, orsch...@googlemail.com wrote:
> Sorry forgot to add a small request when we're already talking about this
> issue.
>
> Is there any way to display the currently used layout via xsetroot in
> statusbar?
>
I simply use something like
setxkbmap -option
> Whenever I use the polish layout this effect appears. The german layout on
> the other side still works fine.
>
> What could that be?
>
I had a similar problem when switching between uk <-> de layout. The reason
was that when the alternate second keyboard is active,
the bit 13 of XEvent->xbut
29 matches
Mail list logo
