Switching from a certrain window 'A' back to emacs (via the default emacs
command) fails to return keyboard focus to emacs, despite emacs being the
(current-window). I don't really know which window, if any, has keyboard focus
at that point. Here's the definition of the default emacs command:
(defcommand emacs () ()
"Start emacs unless it is already running, in which case focus it."
(run-or-raise "emacs" '(:class "Emacs")))
This does not happen with any Window A. Window A is a (any) Matlab figure
window. Its (list-window-properties) is included below:
("_NET_FRAME_EXTENTS : 0, 0, 0, 0"
"_NET_WM_DESKTOP : 0" "WM_STATE : Normal"
"_NET_WM_ALLOWED_ACTIONS : _NET_WM_ACTION_CHANGE_DESKTOP,
_NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CLOSE"
"_NET_WM_WINDOW_TYPE : _NET_WM_WINDOW_TYPE_NORMAL"
"_MOTIF_WM_HINTS : (3 1 1 0 0)"
"_NET_WM_STATE : "
"WM_HINTS : (3 0 1 0 0 0 0 0 0)"
"_NET_WM_ICON : 48, 48, 4278190080, 4278190080, 4278190080,
4278190080, 4278190080, 4278190080, 4278190080, 4278190080, 4278190080,
4278190080, 4278190080, 4278190080, 4278190080..."
"_NET_WM_PID : 9188"
"WM_CLIENT_MACHINE : \"computer\""
"WM_PROTOCOLS : WM_TAKE_FOCUS, WM_DELETE_WINDOW"
"WM_CLASS : \"sun-awt-X11-XFramePeer\",
\"com-mathworks-util-PostVMInit\""
"WM_CLIENT_LEADER : WM_CLIENT_LEADER"
"_NET_WM_ICON_NAME : \"Figure 1\""
"WM_ICON_NAME : \"Figure 1\""
"_NET_WM_NAME : \"Figure 1\""
"WM_NAME : \"Figure 1\""
"WM_NORMAL_HINTS : (525 1079 48 560 475 0 0 0 0 0 0 0 0 0 0 0 0
1)")
I don't have time to track this bug down further, but it is annoying. This is
possibly related to another bug, in which raising a window within a split frame
that contains another window in the maximized state, does not raise it above
the maximed window.
Any ideas for tracking this down further?
Thanks,
Ernesto
stumpwm-devel-requ...@nongnu.org writes:
> Send Stumpwm-devel mailing list submissions to
> stumpwm-devel@nongnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
> or, via email, send a message with subject or body 'help' to
> stumpwm-devel-requ...@nongnu.org
>
> You can reach the person managing the list at
> stumpwm-devel-ow...@nongnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Stumpwm-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: [PATCH] Add ~/.stumpwm.d/config as an init-file option
> (Edward Trumbo)
> 2. Re: [PATCH] Add ~/.stumpwm.d/config as an init-file option
> (Stefan Reich?r)
> 3. Re: [PATCH] Add ~/.stumpwm.d/config as an init-file option
> (Edward Trumbo)
> 4. Re: [PATCH] Add ~/.stumpwm.d/config as an init-file option
> (David Bjergaard)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 04 Feb 2015 10:31:18 -0500
> From: Edward Trumbo <trum...@comcast.net>
> To: David Bjergaard <dbjerga...@gmail.com>
> Cc: stumpwm-devel@nongnu.org
> Subject: Re: [STUMP] [PATCH] Add ~/.stumpwm.d/config as an init-file
> option
> Message-ID: <87wq3xofqx....@comcast.net>
> Content-Type: text/plain
>
> Thanks for the quick acceptance! I'll update the wiki with some
> reference to the different init file styles soon, and I'll open an issue
> to discuss the manual.
>
> --
> Edward Trumbo
>
> "In Emacs Veritas."
>
>
> David Bjergaard <dbjerga...@gmail.com> writes:
>
>> Always drink more ;). I'm more than happy to merge patches too, its
>> just soo much easier with a PR. I was more referring to your suggestion
>> of adding the documentation to the manual/wiki. The wiki is super easy
>> to edit. The manual less so. At a minimum opening an issue with a
>> description of what needs to be added is enough.
>>
>> Cheers,
>>
>> Dave
>>
>> Edward Trumbo <trum...@comcast.net> writes:
>>
>>> Thank you. I've created a fork and pull request and I look forward to
>>> any discussion or its acceptance.
>>>
>>> Please be patient with me. Until yesterday my Git experience was limited
>>> to clones and pulls, and today I'm hip-deep in checkouts, forks,
>>> commits, and several other things I've already forgotten in the past
>>> hour. After confronting Git, I don't know whether to give up beer or
>>> drink more of it. ;-)
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 04 Feb 2015 16:37:04 +0100
> From: Stefan Reich?r <ste...@xsteve.at>
> To: Edward Trumbo <trum...@comcast.net>
> Cc: stumpwm-devel@nongnu.org
> Subject: Re: [STUMP] [PATCH] Add ~/.stumpwm.d/config as an init-file
> option
> Message-ID: <87zj8t4rj3....@xsteve.at>
> Content-Type: text/plain
>
> Hi Edward,
>
> do you have a pointer with the required steps for your pull request?
>
> Would be great to have this information (all needed git commands)
> somewhere in a visible place.
>
> I have some minor improvements for stumpwm. Would be nice to push them
> upstream as well ;-)
>
> Stefan.
>
>> Thanks for the quick acceptance! I'll update the wiki with some
>> reference to the different init file styles soon, and I'll open an issue
>> to discuss the manual.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 04 Feb 2015 10:49:31 -0500
> From: Edward Trumbo <trum...@comcast.net>
> To: Stefan Reich?r <ste...@xsteve.at>
> Cc: stumpwm-devel@nongnu.org
> Subject: Re: [STUMP] [PATCH] Add ~/.stumpwm.d/config as an init-file
> option
> Message-ID: <87r3u5oewk....@comcast.net>
> Content-Type: text/plain; charset=iso-8859-1
>
> Hi Stefan,
>
> I wish I could be more help, but everything I just did I pieced together
> from StumpWM's Info manual (Hacking/Using Git...) and Github's own help
> pages. In short, I'm not the right person to ask.
_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
