71 lines
3.5 KiB
Plaintext
71 lines
3.5 KiB
Plaintext
\INCLUDE{site_header.txt}
|
|
|
|
This page provides a list of 4coder features for anyone trying to determine whether 4coder is the right editor for them. To find a complete list of every default key binding visit \LINK{document:bindings} binding list \END. If a feature is missing here you should check out the \LINK{document:roadmap} roadmap \END page to see what is coming in the future. If the feature you want is on neither, it might be missing from this list, or it might actually be missing from 4coder, you should contact \STYLE{code} editor@4coder.net \END to ask questions and make requests.
|
|
|
|
\SECTION{Text Editing}
|
|
\LIST
|
|
\ITEM Support for UTF8 encoded files
|
|
\ITEM Cursor-Mark editing paradigm
|
|
\ITEM Navigation by characters, words, tokens, lines, and blank lines
|
|
\ITEM Modern style undo and redo
|
|
\ITEM Incremental word complete with matching words in open files
|
|
\ITEM Incremental word search
|
|
\ITEM Word replace
|
|
\ITEM List all occurences of words in open buffers
|
|
\ITEM Clipboard history and "paste-next" to copy multiple chunks of text around easily
|
|
\END
|
|
\END
|
|
|
|
\SECTION{C/C++ Editing}
|
|
\LIST
|
|
\ITEM Code highlighting for C/C++ code
|
|
\ITEM Code auto-layout rendering engine
|
|
\ITEM Text level auto-indenting
|
|
\ITEM Run scripts and command line commands in editor
|
|
\ITEM Jump to error
|
|
\END
|
|
\END
|
|
|
|
\SECTION{Project Organization}
|
|
\LIST
|
|
\ITEM Set file extensions you care about in your project type to automatically open all code files
|
|
\ITEM Set shell/terminal commands to various fkeys for build scripts, test scripts etc
|
|
\ITEM project.4coder is a text file so it works painlessly with source control and can it is easy to start working with an existing project on a new machine
|
|
\END
|
|
\END
|
|
|
|
\SECTION{The Customization API}
|
|
These features are included in the alpha builds for supporters at the $5 tier and above.
|
|
\LIST
|
|
\ITEM Easy key rebinding
|
|
\ITEM Create custom commands
|
|
\ITEM Buffer reading and editing
|
|
\ITEM View opening, closing, positioning
|
|
\ITEM Access to the code intelligence engine
|
|
\ITEM Access to the clipboard
|
|
\END
|
|
\END
|
|
|
|
\SECTION{The Experimental Features}
|
|
These features are included in the alpha builds for supporters at the $10 tier and above and are generally only partially implemented, hence not being fully upgraded to the standard build.
|
|
\LIST
|
|
\ITEM Moving cursor and mark to surrounding and matching braces
|
|
\ITEM Rectangular delete
|
|
\ITEM Multi-line editing
|
|
\ITEM Rename a parameter
|
|
\ITEM Write in explicit enum values from 0 to n
|
|
\ITEM Scope aware features: scope navigation & scope absorb down
|
|
\END
|
|
\END
|
|
|
|
\SECTION{Transition From Emacs}
|
|
4coder's current setup and editing paradigm is modeled after emacs, so it is very natural to transition to 4coder from emacs for many users. 4coder customization is quite different from emacs though, so anyone who wants to keep their current keybinds will have to take the time to rewrite the keybinding code. Once the initial transition is done, any user who prefers C++ to Lisp will have a much better time in their 4coder configuration code.
|
|
\END
|
|
|
|
\SECTION{Transition From Vim}
|
|
For vim users the built-in editing paradigm will not line up with editing habits, but thanks to the open customization model, a vim paradigm and default vim key bindings can be used in 4coder. The vim customization \LINK{!https://github.com/Chronister/4vim} here \END is an early example of this with many basic vim systems up and running.
|
|
|
|
Right now 4coder is admittedly not great for vim users, but the transition path exists so keep your eyes on 4coder as better vim emulation is still on the way.
|
|
\END
|
|
|