macOS Sublime Text 3: How do I disable one window / tabbed windows? - sublimetext3

Not to long ago (well, maybe months and months), Sublime 3 has started launching as a singular window with tabbed windows that have their own tabs. I despise this approach. See screen shot:
How do I disable this behavior?
Version 3.1.1 build 3176
The only Packages I have installed are:
A File Icon
Groovy Snippets
Material Theme
Package Control
Pretty JSON

This particular feature is something that's happening as a result of your using MacOS (i.e. it's not something that Sublime does natively; the OS is doing it on your behalf).
In the general case most MacOS applications should have native menu items to combine windows together like this at the user's request in combination with the Prefer tabs when opening documents setting in the Dock area of the system preferences.
Sublime doesn't support the native menu items for this (yet), so it relies solely on the setting; having it set to Always (and also In Full Screen Only, but this tends to cause problems with Sublime) makes MacOS automatically "tab" new windows. Setting that setting to Manually stops this from happening.
This is also somewhat controlled by the Theme that you're using in Sublime. For MacOS, a Sublime theme can theme the menu bar of the window to match the overall application theme. Behind the scenes, this makes Sublime declare to MacOS that it wants to be in charge of displaying it's own window, which stops the system from automatically combining windows together.
An example of a theme that does this is the Adaptive theme that ships with Sublime.

Related

How to change the font of Visual Studio Code's UI?

I'm trying to figure out how to change the font used in non-editor tabs in Visual Studio Code; right now this is what I'm getting (zoom the picture to better see what I'm referring to):
As you can see, a Serif font is used on these non-editor tabs (extension info, Git Graph tab, etc.), making it quite unpleasant and really hard to read.
This happened all of a sudden, I'm quite sure that it is not the default and a nicer and more readable Sans font was used before (like on the left panel), until this problem occurred. I've tried to find if it is possible to change this from inside VSC, but I'm only able to change the fonts used in the editor tabs.
I don't know why and how this behavior has started, and I'm not really sure if this issue is caused by VSC itself, by an extension, by the OS, or something else.
If it matters, I'm working on Linux, on a fully updated openSUSE Tumbleweed with KDE, and like I said this problem started to manifest itself only recently, it was not how it worked by default.
Any clue on how to solve this?
Visual Studio Code does not offer convenient solution out of the box to change the UI font family.
But a developer created the Customize UI plugin for VS Code.
⚠️ EDIT 02/01/2023: following the version 1.74, the Customize UI plugin no longer work, see here. There is currently no ways to change the font in VSCode.
Setup
Install the Customize UI plugin
Restart VS Code
Open VS Code Settings
Change Customize UI Font:Monospace to Fira Code
Change Customize UI Font:Regular to Helvetica Nueve or Arial depending on your OS
Alternativaly, you can edit those settings using the json settings editor as follow:
"customizeUI.font.regular": "Helvetica Nueve",
"customizeUI.font.monospace": "Fira Code",
GitHub issue here
vscode is an electron app so you can actually just open up the developer tools in the help menu, look up the location of workbench.desktop.main.css under the source tab, make a backup and edit the font-family rule for your OS.
There's a pretty gnarly-phrased notification that pops up about vscode being corrupted, however the linked-documentation is fairly clear it's just unsupported officially.
In most of the Linux distributions we get the option to change the fonts systemwide if you are okay with changing the system font.

Same executable with different icons

I want to open a pdf-viewer (okular) with different icons from the gnome-console.
Basically I want to differentiate between pdfs I am reading. Some would have the default okular icon, but I would like to have a different/special icon for the pdf generated by the LaTeX document I am editing.
Thinking about how to do this, I realized that I am not sure how gnome knows what icon to use when I execute /usr/bin/okular from the console. How is that bin related with an icon, no .desktop file involved right?
Applications set their icon at launch, to a compiled-in value. Most do it using the API of their graphics toolkit (Gtk provides various forms of the gtk_window_set_icon API call), but it has its roots in an X Windows window-manager property that's as old as dirt — which is why, for example, okular still has an application icon in Gnome Shell even though it's a KDE application.
You can see a grayscale representation of the icon(s) an application is exporting if you type xprop in a terminal, then click the application's window. (You need to have the correct utilities package installed, it's called xorg-x11-utils in Fedora.)
The application icon doesn't depend on Gnome or on the .desktop file under any circumstances.
(In fact, you could create your own $HOME/.local/share/applications/okular.desktop file that represented the application with a different icon, and launch it by clicking that icon, but it would be ignored in favor of the one that's compiled in to the application once it started. I have some custom launchers in my Favorites panel for different VNC sessions, using a different icon for each, but they all show up as TigerVNC with the standard icon when launched.)
AFAIK the only way to do what you want would be to compile your own separate version of okular with the icon changed to something else. That's just not the way application icons were meant to be used, sorry.

Eclipse doesn't render menus or popups

I can't view many windows in eclipse since they don't properly render. The window opens and has an outline, but the body appears transparent and just displays the window behind it. Is there a resolution to this bug? It makes Eclipse extremely frustrating to use. This is using Ubuntu 14.04 and Eclipse 4.5.2 Mars. Eclipse was installed from the latest version on the website.
Another, probably unrelated issue, is that autocomplete doesn't perform any kind of prefix matching. It only appears after a period (in Java) and takes 5-10 seconds to load. If I begin entering characters, it never provides options.
Another issue is that many plugins break emacs keybindings and emacs keybindings are completely inconsistent. In some windows that utilize some bindings, but in another window they different bindings or don't use emacs bindings at all.

Is it possible to change the color of the scrollbars in gVim / Vim in windows os

As the title says, was it possible for gVim editor to have customize scrollbars in windows OS? If it wasn't natively supported are there workaround to achive this?
You either have to modify the GUI widget styling directly in the source code and build your own version of the Vim executable, or use a Windows tool (if such exists; I remember something called Window Blinds that allowed custom styling) that can tweak the appearance of arbitrary Windows applications.
The latest source code and runtime files can be downloaded via FTP or retrieved from Mercurial; see vim.org for details.

GVIM 6.4 has better GUI and options than GVIM 7

I wanted to use tab file feature of gvim, hence I moved to gvim 7.0 from gvim 6.4.6 since older one does not support it. However to my amazement I see much better GUI in my older gvim. Not only the appearance but options are also less. For example in the "Edit" menu there is no select font option which was there in GVIM 6.4.6.
Do I need to change something (.vimrc etc) to have GUI and features better than 6.4.6? Attach is the screenshot showing new vs old to give you an idea...
Thanks for the help
Newbie
You're comparing apples and oranges. Vim can be compiled with different GUI toolkits, and your newer, less-appealing looking one was compiled without the modern GTK2 GUI.
You can check this via :version. Try to get a different Vim build.

Resources