Why choose SlickEdit

The first is to be happy with the code, the nature of the work of the individual plus a lost hobby, the main working language is linux C, occasionally write a little python, usually need a lot of code to see the kernel, the project size is basically thousands of sources The file, the previous editor used source_insight, personally feel that si is really very easy to use, especially 4.0 support UTF8 is enough for daily use, but si has one of the biggest shortcomings, can not cross-platform. . . I tried running in the environment under wine, I feel that the compatibility is still not good. After the development environment is migrated to ubuntu, I took the vi, the operation of the full key is also cool, but it may be poor personal, I feel vi suitable for writing code. But when I analyze the code, I always feel worse. The vscode is also good, it is slow, so I want to find a cross-platform editor. After all, in case, if I use the MacBook code, slickedit this time. Into the field of vision, this editor features more than a little bit, personal choice is the pro version.
After the configuration is completed, the window layout is as shown in the figure below.

I feel that slickedit is really good, but I don’t know why, domestic forums and information are few and far between, most of them rely on their own groping, in order to share with everyone, configure The process is posted, if you are interested, you can discuss it together. I will post the link of the configuration file later, and the interested one can be directly exported.
First dark is a must, this is also a new addition to 2017slickedit
The following two items show whether there are rows and columns of drag and drop
Vertical line columns can display a vertical line at the number of columns you define

Binding shortcut
I added 5 new
are respectively
ctrl+, —>push-bookmark
ctrl+alt+,—>pop-bookmark
Alt+\ —> beautification
Alt+/—>Quick/Uncomment
Alt+d—>Quick doxygen annotation
Because slickedit's navigate does not support jumping in the same file, so when I analyze the code, I am used to push-bookmark first, then pop, I feel very good.
Write these first, then have time to add later