Edit is a new open source command line text editor from Microsoft that supports Windows, macOS and Linux. Learn what it can do, and how to try it on Ubuntu.
I used to use edit all the time in the autoexec.bat and config.sys days, but it's been a while. Part of me wants to try it for the nostalgia, but I can't imagine I'd ever use it with any regularity.
@jtb I'll be honest: I don't really know the difference! To me, a tool that can only be used from the command-line is a command-line tool, as Edit is, and as it's a text editor, it is a command-line text editor. I appreciate I may be alone in this. The TUI does works with a mouse, for sure - but it's also keyboard driven. 😅
as you are pointing out vim and emacs are too tricky to me, but i'll stick to nano under linux to keep it floss. And WordGrinder form more advanced text edit and word prossessor in cli !
@jaiecoute Nice shout on WordGrinder. I hadn't heard of it before but I just tried it out and it's really cool. Definitely more of a CLI Word Processor than a bare text editor, which appeals!
Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
Rest assured, I won't sell. In the event that I ever need to move on, I have a little contingency set up for the community and would just hand it over to someone I know and already trust.
The fact it doesn't count as illegal impersonation if, after being sold, they behave as if they're the same people behind the name is just immoral as fuck. Fuck this whole economical system…
Sounds like they're morphing into another slophole like the sites being paid for "SEO juice", covered by Stephanie Sterling of The Jimquisition many years ago. IIRC it basically meant/means to have slop "articles" on your site with some legit inline links for cover and then some other inline links to gambling garbage sites to boost those sites' SEO through manipulating search crawlers. Though I'm not sure that method would even work anymore in the age of so-called "AI"-crawlers.
🎙️ New Podcast Episode!🎙️ On this summer transmission, Alex and Emma hype new hardware and our presence at the Open Source Summit in Denver. We interview Viktor Petersson at Screenly. The discussion dives into Screenly’s focus on security, especially for enterprise environments, and emphasizes the need for strong hardware and software security partnerships. Listen here: system76.transistor.fm/19 #security #opensource #System76 #Screenly
On this summer transmission, Alex and Emma hype new hardware and our presence at the Open Source Summit in Denver. We interview Viktor Petersson at Screenly, an open-source digital signage company....
“Why would I even look at the sale? I have a library of hundreds of games I have never played on GOG let alone Steam and I don’t need to add to it” I say as I complete a purchase for ….. 9 new games.
The article doesn't mention XWayland at all, but KiCad works perfectly under XWayland as far as I can tell, and that is the default on at least Fedora! wxwidgets (the toolkit KiCad uses) is still flaky under native Wayland apparently, but it is perfectly okay to keep using XWayland for now, and you should! Apps and toolkits should not switch the default backend to Wayland until all major regressions are fixed, that's kind the whole reason why XWayland exists!
If you are on a distro that enables KiCad Wayland support by default and you experience the issues in that blog post, you don't need to (and probably should not) switch to an X11 session. Just launch KiCad as GDK_BACKEND=x11 kicad and it should run under XWayland just as well as it does under X11 sessions.
Some distros are dropping support for the legacy Xorg server and X11-native sessions, but nobody is dropping support for X11 apps and XWayland, and nobody should be concerned about running apps in X11 mode for as long as it's needed!
Edit: If you're on GNOME with fractional scaling and XWayland apps are blurry, apparently there's a secret toggle to fix that these days.
The KiCad development team frequently receives questions about our support for Wayland. Given that Fedora and Ubuntu are both planning to drop X11 support from their main desktop environments in the near future, we want to provide clear, transparent …
No it doesn't. Xwayland uses Wayland to get things on the screen, so it has the same fundamental limitations as Wayland (minus some window management behavior). There is no way around actually adjusting the UX in some cases.
All of that misses the important point though: their complaints are for the most part just whining while not putting any effort into wayland for their UI toolkit. Other productivity apps like blender managed to transition to Wayland just fine.
None of their whining is actionable and they take an absolutist position and say Wayland has to change for them to make all of their existing UX work, instead of trying to come up with alternative solutions.
Most of the issues KiCad is pointing out aren't Wayland protocol limitations, they are bugs in their implementation or the toolkit's (wxwidgets). Those go away under XWayland. The rest are mostly window management issues where XWayland gets to do things with extra privilege, and it also works fine.
I just tested this. The panel docking, the window position restoring, etc. all works under XWayland. If there are any specific bugs with repro steps that affect XWayland and not native X11 I'd love to know about them!
Xwayland doesn't have extra privileges, it interacts with the compositors XWM and how well and this works is an implementation detail. You got lucky with your testing. This will get worse as compositors are looking for ways to get rid of the XWM which means no more of this special handling. You will have the option to run a rootful Xwayland when that's not sufficient.
Then there are things like pointer warping which also won't work, or at least not in all the ways it works on X11. I guess you didn't test those?
@swick That sounds like a compositor problem, not an XWayland problem. I doubt KWin is going to get rid of its XWayland integration any time soon, and right now it works great and has had a lot of effort put into it...
I didn't try the pointer warps because I'm not sure where KiCad uses them. Maybe someone knows?
@swick I expect that eventually compositors will start relying on xwayland-satellite or something similar so that they don’t have to implement an X11 window manager. That is when these things will regress.
Honestly, I might prefer the native Wayland version of KiCad with all its issues rather than the XWayland version of KiCad with all of XWayland's issues. I'm willing to deal with *a lot* of inconvenience to avoid the blur of XWayland...
As long as XWayland is completely broken when using DPI scaling, it's not a suitable fallback for anything but certain games where the blur is acceptable.
I don't get it either. But since it's still broken, I totally get why distros which use GNOME would prefer to package broken wayland-native builds of applications instead of packaging broken XWayland builds of applications
Honestly I think that a lot of the animosity towards Wayland in general stems from the lack of a functional compatibility layer to run X applications in GNOME.
this is kind of skimming over the huge list of stuff that kicad uses which will never be usable under a native Wayland backend because of Wayland design decisions. So regardless of what wxwidgets does, it's not going to be able to use the native Wayland backend. It's of course a subtle problem to explain to users, but it's totally valid for kicad to rant about it when their application won't ever work with a native Wayland backend, and when the blowback of that affects users in practice.
applications tend to want to work on all configurations, because otherwise you have to give completely ridiculous user instructions like "please enable this environment variable to run the application, and then on gnome you need to enable this other experimental feature all the entire screen will be unusably blurry". Calling that a "distro problem" is hugely dismissive of the user experience in reality.
to be concrete the design enforced limitations are: - everything with window positioning - clipboard functionality - dialogs - call throttling for obscured windows - focus
Some have mitigations: - throttling has some extensions now, unsure whether they're universally supported (don't believe so) - some environments have clipboard managers - there's a feature that allows (if supported) restoration of window layout at startup (but without any other features, and without any info to the app)
@dotstdy Every other project is either working with or working to change those Wayland design decisions. It takes time, but saying these things will "never work" with Wayland is needlessly pessimistic.
well they haven't changed in the decade or so the issues have been known, and every time somebody brings it up the upstream developers get ultra defensive (like your post here) and then if you do engage with Wayland developers you get told to shut up (my favorite one is when icculus got flamed for criticising a Wayland design decision). So... Yeah...
@dotstdy All I can say to that is... sometimes there's GNOME and then there's everyone else. It's not just a Wayland thing, GNOME devs like to be opinionated in general...
I think the right call in that case is to explain to your users why things don't work properly in GNOME and why there is no viable path forward, not that it's Wayland's fault.
the people blocking that stuff in Wayland *are* the gnome developers (and to a lesser extent the KDE developers) there's no functional difference between the two groups really. Should kicad try to explain the complex political nightmare of the Linux desktop? Or should they just give their users straightforward actionable advice "don't use Wayland it breaks our app". I know which I'd choose.
@dotstdy Even if you do choose to give up on native Wayland, the answer is still to tell people to use XWayland, not to tell them to switch back to X11 sessions.
you can't tell them that because it isn't useful, actionable, advice. At best they could force it in their own code, but the app will then be blurry if you are using gnome. And distros will probably remove those disable Wayland patches anyway
it's not experimental, and it affects integer scaling too. If you have a 2x scale factor the upscaling will be "perfect" but it's still rendering at half resolution then zooming. So text looks god awful and you know, stuff like line drawing...
is cursor warping under xwayland? Does window placing (in absolute coordinates, controlled by app) work in xwayland on every wayland implementation reliable?
You know that feeling when you're drowning in research papers, desperately trying to connect dots across thousands of studies? What if I told you AI is already doing that h
Al Jazeera - Tehran, home to 10 million people, suffers from severe traffic congestion making a speedy evacuation impossible. aljazeera.com/news/2025/6/17/t…
As of today, all Copr builder virtual machines are now being spawned from
bootc images, which is no small feat because the builder infrastructure
involves multiple architectures (x86_64, aarch64, ppc64le, s390x), multiple
clouds (Amazon AWS, IBM Clou…
Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
they want to earn it? They got it backwards. You gotta earn needing no introduction. I'm keeping my eye on this because that explanation stinks to high heaven.
📅 Date: June 21, 2025 4pm EAT (1pm UTC) 🕒 Learn how to contribute to Fedora Docs, get hands-on experience, and explore beginner-friendly tasks with the community.
KDE Plasma 6.4 has arrived bringing lots of modern enhancements to my favourite Linux desktop environment, and what's used on SteamOS / Steam Deck Desktop Mode.
Mike Stone
in reply to omg! ubuntu • • •jtb
in reply to omg! ubuntu • • •omg! ubuntu
in reply to jtb • • •Mark Fraser
in reply to omg! ubuntu • • •j'ai écouté 📢👂
in reply to omg! ubuntu • • •as you are pointing out vim and emacs are too tricky to me, but i'll stick to nano under linux to keep it floss. And WordGrinder form more advanced text edit and word prossessor in cli !
PS : i like the note in this blog post !
omg! ubuntu
in reply to j'ai écouté 📢👂 • • •HoracioDos
in reply to omg! ubuntu • • •