xenia/kakoune
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc faq: Fix the prose

Browse Source
This commit is contained in:
Frank LENORMAND 2020-06-11 10:30:46 +03:00
parent 1761c4e059
commit 442aae1cef
1 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/pages/faq.asciidoc
View File

@ -10,9 +10,9 @@ but generally refers to a strike into which all of one's strength went.
=== Is there going to be a Windows port of Kakoune ? === Is there going to be a Windows port of Kakoune ?
As many features provided by UNIX systems would be missing, or albeit much As many features provided by UNIX systems are missing or less efficient on
less efficient, on a Windows system, the incentive to porting the project a Windows system, the incentive to porting the project to this operating
to this operating system is low. system is low.
Moreover, you can achieve pretty decent performance by using Kakoune on Moreover, you can achieve pretty decent performance by using Kakoune on
Cygwin (which is officially supported). Cygwin (which is officially supported).
@ -114,7 +114,7 @@ to a short time, e.g. 25ms: `set -sg escape-time 25`
As a fairly compliant follower of the UNIX philosophy, Kakoune does not As a fairly compliant follower of the UNIX philosophy, Kakoune does not
try to implement features that are best handled by separate, dedicated try to implement features that are best handled by separate, dedicated
tools. Window splitting in terminals is a prime example of that tools. Window splitting in terminals is a prime example of that
concept, whereby the editor provides commands to interact with several concept, where the editor provides commands to interact with several
terminal multiplexers (e.g. `tmux`), as opposed to emulating their terminal multiplexers (e.g. `tmux`), as opposed to emulating their
functionalities. functionalities.
@ -157,7 +157,7 @@ post in an issue in unmangled form (c.f. `c++filt`).
=== How can I explore the filesystem the way Vim's NerdTree does? === How can I explore the filesystem the way Vim's NerdTree does?
The builtin file completion engine used when opening a file for editing The builtin file completion engine used when opening a file for editing
(using the `:edit` command and letting the suggestions popup in the menu (using the `:edit` command and letting the suggestions pop up in the menu
beneath) is more convenient than Vim's, which should suit basic needs. beneath) is more convenient than Vim's, which should suit basic needs.
However, if you need an actual explorer to interact with the editor, However, if you need an actual explorer to interact with the editor,
@ -174,9 +174,8 @@ the language you're using with the help of the `|` key.
Example: `%|indent<ret>` to indent an entire buffer with C code. Example: `%|indent<ret>` to indent an entire buffer with C code.
Note that you can also set the `formatcmd` option, used by the `format` You can also set the `formatcmd` option and use the `:format` command to
command to handle formatting in the current buffer without further format the entire buffer.
interaction.
=== Can Kakoune automatically complete the parameters of my functions? === Can Kakoune automatically complete the parameters of my functions?
@ -288,9 +287,9 @@ characters before the cursor, which never modifies the current selection.
The `:exec` and `:eval` commands can apply changes to a comma-separated The `:exec` and `:eval` commands can apply changes to a comma-separated
list of buffers, passed as argument to the `-buffer` flag. list of buffers, passed as argument to the `-buffer` flag.
In order to the editor figure out which buffers are open, the special value In order to let the editor figure out which buffers are open, the special
`*` is accepted as a wildcard. For example, in order to reload all open value `*` is accepted as a wildcard. For example, in order to reload all
buffers: open buffers:
---- ----
:eval -buffer * e! :eval -buffer * e!