I started using gedit because it was the default on the Linux distro my university ran at the time. The craftsmanship of programming, so to speak. I learned about programming languages, operating systems, compiler design, and all those wonderful things, but all this time, I was never given the opportunity to sit down and think about the tools I was using. I think the problem is, in university, there was never any class that was really about teaching us how to use properly and efficiently use tools. I had the ramen right here at home, no cash on hand, and well, I was hungry. If you were to think of emacs as a sushi meal prepared by an experienced chef, then you could think of gedit as a microwaved bowl of ramen with a half cup of sriracha sauce dumped on it. It’s a fairly shitty text editor. It will freeze up if you try to open a text file more than a few hundred kilobytes, or with lines that are too long for it to properly digest. It’s the GNOME text editor. Its noteworthy features are syntax highlighting, and the ability to have multiple tabs open at once. Most of it on Linux, and most of it using a text editor called gedit. It’s probably because as a teenager, I grew up with Windows 98, and on that platform, back then, command-line tools were very much second-class citizens. In university, I was introduced to Linux and somehow, over the years, I became hooked. I spent a total of 11 years in university, and over that course, I probably wrote over 400K lines of code. I’ve been programming since I was 16, but all this time, I’ve never learned how to use a “proper” text editor. Half of our stuff still pretends it's operating on those old character based teletype machines I mentioned earlier.This is my coming out. If you do not appreciate doing deep lore spelunking to understand things, the unix/linux ecosystems are going to be frustrating for you. > If you don't know the relationship between the GUI name alias, and the literal process name, how are you supposed to figure it out? It's a direct abbreviation of ex's "visual" command (and used to just launch you into ex in visual mode), and everyone using it at the time would have known what it meant. ed didn't do this because it needed to be conscious of teletype machines. It took a lot of it's (non-motion) commands straight from ed, but let you see the entire page of text as you changed it. > "Vi" is not "just naming the editor what it is", it's a relatively distinct short name that doesn't actually mean anything unless you know the reason for the name (which I did not for years after being introduced to it).īut "visual" is was vi is. There are several gedit things that aren't in Text Editor and probably won't be, like the side panel and bottom panel and assorted plugins for those, but these days I find if I want those, I'll be happier in Builder or VS Code anyway. Special font for the mini map, which is very useful to see patterns and find a particular block of code. Dark mode! (The syntax highlighting changes accordingly). UI is styled according to the syntax highlighting. It's noticeable if you scroll through a file with a device that supports pixel-perfect scrolling. Which is not an especially practical concern most of the time, but it feels nice. It has noticeably better rendering performance. Automatic editor settings via editorconfig / modelines is built in. It also means you get the benefits of auto save, but without it actually changing the files until you tell it to. This is great if you're jotting something down and don't expect to save it anywhere and then your battery dies. Session saving is built in, and it even restores unsaved files, similar to VS Code or Sublime Text. (If you want the IDE parts, Builder is excellent and reasonably lightweight). They share a lot of code, so it's pretty much Builder minus the IDE parts. Especially if you're using Builder as well. The new Text Editor is really nice! You all should give it a chance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |