Set the default text editor in Ise to Gvim

Ise Windows edition, adding way

Under Ise, click Menu, Edit-Preferences, Editor. In the Editor Options box, select Custom, and in the command Line Syntax text box, type:
{D:\Program Files\vim\gvim.exe} +$2 $
Change the path to your own path, then note that there is a space in front of it, and there is a space in front of it, and the path is enclosed in curly braces.

Vivado Windows Edition, how to add

Remember to add Gvim:path=d:/program files/vim/vim74/to the environment variables

Click Tools, Options; Text Editor,custom Editor

D:/program files/vim/vim74/gvim.exe [file name] +[line number]

Refer to the following articles and list

Call UltraEdit Editor in Vivado

Under Ise, click Menu, Edit-Preferences, Editor. In the Editor Options box, select Custom, and in the command Line Syntax text box, enter: {C:/Program Files/notepad++/notepad++.exe} The curly braces {} is your notepad++. EXE path, where spaces are present in the path, plus braces; \ n equals the file name. then click OK. After clicking on a. v or. vhd file under Ise Engineering, or file compilation error, clicking on the wrong file will automatically call notepad++ to open the file. But unfortunately, this method does not achieve error highlighting location, that is, compile errors click Error files, pop-up notepad++ and cursor always appear in the first line of code, and can not quickly locate the wrong line, very inconvenient. And there's no Internet. The method of using notepad++ to implement error highlighting location =.=| | There is no way to self-pondering, referring to the online related methods, coupled with their own experiments, finally tried out.
The previous steps are the same as before, but you need to type in the command line Syntax text box: {C:/Program Files/notepad++/notepad++.exe} $1-n$2-n is notepad++, Represents the line number where the cursor is located after the file is opened; In this way, the ISE calls notepad++ and implements the error highlighting method to be completely implemented.

。 To change to: [File name]-l[line number]

First, the use of UE.

This paragraph is forwarded, written in quite detailed. Because in the big project, it is obviously more inconvenient to use the editor that comes with Ise.

1. Specify the UE as the default editor inside the ISE. Edit---Preferences open the property configuration, the left point editors, the right editor select UltraEdit again click OK, but sometimes this choice after double-clicking the vhdl file inside the project can not start the UE, If this is the case, you can choose the custom editor and then the command line syntax inside to enter {F:\Program FILES\IDM computer solutions\ultraedit-32\ Uedit32.exe} $1-l$2 curly braces are the path of the UE (because ISE requires that the directory cannot have spaces, so it needs to be enclosed in parentheses), it needs to be modified according to the different UE installation location, then click OK. This allows you to directly invoke your UE to edit the source file in the Ise.

2. Under the UE installation directory to see workfile.txt there is no VHDL keyword highlighting configuration, if not can be added from the online search wordfile inside, so that you can achieve the VHDL syntax highlighting.

3. Implement code folding and indentation. In general, the Wordfile file downloaded from the Internet in the VHDL part of only the keyword highlighting, you can use the following methods to achieve code folding and indentation:

To implement code folding:

/open Fold Strings = "(" "Begin" "If" "Loop" "Case" "Block" "Fold"
/close Fold Strings = ")" "End Process" "End If" "End Loop" "End Case" "End Block" "unfold"

To implement indentation:

/indent Strings = "Generate" "Entity" "Architecture" "Component" "Begin" "If" "Case" "elsif" "Else"
/unindent Strings = "End Generate" "End component" "End Arc" "Else" "elsif" "End Case" "End If" "End Process"

Add the above code to the VHDL section, you can also make changes according to your own needs.

4. Implement Modelsim to VHDL file compilation. The UE retains many application interfaces for the user, and the compiler can be linked to the UE. Because the usual project is to write good code first with Modelsim simulation, so choose to use Modelsim vcom program to compile VHDL files, I think this is a very good UE function.

First, you need to install the Modelsim on your computer, and the path value of the environment variable contains both MODELSIM and UE paths.

In the UE point menu bar, "Advanced"---"Toolbar configuration", in the "Command" tab, "menu item name" Inside for the added tool input name such as "VHDL compilation", the command line input vcom%f working directory inside the output%p. Select DOS Program and save active file in "options", "Output to list box" in "Output" tab. Click OK to close the settings. At this point, the "Advanced" menu bar will find that you set the "VHDL compilation" option, the option is followed by the shortcut key (shift+ctrl+0), so that after writing VHDL files can be in the UE through the shortcut key directly to the VHDL file compiled to find grammatical errors.

Note: Before you can use your UE to compile VHDL, you need to create a work directory within the folder where the source files are located. You can use the Windows DOS window to change the path to the working directory and then use the vlib work command to build.

If you use Verliog, you can follow the steps above to set it, but command-line input changes to vlog%f.

Set it up and start using it. Use ISE to establish a new project, add source files, double-click Source files using UE for code writing, open Modelsim to the project simulation, simulation found problems, after the UE to modify the code after the use of shortcut keys to compile, and then Modelsim inside restart re-simulation, until the completion of the function hehe, It's a lot faster than just using ISE.

Ii. use of vim (VI improvement)

Also select Custom, and then enter the following command line syntax:

{D:\Program Files\vim\vim73\gvim.exe}--remote-tab-silent +$2 $. Inside the parentheses is the path of the vim installation.

Vim Common Command Introduction

1. In the VIM installation directory, there is a VIMRC file, after opening, plus colorscheme darkblue This sentence, the default color scheme changed to Darkblue. Add the following two sentences at the back, you can solve the situation sometimes garbled.

Let &termencoding=&encoding
Set fileencodings=utf-8,gbk,ucs-bom,cp936
2.VIM default is normal mode, directly press I to go to input mode, and then press ESC and return to normal mode.

3. Start with "/", then you can enter the string you want to find directly, and then press N to look down in turn to "? "The input string after the beginning is also the beginning of the search, just press N to look forward from behind."

4. In addition to delete, press X to delete the letter where the cursor is located, and the uppercase X to delete the letter in front of the cursor. U is the undo operation, Ctrl+r is to undo the previous undo operation, a bit messy, try it yourself.

5. The uppercase ZZ is saved and launched: q! discard the changes and launch.

6. Enter gg=g in the command line mode, the entire code will be typeset, two times consecutive "=" to indent the line of the cursor, press n== to the cursor under the N-line indentation, according to the position of the previous line should be; shift+ greater than and less than to the left and right indent, press V to enter the visual mode, highlight a row , press ENTER to highlight down by row selection, and then indent the whole paragraph.

7.y$ is copied from the cursor to the end of the line.

Set the default text editor in Ise to Gvim