Your message dated Wed, 07 Jan 2009 17:59:16 +0100
with message-id <[email protected]>
and subject line Re: Bug#120160: WINDOWID equivalent for m-x shell?
has caused the Debian Bug report #120160,
regarding WINDOWID equivalent for m-x shell?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
120160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=120160
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21
Version: 21.1-5
Priority: wishlist
Could FRAME_X_WINDOW (f) get leaked (through some (x-* FRAME)
function), or even better, passed into the environment that a
M-x shell gets? (maybe use $WINDOWID like xterm does - would be
convenient for calling out to things like xwit; or maybe not.)
--- End Message ---
--- Begin Message ---
On 2009-01-07 17:45 +0100, Mark Eichin wrote:
> Sven Joachim <[email protected]> writes:
>
>> tags 120160 + moreinfo
>> thanks
>>
>> Hello Mark,
>>
>> I'm going through the list of old Emacs bugs in Debian. This one is a
>> bit mysterious to me.
>>
>> On 2001-11-19 04:50 +0100, Mark W. Eichin wrote:
>>
>>> Package: emacs21
>>> Version: 21.1-5
>>> Priority: wishlist
>>>
>>> Could FRAME_X_WINDOW (f) get leaked (through some (x-* FRAME)
>>> function), or even better, passed into the environment that a
>>> M-x shell gets? (maybe use $WINDOWID like xterm does - would be
>>> convenient for calling out to things like xwit; or maybe not.)
>>
>> Passing into the environment of a shell running under Emacs seems to be
>> wrong, since the frame where the shell buffer is displayed (if any) is
>> subject to change, and you cannot change the environment of subprocesses
>> after they are started. It's also not clear to me which problem you
>> want to solve. Could you elaborate?
>
> Hmm, that's a good point. And poking at frames in emacs22, it looks
> like I can get the window id with
>
> (frame-parameter nil 'outer-window-id)
>
> which is probably sufficient for whatever I was trying to do at the
> time, so you can go ahead and close this (since I have no interest in
> backporting the feature, just having it in "emacs".)
Actually, (frame-parameter nil 'outer-window-id) works in emacs21, so I
close the bug as you proposed.
Thanks,
Sven
--- End Message ---
