|
From: | martin rudalics |
Subject: | bug#10729: 24.0.93; On MS-Windows: emacsclientw.exe -n -c does create a new frame, but does not always display the requested file or the requested directory (24.0.92 does) |
Date: | Tue, 07 Feb 2012 08:53:32 +0100 |
> I don't really know why the set-buffer is required, because that code > only runs when (get-buffer-window next-buffer 0) has returned a window > (and server-window is nil, but that's irrelevant), and the call to > (select-window win) makes next-buffer the current-buffer. Perhaps > because it can be in another frame? A `set-buffer' can be needed if win is already selected but next-buffer is not the current buffer. Otherwise the subsequent (when filepos (server-goto-line-column filepos))) might do strange things. In any case this part should not be responsible for the behavior you see. >> When is it replaced? After exiting `server-switch-buffer'? > > When running it with edebug, yes. I haven't yet tested without edebug > (but it happens if you're not debugging, so the effect is real). I'm not used to working with Emacs as server. Could you try putting a breakpoint somewhere in set_window_buffer and get a backtrace there? I suspect the behavior is the result of some sort of window excursion but can't imagine why and how someone would wrap `server-switch-buffer' in such a thing. martin
[Prev in Thread] | Current Thread | [Next in Thread] |