This is really just meant to be goofy, noone should use this instead of a mouse.
Add these lines to your i3 config.
bindsym $mod+Mod1+h exec xdotool mousemove_relative -p 270 10
| Begin by enclosing all thoughts within <thinking> tags, exploring multiple angles and approaches. | |
| Break down the solution into clear steps within <step> tags. Start with a 20-step budget, requesting more for complex problems if needed. | |
| Use <count> tags after each step to show the remaining budget. Stop when reaching 0. | |
| Continuously adjust your reasoning based on intermediate results and reflections, adapting your strategy as you progress. | |
| Regularly evaluate progress using <reflection> tags. Be critical and honest about your reasoning process. | |
| Assign a quality score between 0.0 and 1.0 using <reward> tags after each reflection. Use this to guide your approach: | |
| 0.8+: Continue current approach | |
| 0.5-0.7: Consider minor adjustments | |
| Below 0.5: Seriously consider backtracking and trying a different approach |
| ## General info: | |
| # Function starts with @ | |
| # Variable starts with $ | |
| # Return of the most recently run function made by $@ | |
| # Key comments marked with ## | |
| ## Version of IV must be set first | |
| ~version: "2.1" | |
| # Telegram doesn't support JW Player which is used in videoheaders |
| # This is something that I always forget and had a surprisingly hard time finding (or better yet, understanding). Here's the | |
| # scenario: a colleague creates a new kubernetes cluster, named" cluster-foo.example.com". You want to look at it (for | |
| # troubleshooting, updating the deployment, whatever). To get your kubectl installation to "see" the new cluster, take the | |
| # following steps: | |
| # ASSUMPTION: You have pointed kops to some location where the cluster configurations are stored | |
| # (I have this in my ~/.bash_profile): | |
| export KOPS_STATE_STORE=s3://example-state-store | |
| # Use kops to get the list of clusters |
Create file /etc/systemd/system/[email protected]. SystemD calling binaries using an absolute path. In my case is prefixed by /usr/local/bin, you should use paths specific for your environment.
[Unit]
Description=%i service with docker compose
PartOf=docker.service
After=docker.service| // iMacro CheatSheet - Command Reference | |
| // http://wiki.imacros.net/Command_Reference | |
| // iMacros supports 3 types of variables: | |
| // * The macro variables !VAR0 thru !VAR9. They can be used with the SET and ADD command inside a macro. | |
| // * Built-in variables. They contain certain values set by iMacros. | |
| // * User-defined variables. They are defined in-macro using the SET command. | |
| let g:ctrlp_buffer_func = { 'enter': 'CtrlPMappings' } | |
| function! CtrlPMappings() | |
| nnoremap <buffer> <silent> <C-@> :call <sid>DeleteBuffer()<cr> | |
| endfunction | |
| function! s:DeleteBuffer() | |
| let path = fnamemodify(getline('.')[2:], ':p') | |
| let bufn = matchstr(path, '\v\d+\ze\*No Name') | |
| exec "bd" bufn ==# "" ? path : bufn |
| /** | |
| * Author: Michael Weibel <[email protected]> | |
| * License: MIT | |
| */ | |
| var passport = require('passport') | |
| , StrategyMock = require('./strategy-mock'); | |
| module.exports = function(app, options) { | |
| // create your verify function on your own -- should do similar things as |