Sven Joachim <svenj...@gmx.de> 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".) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
