This text is the section about OS X Yosemite (which also works for macOS Sierra) from https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/#mac-os-x
The last time i visited this link it was dead (403), so I cloned it here from the latest snapshot in Archive.org's Wayback Machine https://web.archive.org/web/20170523131633/https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/
macOS has ncurses version 5.7 which does not ship the terminfo description for tmux. There're two ways that can help you to solve this problem.
Instead of tmux-256color, use screen-256color which comes with system. Place this command into ~/.tmux.conf or ~/.config/tmux/tmux.conf(for version 3.1 and later):
| #!/usr/bin/python3 | |
| from functools import partial | |
| def colors16(): | |
| for bold in [0, 1]: | |
| for i in range(30, 38): | |
| for j in range(40, 48): | |
| print(f'\x1b[{bold};{i};{j}m {bold};{i};{j} |\x1b[0m', end='') | |
| print() |
React's official website makes a banner, which offers visitors a way to provide humanitarian aid to Ukraine.
React的官方网站做了一个横幅，为访问者提供了向乌克兰提供人道主义援助的途径。
Then, many people went to the React.js Github repository and opened lots of spam issues with anti-US and anti-Ukrainian comments in an apparent form of digital protest. The messages are in English and Mandarin.
然后，很多人到React.js Github 仓库中开了很多带有反美国和反乌克兰 issue，进行一种数字化的抗议。这些信息是用英语和普通话写的。
| local ls = require("luasnip") | |
| local fmt = require("luasnip.extras.fmt").fmt | |
| local s = ls.snippet | |
| local i = ls.insert_node | |
| local f = ls.function_node | |
| local d = ls.dynamic_node | |
| local sn = ls.snippet_node | |
| local rep = require("luasnip.extras").rep | |
| -- Get a list of the property names given an `interface_declaration` |
tl;dr: If you want to just know the method, skip to How to section
Clangd is a state-of-the-art C/C++ LSP that can be used in every popular text editors like Neovim, Emacs or VS Code. Even CLion uses clangd under the hood. Unfortunately, clangd requires compile_commands.json to work, and the easiest way to painlessly generate it is to use CMake.
For simple projects you can try to use Bear - it will capture compile commands and generate compile_commands.json. Although I could never make it work in big projects with custom or complicated build systems.
But what if I tell you you can quickly hack your way around that, and generate compile_commands.json for any project, no matter how compilcated? I have used that way at work for years, originaly because I used CLion which supported only CMake projects - but now I use that method succesfully with clangd and Neovim.
| -- Same with text node, used for function nodes | |
| local function text_same_with(args) | |
| return args[1] | |
| end | |
| -- Same with text node, used for dynamic nodes | |
| local function insert_same_with(args) | |
| return sn(nil, { | |
| i(1, args[1]), | |
| }) |
