惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

宝玉的分享
宝玉的分享
H
Hackread – Cybersecurity News, Data Breaches, AI and More
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
小众软件
小众软件
月光博客
月光博客
D
DataBreaches.Net
L
LangChain Blog
美团技术团队
S
SegmentFault 最新的问题
MyScale Blog
MyScale Blog
大猫的无限游戏
大猫的无限游戏
博客园 - 司徒正美
aimingoo的专栏
aimingoo的专栏
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
H
Help Net Security
阮一峰的网络日志
阮一峰的网络日志
Y
Y Combinator Blog
I
InfoQ
U
Unit 42
Microsoft Azure Blog
Microsoft Azure Blog
J
Java Code Geeks
博客园 - 三生石上(FineUI控件)
腾讯CDC
Martin Fowler
Martin Fowler

abyss.fish thoughts

abyss * your_dotfiles_are_not_a_distro abyss * tree-style_invite_systems_reduce_AI_slop abyss * all_eyes_on_minneapolis j3s.sh j3s.sh j3s.sh j3s.sh j3s.sh j3s.sh j3s.sh j3s.sh j3s.sh
j3s.sh
2023-10-06 · via abyss.fish thoughts

↵return

shell tip: print json with printf

another pufferfish drawn by rekka

shell tip: print json with printf 2023-10-06 i am commonly consulted when people are having strange issues with shell. one of the most common issues that shows up is when people try printing their json in shell. printing json might seem straightforward at first, just: $ echo '{"name": "jes", "sign": "aquarius"}' {"name": "jes", "sign": "aquarius"} but inevitably, variables show up: $ echo '{"name": "$name", "sign": "$sign"}' {"name": "$name", "sign": "$sign"} <-- this output is very broken at this point, the shell user realizes that they need double quotes in order to make variables interpolate properly. the user then commits one of two *cardinal* sins: sin 1: the eternal double-quote swamp $ echo "{\"name\": \"$name\", \"sign\": \"aquarius\"}" {"name": "jes", "sign": "aquarius"} if you write anything as ugly as the abomination above in shell, you are sending a clear signal that you do not care about yourself. you are condemning yourself to wade through the double-quote swamp for eternity. and you will deserve it. '\"\"\"\"\"\""\""\"'\\""\"""\\""\""\"\\\"\""\""\"""\\""\\" ^ a small portion of the eternal double-quote swamp ^ sin 2: the long ugly HEREDOC $ cat <<-EOF {"name": "$name", "sign": "$sign"} EOF {"name": "jes", "sign": "aquarius"} the HEREDOC is more forgivable, but it takes up 2 unnecessary lines, and it's much harder to recall on-the-fly. and frankly, it looks pretty strange. and god forbid if you have to use a heredoc in an indented block. kiss your nice orderly indentation goodbye: if blah; then cat <<-EOF {"name": "$name", "sign": "$sign"} EOF fi there is a better way! we just need to bust out our old dusty friend *printf* printf offers several advantages over echo: - many languages (C, Go) have a printf equivalent, so it feels familiar - printf behavior does not differ across systems (it is posix compliant) - printf handles escape sequences (printf "hello\nworld\n") - printf can trivially handle json witness, as we print the same json text using printf: $ printf '{"name": "%s", "sign": "%s"}' "$name" "$sign" {"name": "jes", "sign": "aquarius"} & there you have it! nice orderly json using an easy to remember command, with no-fuss variable injection built-in. i hope that this tip saves you some pain! love, jes

follow me on mastodon or bluesky!

last updated 2023-10-06T00:00:00.000Z