You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It seems impossible to find answers on how to debug Scala with jdb on Google. I
wanted to consolidate what I've learned in a easy to digest guide. Please feel
free to comment with other tips I may have missed, or corrections to what's here.
##Classes
Setting a breakpoint in a class is just like debugging java
stop at my.package.ClassName:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vim: pushing built-in features beyond their limits
Vim: pushing built-in features beyond their limits
The situation
Searching can be an efficient way to navigate the current buffer.
The first search commands we learn are usually / and ?. These are seriously cool, especially with the incsearch option enabled which lets us keep typing to refine our search pattern. / and ? really shine when all we want is to jump to something we already have our eyeballs on but they are not fit for every situation:
when we want to search something that's not directly there, those two commands can make us lose context very quickly,
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Nix can be used to build any kind of package. But here I'm just going to focus on the simple C&C++ case.
Firstly we have to know that the final built packages will located inside /nix/store. Which is globally readable directory of all build inputs and build outputs of the Nix system. The emphasis is on readable, not writable, that is /nix/store is meant to be modified by the user or programs except for the Nix system utilities. This centralises the management of packages, and keeps our packages and package configuration consistent.
So what exactly are we trying to build. Our goal is to build a directory that will be located in /nix/store/*-package-version/, where * is the hash of the package. Preferably a version is also available, but some C&C++ packages don't have versions, so in that case, there's only /nix/store/*-package/.
What will be inside this directory? It follows the GNU Coding Standards descri
There are many guides on how to install and use PGP to encrypt email.
This is not one of them. This is a guide on secure communication using
email with PGP encryption. If you are not familiar with PGP, please
read another guide first. If you are comfortable using PGP to encrypt
and decrypt emails, this guide will raise your security to the next level.