![]() ![]() 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. Now you can close the second window and remove the undesired tabs of the right side of the original window.The new Text Editor is really nice! You all should give it a chance.The tricky points: Drag from the second window, the tab of your document and drop it as a tab in the right side of the original window.The tricky points: Open a new tab in the second window, so now you can see tabs instead of only the document.It's better to use one for writing an the other for reading/copying. My suggestion is to use "Don't Edit", otherwise you'll be overwriting your own changes from one window to the other. It will tell you that the file is opened somewhere else and ask you if you want to edit the file anyway. Open a second window and open again the same file (as suggested by gedit -new-window file).This will vertically split the window opening a new document as a tab on the right side. ![]() Go to Documents->New Tab Group (or press Ctrl+Alt+N).In case anybody still wonders, at least in Ubuntu 16.04 there is a workaround using also tabs as requested by the OP and with a read-only side (just replied here): ![]()
0 Comments
Leave a Reply. |