Re: bump : *EDE Shell v2* buffer consecutively kills other windows content

Hi Eric,

 > ... you may need to start commenting out chunks of your .emacs file
 > to see what might be the cause.

Actually, I did that before settling down to post the issue here. The 
simplest init.el I get this problem with is just

(global-ede-mode 1)
(setq ede-project-directories t)
(require 'ede/proj-prog)

where probably the 2nd and 3rd line could also be dropped. Moreover, I 
get the issue with both, the ede version built into Emacs (ver. 24.3.1) 
and the one from bazar.
So I don't really know what other tools should interfere with EDE at 
that level.
Once again: using just this init.el, starting Emacs, opening some 
'main.cc' from a project, typing 'C-c . R' once, pops up an *EDE Shell 
v2* window, which splits the Emacs pane. Typing 'C-c . R' a 2nd time, 
will not reuse the *EDE Shell v2* window, but place another *EDE Shell 
v2* buffer into the window previously containing 'main.cc'.

Appending this

 > (defadvice pop-to-buffer (before cancel-other-window first)
 >      (when cancel-other-window (debug))
 >      (ad-set-arg 1 nil))

to the aforementioned three lines does not lead to the debugger or a 
stack trace showing up(?).

Any other idea?

Xaver

PS.: when you say
 > I haven't used that feature in a while, ....
do you imply that there are other, more preferred ways to run 
executables from within EDE?


On 10/13/2014 12:14 AM, Eric M. Ludlam wrote:
> Sorry for being slow to reply.
>
> I haven't used that feature in a while, but I looked through the code
> and I don't see anything that would make me think it would kill window
> content.
>
> There was a problem someone reported once with semantic-symref where it
> was killing other buffers.  It turned out that there was some other
> package installed on his Emacs that interacted with the buffer creation
> stuff semantic-symref was using that caused it.
>
> Your advice you listed in your reply below tells me that there are
> probably some hooks or advice in your emacs getting in the way.
>
> One option is to put something like this in the advice function below:
>
> (defadvice pop-to-buffer (before cancel-other-window first)
>      (when cancel-other-window (debug))
>      (ad-set-arg 1 nil))
>
> which will toss up the debugger when the window was being cancelled.
> That stack will hopefully show which other random tool might be involved.
>
> If not, you may need to start commenting out chunks of your .emacs file
> to see what might be the cause.
>
> Eric
>
> On 10/09/2014 11:57 AM, Xaver Gerster wrote:
>> Really no one out there having the same issue?
>>
>> In the meantime I found out, that putting this into my init.el seems to
>> be kind of a cure to the *EDE Shell v2* buffer stealing my other windows
>>
>> (defadvice pop-to-buffer (before cancel-other-window first)
>>     (ad-set-arg 1 nil))
>> (ad-activate 'pop-to-buffer)
>> (setq pop-up-windows nil)
>>
>> This is from Jérôme Radix @
>> http://stackoverflow.com/questions/812192/emacs-preventing-gud-pdb-from-controlling-windows/5175715#5175715
>>
>>
>> Yet, neither do I understand why this actually is of help, nor why it
>> should be needed for EDE after all, nor if it will mess with other parts
>> of Emacs (v. 24.3).
>>
>> Would anyone here have more insight?
>>
>>
>> On 10/08/2014 10:20 AM, Xaver Gerster wrote:
>>> Hi,
>>>
>>> I have an issue with the *EDE Shell v2* shell buffer: it kills my other
>>> windows content.
>>>
>>> When I run code using 'C-c . R' from within one of the project's
>>> modules, a new window on the Emacs frame pops up showing the output of
>>> the code in a 'Shell' major mode window. The corresponding buffer is
>>> named *EDE Shell v2*.
>>>
>>> My problem starts when I try to do this several times.
>>> Then, the output of the code will not remain within the window which
>>> popped up prior, but the *EDE Shell v2* buffer will consecutively
>>> replace the content of all windows previously displaying other buffers,
>>> until all of the Emacs frame is filled with windows displaying only the
>>> *EDE Shell v2* buffers.
>>>
>>> How can I force the *EDE Shell v2* buffer to display and update in only
>>> *one* window?
>>>
>>
>> ------------------------------------------------------------------------------
>>
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>
>> _______________________________________________
>> Cedet-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/cedet-devel
>>

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Cedet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cedet-devel