A Johnston dijo [Sat, Nov 22, 2025 at 10:46:17AM -0800]:
Package: wnpp
Severity: wishlist
X-Debbugs-CC: [email protected]
* Package name : msedit
Version : 1.2.1
Upstream Author : Microsoft Inc.
* URL : https://github.com/microsoft/edit
* License : MIT
Programming Lang: Rust
Description : Console text editor (Microsoft Edit)
Microsoft recently released an easy to use console text editor written
in Rust licensed as MIT.
Wow, this looks like a quite nice addition! I see several other well-known
distributions already package it, which makes me think the licensing is
actually correct and not something to trick you into signing with blood...
Personally, I would love to see this be the default text editor for
the Linux console because it should be the most familiar choice
available for new users. Edit/msedit works with or without a mouse and
is optimized for large files. And it has the same key bindings and
interface modality as your web browser's text editor. It also still
knows about code pages, line endings, regular expressions and tab
settings.
You are getting too ahead of yourself with this ;-) Much as I despise nano
as a braindead and too limited editor, there are arguments for it... And if
we are going to choose a new default editor, I will be pushing for The
Right One™. I am dismayed that, 50 years after its introduction, the
proportion of people with polydactilia hasn't increased — but with the
right incentives, such as having the Linux world coalesce as a single mind
behind Emacs, we will surely reach the goal of many more fingers per hand.
</joking>
So I went and checked with the Edit/msedit team at Microsoft and they
said they would be cool with me setting up a Debian package for it.
Is adding a .deb for this one a realistic thing for me to want to do?
I will be happy to maintain the packaging. Microsoft already has an
active open source community committing a stream of PRs to this
project.
I see no obstacle! It really looks like a good contribution. You have to
check which libraries/crates it pulls from, how deep its chain of
dependencies goes... Because Rust still suffers from being a
dynamic-linking-averse language.
