Source Insight Utility Configuration

1. Set the font Size options-document options, Find screen fonts and open the following interface to set the full-text font size

2. When adding Chinese annotation to the inside, the word spacing is very large. Here's how to fix it:

     1, Options->style Properties
    2, left style name below find comment Multi line, Comment, Comment right, Comment single line. Select "Pick ..." in the font name under the corresponding Font property box on the Set to Arial, regular, small four, OK, return to the style properties interface, size set to 12. (font size can be set according to your preferences and display size, of course, different places can be set to different styles of annotations)

2. Configure the keyword color. Click the menu Options->style Properties to set the style. In the default text style, Foreground color pick,rgb is filled with 0, 0,128. This dark blue is a little more comfortable than black. Similarly, the ref to local, the ref to Parameter,ref to Member,standard Object,standard property, is set to 128,128,128 Gray. Set the null Value,keyword,ref to Class,ref to Struct,ref to typedef,string to 0, 0,255. Set ref to Macro,ref to Const,ref to Enum,ref to Enumconst to 160, 0,160, and ref to method, ref to method, Proto,ref to Proto,ref to The color of the Func,standard function is set to 136,0,0 dark red, and the comment is set to 33,133,33 green.

3 . Fine- tune the color. If you see the keyword color does not meet your own requirements, on the keyword right-click on the pop-up menu has a style Properties, enter after the corresponding entry, you can set its style, usually color.

4 . Save. After you have satisfied yourself, go to style properties and click the Save button to save it and even save it to the web for next use and share with friends.

3. options->save Configuration

Application Tips

1. Show full path

Options->preferences->display, remove the tick "Trim long path names with ellipses" so that the ellipsis in the path is gone, showing the full path

With SI for several years, fragmented also accumulated a lot of experience, but always feel that there is still some content is not know, so today simply to a big sweep, all the options are studied once, and think of useful content in here to tidy up.

The main configuration of Si is in the options->perferences menu,

1. General

Project file Synchronization->remove missing file from project to avoid popping the error dialog box because the file cannot be found.

Remove the Misc->use stricter confirmation dialog option so that you do not enter "yes" when confirming.

2, Typing

Source editing->indent commands affect #-preprocessor statements. Once removed (the default), multiple lines of indentation do not affect the preprocessing statements (such as # If ... #endif).

Auto completion->use Detailed Completion window, when selected, the function details can appear when Lenovo. See:

Simple

More

Auto Completion->insert paremeters for functions, when removed, automatic Lenovo does not output the entire parameter to the current line.

Browsing in lists->match syllables while typing (slower). Whether a syllable match is used when retrieving symbols in the symbol list box, such as the function FindNext, which can be found by entering find or next. This feature may cause slow reaction (depending on the engineering and machine configuration) and is recommended to turn off because the feature can be dynamically enabled even in the closed state by entering a space and then entering a word.

Note Browsing in lists actually has two functions, but generally we can only see the match syllables while typing this one, should be SI menu design is not done well, resulting in Chinese windows can not display full, another feature is match Members while typing, used to turn on/off the ability to retrieve class/struct bodies by member variable name.

3. Files

Opening Files->sharing:let Other programs modify files, it is important to open the file in a shared manner, which ensures that the file can be edited simultaneously in other edits. The typical scenario is to use an IDE environment to dynamically compile and debug, while still reading with Si.

Customize ' Open ' Command ..., used to set Ctrl+o open page, the default option is Project File list view in Project Window, it is recommended to leave the default.

Saving Files->preserve undo data and revision marks after saving, if you cannot undo the discovery after saving, check that the option is selected.

Remove Extra white space when saving. Automatically strips the trailing spaces and tabs at the end of each line when saved. Recommended selection.

4, Languages

Custom syntax parsing for other programming languages, this ... Let's write another article.

Conditional parsing do not miss, the conditions function here is really let people like. What does conditions mean? In our code, there are generally some switch macros, by configuring the default values of these macros in conditions, you can let SI to be configured as non-open macros as invalid code, so that no symbolic retrieval.

If there are too many switch macros in the source code, you can also use scan files from condition parsing to find all the switch macros.

5. Symbol Lookups

Not too much of a special.

6. Display

Display configuration and personal preferences and the status of the display, I use x60 small, screen resources are limited, so in Display Elements Project window, Status Bar, Tool bar,clip window is closed, Basic shortcut keys can be used instead of them.

Options->horizontal scroll bars for each new window. Many masters have taught us to say that one line does not write too much code. Under this guideline, we don't need this stuff.

Show exact case of file names. If you don't like SI to capitalize all the filenames, tick this option.

Tile source and destination windows for source Link commands. The Source link is often used for parsing external command output results (such as make, lint), which automatically tiles the parsing results with the target window, which is useful.

Trim long path names with ellipses. This suggestion is not to be selected. In fact, this mainly affects the title bar, but generally the title bar on the space is ample, after the election will often make us do not know the exact location of the edited file.

7. Color

That's not much to say. How do you like to match it.

8, Syntax formatting

If we let people say that they like SI, I think grammar coloring will be one of them.

Basics->use only color formatting. Only the color-related settings in the style are enabled. Other such as bold, italic, shadow, etc. are not enabled.

Apply Styles for Lanugage Elements. Turn the category on style and choose it.

Symbol Reference lookups->qualify references to members. Detects the validity of a member and does not enable a style if it is not part of a class/struct. Although performance may be degraded, it is recommended to open it. Likewise qualify references to functions too.

Here is a button to access the Doc Types page (Options menu is also available), there are many important options:

In the Editing options,

Expand tabs, visible tabs can help us find and convert tab.

Show right margint and margin width can remind us whether to write a line too long.

The Symbol window option is recommended to close (because there are shortcut keys).

Auto Indent dialog box,

If you do not have a special preference, it is advisable to remove all two hooks from smart Indent options. At the same time, auto Indent type is selected smart.

9, Syntax Decorations

You can convert some symbols into a special form display, such as convert to →. If you want to use this feature, you cannot turn on syntax formatting->basics->use only color formatting.

The three functions under Auto annotations are more useful,

Show arrows at goto statements can display an up or down arrow on Goto, indicating whether to Goto or down. But let's try not to use Goto.

Annotate closing braces with end-statement. Displays the identity after "}", indicating which if/switch the "}" is paired with. The following annotate closing braces only for long blocks is a supplemental option, indicating that the identity is displayed only in the case of a longer block of statements.

10, searching

Nothing special, note automatically load selection into Find pattern.

11. Remote

Some options related to remote login. Can improve display performance for remote use.

12, Folders

It's nothing special.

Finally, the configuration file of Si is briefly introduced. You can import/export configurations by Options->load Configuration/save configuration, you can export them all, or you can export a few parts (such as style). Si configuration has two levels, one is the global configuration, one is the project configuration. Easy to access, unified a configuration is good, when you create a project, select the global configuration (the default value).

The import configuration can also be done by double-clicking the configuration file.

Set tab to 4 spaces

Add makefile, Kconfig, * to Sourceinsight. S file support

Everyone with source insight to see the Linux source code when all encountered such a trouble, Makefile and Kconfig in the text in search can not be found, this is because the source insight by default is not selected Makefile, There are no konfig files of this type. Let's talk about how to add Makefile: Open source Insight, before you create a new project, enter
Options--Document Options-> Click the drop-down box for document type and select Make File, and in the File filter on the right, add a semicolon after the original *.mak. That is, multiple different filtering rules are separated by semicolons, plus *makefile, become *.mak;*makefile, and include when adding to projects are selected, so that In the future when the new project (the current project synchronization under the makefile), you can identify makefile or makefile (as if the Source insight here is not case-sensitive). How to add Kconfig: Since Kconfig is a format that is not supported by the Sourceinsight default, we now want to add a type first.
Click Add Type, fill in the name of the new file type Kconfig,file filter is written in *kconfig, it is best to add kconfig* (because some kconfig in Linux appear in the form of kconfig.*), pay attention to the selection The following include when the adding to projects, so that the creation of a new file type, in the future when the new project to add files, the system will be able to identify the kconfig files. //===========================================

The function is defined with a compilation. Went to the internet to check, found that the reason is *. s file is not added to the modification project. 
in order to be able to search with source insight. s assembly file, you must add the file in. 
Method:
1, in the creation of the project before the special set up the source insight. Settings are as follows:
options->document options->doucment types-> Select x86 Assemble, and then enter * In the file filter on the right. S In this way, a new project is added, and when you add a file, you can put the * in the folder. S added in. 
2, if you have already created a good project, but also want to put *. s file to add in. as follows:
Open the created project, options->document options->doucment types-> Select x86 Assemble, and then enter * In the file filter on the right. S Then Project-->add and remove project files, and then re-add all the project's folders again so that you can put the *. s file added (note: The original *.c and other files will not be added repeatedly), and then re-rebuild on it.

Also, the SI default assembly file suffix does not support. s, so to support ARM's assembly file also needs to change the file filter.

Source Insight Utility Configuration