I am running a hugo site this blog. I had the idea of how do I add a promotional Value for value note that would show at the bottom of each post, since I am shooting for the advertisement-free Value for Vale model. I wanted to figure out how to do this. I went to my current theme LoveIt and looked through the layout options where I eventually found footer.html themes/LoveIt/layouts/partials/single/footer.

I started getting the following error when trying to run nvm for windows on my work development system. NVM ERROR open \settings.txt: The system cannot find the file specified The User variable NVM_HOME was removed from the system. NVM would not function at all without the above error. I found the following ProgrammerAH - NVM ERROR open \settings.txt: The system cannot find the file specified solution. Now since I am using NVM for windows without admin I am not needing the NVM_SYMLINK.

This will help you create a zip archive that went extracted just dumps a bunch of files in the directory it is extracted in. Usually a problem you don’t want in my option, but when I was requested to make such a zip archive, here is how I made one on Microsoft Windows 10. How to make a zip file containing just a bunch of files, not contained in a root directory.

Possible Alternative solution for Stack Overflow - How to install node version manager without Admin The Short answer is NVM For Windows can’t be installed without admin privileges, yet. However, you can manually use it and change node versions manually without needing admin again nor having to manually manage installing various versions of Node.js using the Node.js Windows installer ever again. My solution is ask your local admin to install nvm for Windows for you and additionally to install it in a not locked-down folder path on the C drive, something like C:\nvm worked for me.

I was updating the font awesome version on a work project when upgrading Angular and ran into a simple problem that wasted a lot of time. I was getting this error on the console at runtime: ERROR Error: Could not find icon with iconName=home and prefix=fas in the icon library. Since faHome was imported without an error in typescript / javascript, this turned into a fix at run-time problem. import { faHome } from @fortawesome/free-solid-svg-icons <fa-icon icon="home"></fa-icon> The fix after closer re-examination was that home was renamed to house in Font Awesome 6.

The Issue Zoom window goes full screen everytime someone shares their screen during a meeting. I have a very intentional placement of windows on the screen. So I can see my notes etc., so every time Zoom goes full screen, its bit of a disruption for my workflow. After a few times, I looked for a way to stop this from happening and found it. See below for how I stopped the full screen take over with Zoom meetings.

The Problem Your running Linux Mint or other Linux on a Classic Mac Pro {1,1; 2,1; 3,1; 4,1 or 5,1} you may have noticed that opening the DVD / optical drive is a bit of a challenge under Linux on these macs or other similar systems. The old macOS tricks of pressing and holding F12 key no longer works. And there appears to be no applets or shortcuts available yet on the panel to send a command to open the drive.

This is for you If you try to lock your screen like you do on most PC’s and instead are greeted with a surprising new window titled Melange. This is a guide on how to swap or fix the screen lock shortcut so that it’s Win/Super + L instead of Linux Mint default of CTRL + ALT + L to lock the screen. Relevant for Debian, Linux Mint and possibly more Cinnamon-based UI Linux distributions.

The problem I have stalled not fully starting Mac Pro 3,1 after re-installing its SSD hard drive. Upon reinstalling the SSD back into the Mac Pro the machine just hung on LM logo never booted any further. Recalling, I should be able to switch to a console output for booting with the chance of seeing any potential errors. I researched and rediscovered ctrl + ALT + Choose one at a time F1 through F7 to switch between consoles and GUI.

The Problem Had an Angular application setup like this at work and was trying to figure out why we were getting a blank leading page when clicking the print button in ngx-extended-pdf-viewer. So I created a new fresh start with the following components we were using: Angular 12.2.16 ngx-extended-pdf-viewer 3.2.4 Conclusion now the blank is at the end. So this combination has issues to begin with at this time. The Solution Upgrade to ngx-extended-pdf-viewer 10.