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 17393 - Cann't connect to vim after using C++ template wizard
Summary: Cann't connect to vim after using C++ template wizard
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: externaleditor (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-07 17:34 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 2001-11-07 17:34:11 UTC
Steps to reproduce:
1. Start ide with fresh user and set editor to vim
2. Select menu File=>New to bringup New WIzard window.
3. Expand C++/Class and select class.group to generate class.cc and class.h
files
Givm window comes up along with Note dialog which say "Waiting connection from
external editor". No like the time when open a normal file, this "Note" dialog
won't go
away itself. Click Cancel to close this dialog.  FIles "class.h" and "class.cc"
are loaded
into vim. But I can't open any file into vim. If I am in SDI mode, I can see
from this
point all the files I try to open are loaded to internal editor.

This problem won't show If I load any file to vim before I use New Wizard.

Netbean build : 20011081131(FD EA1) or 200110231011 (ifdef nightly)
vim:
/set/krakatoa_ea1/dist/ea1.10/sparc-S2/opt/SUNWspro/FD7/contrib/contrib7/vim6.0
Comment 1 David Weatherford 2001-12-07 00:14:15 UTC
The basic problem here is that the "Waiting for connection" dialog
does not go away automatically in this case.  This is a reproducible
testcase for a race condition:  If the external editor has already
connected before the dialog is displayed, the notification is lost
and the dialog must be dismissed manually, via the window manager's
Close button, *not* the Cancel button.  Using the Cancel button
cancels the operation and disables the externaleditor module (as
the text in the dialog clearly states).  This is why subsequent
Open actions invoked the internal editor.

I will leave this issue open to track the dialog-box race condition.

Comment 2 David Weatherford 2001-12-11 19:55:25 UTC
Eliminated the race condition.