AR# 13713


Project Navigator - Does the ISE Design Suite support the integration of third-party HDL text editors from within Project Navigator?


Does the ISE Design Suite support the integration of third-party editors from within Project Navigator?


To change the text editor preference in Project Navigator, select Edit -> Preferences -> Editor tab. 

In the Text Editor section of the dialog box, use the drop-down list to select the default editor to use in ISE Design Suite. ISE Design Suite includes built-in support for the following editors: Ultra Edit (PC), CodeWright (PC), and ISE Text Editor.  

NOTE: UltraEdit version 7.2 was used when selecting the command syntax.  Newer versions of UltraEdit require the "Custom" selection as shown below.

Select the "Custom" option to specify an editor of your choice.  

NOTE: Any editor you select must be included in your %PATH% unless the complete path to the editor is provided in the "Custom Editor" command line (e.g., {c:\program files\myedit\editwell.exe} $1). 

Spaces and back slashes should not be used in the directory path unless properly escaped. It is best to use curly braces as in the example above. 

Command Line Syntax 

When selecting a custom editor, you must enter the correct command line associated with the editor (if installed). 



GVIM 7+ - gvim --servername gvim_ise --remote-tab-silent +$2 $1 
Emacs - runemacs.exe $1 
WordPad - wordpad.exe $1 


VI - xterm -e vi +$2 $1 
GVIM 7+ - gvim --servername gvim_ise --remote-tab-silent +$2 $1 
Emacs - emacs $1 


  • You can also specify the path as part of the command line (for example {C:\windows\wordpad.exe} $1). The full path must be specified if the editor path is not specified in the PATH variable. 
  • If you want to use a different custom editor, refer to the editor documentation for the appropriate command line syntax. The command line syntax for several editors is listed below. 

When Project Navigator calls the specified editor, $1 is the file name and $2 is the line number if specified. 


ConTEXT.exe" $1 /g1:$2 -- (ConTEXT Editor)  

esview.exe $1 -line $2 -- (ESview) 

runemacs.exe +$2 $1 -- (Emacs) 

gnuclientw.exe +$2 $1 -- (Emacs using server) 

gvim --servername gvim_ise --remote-tab-silent +$2 $1 -- (GVIM 7) 

hdlauth.exe $1 -G$2 -- (HDL Author) 

TWriter.exe $1 -G$2 -- (HDL Turbo Writer) 

notepad.exe $1 -- (Notepad) 

txtpad32.exe $1($2)" -- (Textpad 3.2) 

textpad.exe $1($2) -- (Textpad 4.0) 

UltraEdit $1/$2 -- (UltraEdit - depending on version)  

Edit32 $1/$2 -- (UltraEdit - depending on version)  

VI - xterm -e vi +$2 $1 -- (VI) 

WinEdit.exe $1 -# $2 -- (WinEdit) 

wordpad.exe $1 -- (Wordpad) 


There are special considerations for spaces in the directory path to a custom editor. 

If the custom editor is installed in a location that has spaces in the path name, the path to the editor should be enclosed in curly braces. 

For example, the default installation path for UltraEdit is as follows: 

C:\Program Files\IDM Computer Solutions\UltraEdit-32\uedit32.exe 

The easiest way to handle this is to enclose the path in curly braces, as follows: 

{c:\Program Files\IDM Computer Solutions\UltraEdit-32\uedit32.exe}. 

Alternatively, you can escape all spaces and back slashes with a back slash as follows: 

C:\\Program\ Files\\IDM\ Computer\ Solutions\\UltraEdit-32\uedit32.exe 

Or, you can escape the spaces with a back slash and use forward slashes for directory separation: 

C:/Program\ Files/IDM\ Computer\ Solutions/UltraEdit-32/uedit32.exe



AR# 13713
日期 08/29/2014
状态 Active
Type 综合文章
Tools More Less
People Also Viewed