| description | tools | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4.1 Beast Mode |
|
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
| -- put this file somewhere in your nvim config, like: ~/.config/nvim/lua/config/lua-lsp.lua | |
| -- usage: require'lspconfig'.sumneko_lua.setup(require("config.lua-lsp")) | |
| local library = {} | |
| local path = vim.split(package.path, ";") | |
| -- this is the ONLY correct way to setup your path | |
| table.insert(path, "lua/?.lua") | |
| table.insert(path, "lua/?/init.lua") |
Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.
If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.
| %YAML 1.2 | |
| --- | |
| name: PHP | |
| file_extensions: | |
| - php | |
| - php3 | |
| - php4 | |
| - php5 | |
| - php7 | |
| - phps |
| # Reconstructed via infocmp from file: /usr/share/terminfo/t/tmux-256color | |
| tmux-256color|tmux with 256 colors, | |
| OTbs, OTpt, am, hs, km, mir, msgr, xenl, AX, G0, | |
| colors#256, cols#80, it#8, lines#24, pairs#32767, U8#1, | |
| acsc=++\,\,--..00``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~, | |
| bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l, | |
| clear=\E[H\E[J, cnorm=\E[34h\E[?25h, cr=^M, | |
| csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H, | |
| cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C, | |
| cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\EM, |
The [React docs][condoc] give some example use cases for context:
Context is designed to share data that can be considered “global” for a tree of React components, such as the current authenticated user, theme, or preferred language.
The common property of these use cases is that data like the current theme doesn't change often and needs to be shared deep down the component tree, which would be cumbersome with "[prop drilling][drill]". Something else that needs to be shared everywhere is the application state when using a "single source of truth" pattern, so it would follow that the context API would help with that as well, but there's a catch: components that use context will rerender every time that the provided value changes, so sharing the whole application state through context would cause excessive render lifecycles.
| // create a bookmark and use this code as the URL, you can now toggle the css on/off | |
| // thanks+credit: https://dev.to/gajus/my-favorite-css-hack-32g3 | |
| javascript: (function() { | |
| var elements = document.body.getElementsByTagName('*'); | |
| var items = []; | |
| for (var i = 0; i < elements.length; i++) { | |
| if (elements[i].innerHTML.indexOf('* { background:#000!important;color:#0f0!important;outline:solid #f00 1px!important; background-color: rgba(255,0,0,.2) !important; }') != -1) { | |
| items.push(elements[i]); | |
| } | |
| } |
| " gq wrapper that: | |
| " - tries its best at keeping the cursor in place | |
| " - tries to handle formatter errors | |
| function! Format(type, ...) | |
| normal! '[v']gq | |
| if v:shell_error > 0 | |
| silent undo | |
| redraw | |
| echomsg 'formatprg "' . &formatprg . '" exited with status ' . v:shell_error | |
| endif |
FOREWORDS
I don't mean the snippet at the bottom of this gist to be a generic plug-n-play solution to your search needs. It is very likely to not work for you or even break things, and it certainly is not as extensively tested and genericised as your regular third-party plugin.
My goal, here and in most of my posts, is to show how Vim's features can be leveraged to build your own high-level, low-maintenance, workflows without systematically jumping on the plugins bandwagon or twisting Vim's arm.
