chore: fix some typos (#3239)

Signed-off-by: lvyaoting <lvyaoting@outlook.com>
This commit is contained in:
lvyaoting 2024-04-08 18:04:38 +08:00 committed by GitHub
parent 467c71dbb8
commit d1d38d1ed7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 5 additions and 5 deletions

View file

@ -318,7 +318,7 @@ func (h *BufPane) ResizePane(size int) {
}
// PluginCB calls all plugin callbacks with a certain name and displays an
// error if there is one and returns the aggregrate boolean response
// error if there is one and returns the aggregate boolean response
func (h *BufPane) PluginCB(cb string) bool {
b, err := config.RunPluginFnBool(h.Buf.Settings, cb, luar.New(ulua.L, h))
if err != nil {

View file

@ -1011,7 +1011,7 @@ func (b *Buffer) MergeCursors() {
b.EventHandler.active = b.curCursor
}
// UpdateCursors updates all the cursors indicies
// UpdateCursors updates all the cursors indices
func (b *Buffer) UpdateCursors() {
b.EventHandler.cursors = b.cursors
b.EventHandler.active = b.curCursor

View file

@ -7,7 +7,7 @@ import (
)
// The InfoBuf displays messages and other info at the bottom of the screen.
// It is respresented as a buffer and a message with a style.
// It is represented as a buffer and a message with a style.
type InfoBuf struct {
*buffer.Buffer

View file

@ -205,7 +205,7 @@ func (n *Node) ResizeSplit(size int) bool {
return n.parent.hResizeSplit(ind, size)
}
// Resize sets this node's size and resizes all children accordlingly
// Resize sets this node's size and resizes all children accordingly
func (n *Node) Resize(w, h int) {
n.W, n.H = w, h

View file

@ -214,7 +214,7 @@ safe and recommended to use subgroups in your custom syntax files.
For example if `constant.string` is found in your colorscheme, micro will us
that for highlighting strings. If it's not found, it will use constant instead.
Micro tries to match the largest set of groups it can find in the colorscheme
definitions, so if, for examle `constant.bool.true` is found then micro will
definitions, so if, for example `constant.bool.true` is found then micro will
use that. If `constant.bool.true` is not found but `constant.bool` is found
micro will use `constant.bool`. If not, it uses `constant`.