dotnet publish: specify RuntimeIdentifier
Ever came across this error on publishing a dotnet project that includes libs of your own: error NETSDK1097: It is not supported to publish an application to a single-file without specifying a RuntimeIdentifier. You must either specify a RuntimeIdentifier or set PublishSingleFile to false.
qtCreator: debugging not working anymore?
All of a sudden (I guess after upgrading lots of libs in archlinux) qtCreator's (at the moment 4.15) debugging stopped working. I tested with gdb manually. Symbols were there and everything looked(!) fine. BUT not a single breakpoint was hit, and manully breaking
Route traffic through ssh-tunnel
Install tun2socks Create interface: sudo ip tuntap add dev tun0 mode tun user <someuser> sudo ifconfig tun0 10.0.0.1 netmask 255.255.255.0 bind connection: badvpn-tun2socks --tundev tun0 --netif-ipaddr 10.0.0.2 --netif-netmask 255.255.255.0 --socks-server-addr
Mate Linux: alt+tab problems
Lately I experienced problems using alt+tab for switching between applications in manjaro-linux using mate-desktop. The problem seems to be the little thumbsnails showing a current preview of the specific application. To get rid of the problem: Pererences > WindowsUncheck 'Enable software compositing window
qtCreator: strange debugging behaviour?
My cpp-ide of choice is qtCreator. But lately I stumbled over a strange debugging behaviour where the debugger was triggered by some breakpoint unrelated SIGSTOPS right into the assembly. The easy fix to get around that is to uncheck "Run in terminal". I'm not
vim: deactivate visualmode
Some linux distributions have vim's visualmode automatically been activated on mouse interaction. If you want to get rid of this: touch ~/.vimrc echo "set mouse-=a" > ~/.vimrc source ~/.vimrcSource: https://gist.github.com/u0d7i/01f78999feff1e2a8361#gistcomment-2698694
NetMQ in Unity3D
Just started to play around with ZeroMQ in Unity3D using the pure C# implentation NetMQ, but I stumpled over this exception when binding the server: SocketException: The operation completed successfully.You can prevent this by just running following command on startup: AsyncIO.ForceDotNet.Force(