Changing the PATH variable in PowerShell 5.1

This $ENV:PATH holds the value of your current PATH settings. This variable can be updated in your current PowerShell terminal :

$ENV:PATH="$ENV:PATH;C:\Program Files (x86)\Notepad++"

You can also retrieve the current value with the following cmdlet Get-ItemProperty :

Get-ItemProperty -Path ‘Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH

To make this change permanently, open up a new PowerShell terminal as Administrator (using runas) :


$oldpath = (Get-ItemProperty -Path ‘Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH).Path

$newpath = "$oldpath;C:\Program Files (x86)\Notepad++"

Set-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH -Value $newpath

Now, just log out of your current Windows session to take this change into account

NB : Tested successfully on Windows 10

Advertisements

Missing firmwares for module i915

While upgrading your Debian Stretch, you can come up with this message :

W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915

This has been referenced as a bug :

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864601

If you can’t upgrade to Debian Buster, there is a possible workaround

Otherwise, after switching to Buster, the available version of firmware-misc-nonfree provides the missing firmwares.

Realtek wifi card rtl8723de not detected on Debian Stretch

The HP Pavilion 15-cc507nf notebook comes up with a wifi adapter Realtek rtl8723de not detected after a fresh install of Debian Stretch.
The firmware-realtek from the stretch backports repository does not provide any available module for this wifi card.

https://unix.stackexchange.com/questions/394012/wifi-not-working-in-debian-8-9-having-rtl8723de-driver-10ecd723

https://ubuntuforums.org/showthread.php?t=2367405&page=2&s=956015e55460cc1fbb14a84439fa3b46

https://github.com/lwfinger/rtlwifi_new/issues/267

https://github.com/lwfinger/rtlwifi_new/issues/270

Support is expected in Q4/2017

Windows PowerShell Syntax Plugin set up in gVim

Windows PowerShell Syntax Plugin provides Syntax coloring, indenting and filetype detection for Windows PowerShell.

It is available at :

http://www.vim.org/scripts/script.php?script_id=1327

http://github.com/PProvost/vim-ps1

If you use Pathogen, just extract into your bundle folder.

If not, just set up Pathogen as follows below :

https://github.com/tpope/vim-pathogen

Additional actions to make it work on Windows 7 :

cd C:\Program Files (x86)\Vim\vimfiles
mkdir autoload
mkdir bundle

Install pathogen.vim in C:\Program Files (x86)\Vim\vimfiles\autoload

To enable Pathogen, add this to your gvimrc :

execute pathogen#infect()
syntax on
filetype plugin indent on

On Windows 7/10, the gvimrc file must be named as _gvimrc and located in one of the folders :

$HOME/_gvimrc
$HOME/vimfiles/gvimrc
$VIM/_gvimrc

$HOME points to your home directory in Windows 7 and $VIM points to your directory where Vim/gVim have been installed.

The personal initialization files are searched in the order specified above
and only the first one that is found is read.

http://vimhelp.appspot.com/gui.txt.html#gvimrc

This plugin is now enabled. Enjoy !

WARNING : Failed to connect to lvmetad. Falling back to device scanning

At boot time, the following message can pop up :

WARNING : Failed to connect to lvmetad. Falling back to device scanning

This message is displayed, whether running Debian stable or Debian testing.

To get rid of this message, disable lvmetad in /etc/lvm/lvm.conf


use_lvmetad=0

Update the initramfs for the current kernel your system uses :

update-initramfs -k $(uname -r) -u; sync

Reboot your system and you’re done !

Ubuntu workaround for this issue

This issue has already been reported in the Debian bug tracking system : #846946