![]() ![]() Maybe it’s just me because for too many years Microsoft offered very basic Notepad with Windows OS, and WordPad, which is aimed towards writing documents, so I apply this concept to GNU/Linux as well, shame on me. The thing is, I don’t think that anybody expects an operating system to have a built-in, graphical, advanced, extensible, development-ready text editor. With file browser you have quick access to related files in the project, mini-map is kinda popular because of Sublime Text I think, and line numbers are, well, line numbers.īut I don’t think that all of this is really necessary for Gedit. This setup may be a bit more useful for you if you decide to use Gedit for development in some language, that Gedit supports. So if we tweak some plugins and enable some settings, we can get this result: There’s a plugin section in the settings, that features some preinstalled plugins, and users can search for extra plugins online or in repositories. Not much to see, looks like a very basic editor.Īnd I think it is one hundred percent fine because if you need to quickly tweak some configuration files it is more than enough. This is how it looks by default on the GNOME Shell desktop: While this is not an issue, I don’t think that this is necessary. I mean, it is great to have a default editor in the system, because casual users sometimes, actually, edit files, but both Gedit and Kate are trying to be hackable developer-friendly editors. Gedit, Kate, and other default editorsĭefault editors are a kinda weird thing, though. These kinds of editors are worth to be mentioned here because I think that it is a good thing to have, and sometimes those are in fact usable. I would like to begin this with a look at default editors in GNU/Linux, which usually are provided with a desktop environment. Such editors are not as simple as plain text editors like MS Notepad, and not as complex as IDEs. ![]() There are several classes of text editing tools, which are different in many ways, and are used in different situations, like pagers, IDEs, hex browsers, stream editors, and so on, so in this topic, I will only touch a small subset of whole text editor world - advanced text editors. Well, a good programmer can write everything in the simplest of editors, or even on paper, but I think no one will argue that a good text editor will boost our work tremendously.ĭon’t take this post too seriously though, as I think text editor is kinda personal thing, and for most users, key features will differ, so I’m not expecting anyone to 100% agree with me. The same goes for programmers - a good text editor enhances our productivity and makes navigating (and thus understanding) the project we’re working with a bit easier. As software engineers, and programmers, we mostly work with text, so obviously we’re all using some sort of a text-related program.Įditing and navigating text is a huge part of our daily job, so a good text editor is like a good set of tools for blacksmiths.Ī good blacksmith may still do their work with inappropriate gear, but will be more productive, and the end result will be in much better shape if good tools are at hand. ![]()
0 Comments
Leave a Reply. |