Microsoft Edit
github.com
Microsoft Edit
1–10 of 337 posts
Re: Microsoft Edit
#2Fun. I must admit I don't really know who this is for, but it seems fun.
Re: Microsoft Edit
#3Fun. I must admit I don't really know who this is for , but it seems fun.
It’s right there in the readme actually:
> The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.
Re: Microsoft Edit
#4Fun. I must admit I don't really know who this is for , but it seems fun.
It’s right there in the readme actually: > The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.
That may be the written goal, but I doubt that's the actual reason the project exists.
Re: Microsoft Edit
#5Fun. I must admit I don't really know who this is for , but it seems fun.
I’ll gladly replace vim with it, especially if it has/gets LSP support or searching via ripgrep. I’m using Helix now but like a good tui.
Re: Microsoft Edit
#6Earlier quoted context omitted.
It’s right there in the readme actually: > The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.
That may be the written goal, but I doubt that's the actual reason the project exists.
Yeah ... I don't think there's any overlap between "users largely unfamiliar with terminals" who want something easy to use, and 'Linux users who are sufficiently technical that they would even hear about this repo'.
Re: Microsoft Edit
#7Earlier quoted context omitted.
It’s right there in the readme actually: > The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.
That may be the written goal, but I doubt that's the actual reason the project exists.
My guess would be there are some people at MS who, somehow, still can do something fun. Because they are not assigned on the another project on how to make OOBE even more miserable.
/rant Today I spent 3 (three) hours trying to setup a new MSI AIO with Windows Pro. Because even though it's would be joined to the local ADDS and managed from there - I need to join some Internet connected network, setup a 3 stupid recovery questions which would make NIST blush and wait another 30 minutes for a forced update download which I cannot skip. Oh, something went wrong - let's repeat the process 3 times.
Re: Microsoft Edit
#8Fun. I must admit I don't really know who this is for , but it seems fun.
It’s right there in the readme actually: > The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.
There are already plenty of those, such as jed, mcedit, etc.
This particular application is incredibly basic -- much more limited than even EDIT for DOS.
Re: Microsoft Edit
#9Earlier quoted context omitted.
That may be the written goal, but I doubt that's the actual reason the project exists.
My guess would be there are some people at MS who, somehow, still can do something fun. Because they are not assigned on the another project on how to make OOBE even more miserable. /rant Today I spent 3 (three) hours trying to setup a new MSI AIO with Windows Pro. Because even though it's would be joined to the local ADDS and managed from there - I need to join some Internet connected network, setup a 3 stupid recov…
Perhaps those are the things that doesn’t take a Ph.D to develop.
Re: Microsoft Edit
#10Fun. I must admit I don't really know who this is for , but it seems fun.
It's for people that want to use the Windows Terminal to edit files. The old `edit` command has been unsupported on Windows since 2006, so there was no Microsoft-provided editor that could be used in the command line since then.
It's impressive to see how fast this editor is. https://github.com/microsoft/edit/pull/408
> By writing SIMD routines specific to newline seeking, we can bump that up [to 125GB/s]