Scribbles for my bad memory

package name for common used Linux util in Debian/Ubuntu

ps

apt install -y procps

ping

apt install -y iputils-ping

telnet

apt install -y telnet

general solution for apt get/apt upgrade similiar issues

first,

sudo dpkg --configure -a

followed by:

sudo apt --fix-broken install

bash

ASPNETCORE_URLS="http://*:9143" ASPNETCORE_ENVIRONMENT="Development" dotnet Yourproject.dll
ASPNETCORE_ENVIRONMENT="Development" dotnet run --urls "http://*:9143" --no-launch-profile

for Windows command line (cmd.exe)

setx ASPNETCORE_URLS "http://localhost:5001"
setx ASPNETCORE_ENVIRONMENT "Development"
dotnet Yourproject.dll

for Windows powershell

$Env: ASPNETCORE_URLS "http://localhost:5001"
$Env: ASPNETCORE_ENVIRONMENT "Development"
dotnet Yourproject.dll

Reference

The keyboard shortcuts setting in the Settings app can only support 4 workspaces. However, I want to use 8 workspaces to implement the goal of "everything in its right place". Solution:

sudo apt install dconf-editor
dconf-editor

org/gnome/desktop/wm/keybindings
# Then you can do what you want to do there

Reference

By the way, my final configuration is shown below:

Ctrl + 1-8 Switch to workspace 1-8
Ctrl+Alt+1-8 Move current window to workspace 1-8 and jump to that workspace

• Workspace 1: Chrome
• Workspace 2: Gnome-terminal
• Workspace 3: Rider
• Workspace 4: WebStorm
• Workspace 5: Ebook reader (Evince and others)
• Workspace 6: File Manager, BitTorrent downloader,
• Workspace 7: VMs
• Workspace 8: Settings, Telegram, music player, misc.

1. Jenkins 虽然通过ssh访问一个node来执行build或者 deploy任务，而且它也确实执行了远程机器的.bashrc 脚本，但它却刻意的抹掉了PATH 环境变量。所以在你要运行的bash脚本里再 source 一遍 /etc/profile 就有了必要。
2. Jenkins自己的环境变量，可以在脚本里直接用，但从bash里来的环境变量，如 $?，就得用反斜线转义 \$ 符号。
3. .bashrc 别 echo 东西，否则 Jenkins 会拒绝干活。（应该弄一台专门的机器只跑 Jenkins）

PS: 上面第2条其实描述不准确，后面踩的坑证明，如果用 sh 命令里有环境变量，老老实实用单引号，如果非用双引号，你反而要用\给 $转义。切记！Jenkins环境不是bash环境。不论是否 Jenkins里定义的环境变量，如果要在bash脚本里用，就老老实实用单引号。

1. http_proxy environment in sudo command： http_proxy=xxx:xxx sudo yourcommand doesn't work, you should sudo http_proxy=xxx:yyy yourcommand instead.
2. ssh running local script: ssh username@hostname 'bash -s' < your.local.script.sh
3. ssh running local script with paraemters: ssh username@hostname < your.local.script.sh 'bash -s' yourparam1 yourparam2 doesn't work, you should runssh username@hostname < your.local.script.sh 'bash -s' -- yourparam1 yourparam2
4. make your fonts configuration work without a reboot: sudo fc-cache -fv