This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 19157 - xemacs/gvim is disabled after load dbx debugger and restart netbean
Summary: xemacs/gvim is disabled after load dbx debugger and restart netbean
Status: RESOLVED WORKSFORME
Alias: None
Product: obsolete
Classification: Unclassified
Component: externaleditor (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-08 17:54 UTC by Sherry Zhou
Modified: 2002-07-19 15:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sherry Zhou 2002-01-08 17:54:33 UTC
xemacs and gvim :   /set/krakatoa/dist/sparc-S2/FD7/bin
  netbean version:   200112051230 , Release 3.3 Rc 1
                   ifdef:   /net/extend4/export/extend4d/ifdef/install/nb/bin


Steps to reproduce:
1. Start ifdef with new user. Set editor to xemacs (or gvim)
2. Load an excutable to dbx debugger. Everything looks fine at this point
3. Quit ifdef and xemacs and restart ifdef
4. xemacs is up with previouse file loaded. Meantime a Note window popup 
    asking to disable exnternal editor. This window blocks other actions.
5. Press Cancel in Note window. Now the editor is set to netbean editor. 
    But I can not open file to this editor neither.

Note: xemacs behaves correct if open file only .
Comment 1 David Weatherford 2002-03-17 01:52:01 UTC
I can't reproduce this bug.

I believe what happened was that a race condition (which has
been fixed) caused the "xemacs started" notification to be
missed, and the Note window to remain active.  It normally
goes away automatically once the external editor has started.
Closing the Note window via the Cancel button disabled the
externaleditor module, but did not restore the built-in editor's
window (issue 21199, recently fixed).

If you can reproduce this using the current FFJ build, please
re-open this issue.