Windows: version 10 Sumatra PDF: version 3.2 64-bit
A dark mode for Sumatra PDF is really easy – you just need to tinker with 3 lines of code in the settings.
Why Use Sumatra PDF?
In my opinion, it’s the best PDF reader. It’s small in size, super-fast and doesn’t have any annoying cruft.
Why a Dark Mode (Night Mode)?
If you code for long periods of time, then it’s really great to have your code editor run in dark mode. This greatly reduces the strain on the eyes.
But let’s say you are also following along an e-book, maybe a PDF and you switch to Sumatra PDF. The default setting is black text on white background. Immediately your eyes are shocked with bright luminescent white light. It’s as if you were relaxing in a room with the lights switched off and suddenly someone walked in and abruptly turned the lights on.
As you are coding along you have to switch back and forth multiple times between your PDF reader and code editor. It can be really jarring for the eyes and nerves.
How to Enable Dark Mode?
In Sumatra PDF, click on the Menu -> Settings -> Advanced Options
This should open the SumatraPDF-settings.txt file in your text editor. Change the following 3 lines under the heading FixedPageUI:
While there are many Github projects and NPM packages providing Polyfill for URLSearchParams, the easiest way to use it is using a CDN link to one of the Polyfill implementations. Here is one from:
You may have several version of the JDK installed on your machine. By default you may be using JDK 11 or even 13, but GlassFish requires JDK 8.
Running asadmin generates the following error
Exception in thread “main” java.lang.NullPointerException at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.initializeServiceLocator(AbstractModulesRegistryImpl.java:128) at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.newServiceLocator(AbstractModulesRegistryImpl.java:120) at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.createServiceLocator(AbstractModulesRegistryImpl.java:194) at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.createServiceLocator(AbstractModulesRegistryImpl.java:200) at com.sun.enterprise.module.single.StaticModulesRegistry.createServiceLocator(StaticModulesRegistry.java:64) at com.sun.enterprise.admin.cli.CLIContainer.getServiceLocator(CLIContainer.java:193) at com.sun.enterprise.admin.cli.CLIContainer.getLocalCommand(CLIContainer.java:231) at com.sun.enterprise.admin.cli.CLICommand.getCommand(CLICommand.java:207) at com.sun.enterprise.admin.cli.AdminMain.executeCommand(AdminMain.java:347) at com.sun.enterprise.admin.cli.AdminMain.doMain(AdminMain.java:282) at org.glassfish.admin.cli.AsadminMain.main(AsadminMain.java:33)
Edit: ~\glassfish\config\asenv.bat Assuming JDK 8 installation path is C:\Program Files\Java\jdk1.8.0_241
You are working on code or writing something important, you are in the flow, you reduce or increase the volume a bit for the perfect sound-level and pops-up this ugly big annoying Windows 10 volume control disrupting not only your thought process but captures the screen real-estate for 5 seconds before it fades away.
This is down-right evil and will no longer be tolerated 🙂 Well thanks to Marcus Venturi there is a way to disable this.
Windows 10 NetBeans 8.2 JDK 1.8.0_241 GlassFish Server 4.1.1 Maven 3.0.5 (bundled with NetBeans 8.3)
In NetBeans IDE, trying to run a Maven project on GlassFish generates the following Maven Error:
Return code is: 501 , ReasonPhrase:HTTPS Required
Effective January 15, 2020, the Maven Central Repository no longer accepts non-SSL HTTP connections. You have to use TLS, i.e. the HTTPS protocol. Upgrading to a more recent version of Maven resolves the error.
Use a non-bundled recent version of Maven installed on your system. Download directly from the Maven site and install on your system.
Then in NetBeans 8.2, go to Tools -> Options, then select the Java tab and then the Maven tab:
Note the outdated version. Click the drop-down box and select the stand-alone version that you installed.
Upgrading to the later Maven version, for example 3.6.3 resolves the error.