181–190 of 191 posts
Earlier quoted context omitted.
I love nano and used it as my terminal editor on Linux. Edit seems super approachable to newbies with it's mouse support in the menus. I love that and would love to see it in nano.
Just put set mouse in your ~/.nanorc and then you can click on all the UI elements, including the actions/functions at the bottom of the screen, which play the roles of the menu in Nano.
Earlier quoted context omitted.
If it’s not the same then it’s a bad idea to give it the same name. Imagine searching for a tutorial or a bug fix.
One would be in nothing more than the very same situation, which apparently has been problematic in your way for pretty much no-one, of Microsoft's various different programs all named CHKDSK. There have been at least 3, one of which we were told for years was superseded, which was not true for the next two, and the third of which has had four different flavours in the past 30 years. Or command names that are common…
Like most people do.
>Or command names that are common words like MORE, BREAK, DATE, CALL, IF, MODE, MOVE, PROMPT, SORT, TIME, COPY, and PATH for that matter.
Same problem
>Microsoft has published its own command reference for decades
And changes the URLs to that references multiple time. More than one old links lead to nowhere now
>including entire books on commands in Microsoft operating systems, for even longer.
Books with a hefty price tag
Hey all! I made this! I really hope you like it and if you don't, please open an issue: https://github.com/microsoft/edit To respond to some of the questions or those parts I personally find interesting: The custom TUI library is so that I can write a plugin model around a C ABI. Existing TUI frameworks that I found and were popular usually didn't map well to plain C. Others were just too large. The arena allocator e…
I checked the git history to see if you included the Zig version but looks like first revision is rust... In the Zig version did you use my zigwin32 project or did you go with something else? Also, how did you like the Zig build system vs rusts?
Overall, I liked the build system. What I found annoying is that I had to manually search for the Windows SDK path in build.zig just so I can addIncludePath it. I needed that so I can add ICU as a dependency.
The only thing that bothered me apart from that was that producing LTO'd, stripped release builds while retaining debug symbols in a separate file was seemingly impossible. This was extra bad for Windows, where conventionally debug information is always kept in a separate file (a PDB). That just didn't work and it'd be great if that was fixed since back then (or in the near term).
Why didn't they make this a package available ia winget? Did it have to be part of the OS?
It is available via winget https://github.com/microsoft/winget-pkgs/tree/master/manifes... Could be installed with winget install Microsoft.Edit
Earlier quoted context omitted.
And I guess forcing FFI for plugins is going to be a headache for many plugin authors.
What I imagined is that people could load runtimes like node.js as a plugin itself in order to then load plugins written in non-native languages (JavaScript, Lua, etc.; node.js being an extreme example). I wonder if WASM could also be one such "adapter plugin"? But plugins are still a long way off. Until then, I updated the issue to include your suggestion (thank you for it!): https://github.com/microsoft/edit/issues…
"Edit". Really? Was that the only name available? I am sick of these companies repurposing very common computing terms for their mediocre products.
"edit" has historically been the command used to invoke the built-in editor in Microsoft operating systems since DOS 5.0. Why should it suddenly change?
Earlier quoted context omitted.
I wholeheartedly agreee. Nano is quite awesome, it is battle-tested and already has more features than needed for a basic text editor. Actually, Nano is too often frowned upon as too-basic, but is actually has a few advanced features that basic editors do not have (e.g., keyboard macros). I'd argue that Nano is simple rather than basic :). I tried discussing it here a few months ago but it did not took off: https://n…
I love nano and used it as my terminal editor on Linux. Edit seems super approachable to newbies with it's mouse support in the menus. I love that and would love to see it in nano.
Hey all! I made this! I really hope you like it and if you don't, please open an issue: https://github.com/microsoft/edit To respond to some of the questions or those parts I personally find interesting: The custom TUI library is so that I can write a plugin model around a C ABI. Existing TUI frameworks that I found and were popular usually didn't map well to plain C. Others were just too large. The arena allocator e…
It not only written in Rust, but they avoid basically any dependencies to third-party crates (beside the obligatory windows-sys/libc), optimizing probably for binary size. To achieve this, they seem to re-implement considerable parts of the rust ecosystem (own TUI library implementation, own unicode handling, own arena implementation, ...).
I’m guessing this isn’t just to optimize for binary size. If you have the resources to avoid third party dependencies you eliminate the burden of having to build a trust case for the third party supply chain. That is the number one reason we sometimes reimplement things instead of using third party packages where I work: the risk from dependencies along with the effort required to establish that we can trust them is…