microsoft / microsoft/edit

Addition of new hotkeys - Feature request

Open
#609 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
14.6k
Forks
734
Avg merge
8h 40m
Merged PRs (30d)
4

Description

First, I'd like to just comment on how wonderful I think this tiny piece of software is. Thank you for putting in the time to develop this, and I appreciate the desire to keep the editor binary small. There are a couple of features that I think could be added and I think it's a reasonable ask to meet in the middle with workflow efficiency, and lightweight binary size. here's what I'm thinking:

- Hotkeys for quickly navigating between open buffers (I wont cry about not having split panes, and settle for this...it would be awesome)
- allowing fuzzy search within the file picker
- being able to indent selected text
- being able to quickly move a line up or down, or move a block of selected text up or down.
- autocompletion of brackets, quotes, braces, parenthesis etc..
- I'm not sure if being able to quickly make code comments on a block of selected text is doable without using a treesitter or lsp, but if it could be done, this would also be awesome

I'm not sure how much extra development effort it would take to add, but I do think at the very least, it would be nice to have a way to set custom key bindings to a config file if someone doesn't like the defaults...BUT I can live without that if we at least have a bit more expansion of hotkeys to make working in the editor a bit better and navigation a bit faster.

Thank you for all the awesome work you guys are doing. I love this editor so far! I haven't had it on my system but for two days, but I've been using it ever since for work. 👨‍🍳👌💋 chef's kiss!

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by splitting the requested hotkeys, navigation, editing actions, completion, commenting, and configurable bindings into separately scoped proposals, then identify the relevant input and editor components before defining acceptance criteria for any one feature.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.