Depending on the terminal, execute in one of the following ways:
Direct reference to file:
sed -e $'s/\xC2\xA0/ /g' -e $'s/\xE2\x80\x8b//g' -i /path/to/your/filePipe file contents to sed
| setInterval(function() { | |
| let boring = document.querySelector('video'); | |
| let boringAudio = document.querySelector('audio'); | |
| if (boring != null) boring.currentTime = boring.duration | |
| if (boringAudio != null) boringAudio.currentTime = boringAudio.duration | |
| setTimeout(function() { | |
| //.navBtn_item .v .navBtn .nextButton |
Depending on the terminal, execute in one of the following ways:
Direct reference to file:
sed -e $'s/\xC2\xA0/ /g' -e $'s/\xE2\x80\x8b//g' -i /path/to/your/filePipe file contents to sed
tree-sitter. This will be enabled by default quite soon now. It is theoretically faster and more powerful than regex based grammars (the one described in this guide), but requires a steeper learning curve. My understanding is that regex based grammars will still be supported however (at least until version 2), so this guide can still be useful.
To enable it yourself, go to Settings -> Core and check Use Tree Sitter ParsersLinks for tree-sitter help:
tree-sitter: the main repotree-sitter-cli: converts a JavaScript grammar to the required C/C++ filesnode-tree-sitter: module to use Tree-sitter parsers in NodeJS| [user] | |
| name = Pavan Kumar Sunkara | |
| email = pavan.sss1991@gmail.com | |
| username = pksunkara | |
| [core] | |
| editor = vim | |
| whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol | |
| excludesfile = ~/.gitignore | |
| [sendemail] | |
| smtpencryption = tls |
| :map <F9> :e $MYVIMRC<CR> | |
| # or? | |
| :map <F9> :e $HOME/__vimrc<CR> | |
| # The first one should work on both vim and neovim |
| # This yaml file extends default theme. See https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc | |
| extends: default | |
| page: | |
| layout: portrait | |
| margin: [1in, 1in, 1in, 1in] | |
| size: Letter | |
| caption: | |
| align: center | |
| table: | |
| caption: |
Answer by Jim Dennis on Stack Overflow question stackoverflow
Your problem with Vim is that you don't grok vi.
You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).
The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:
0 go to the beginning of this line. y yank from here (up to where?)
I work as a full-stack developer at work. We are a Windows & Azure shop, so we are using Windows as our development platform, hence this customization.
For my console needs, I am using Cmder which is based on ConEmu with PowerShell as my shell of choice.
Yes, yes, I know nowadays you can use the Linux subsystem on Windows 10 which allow you to run Ubuntu on Windows. If you are looking for customization of the Ubuntu bash shell, check out this article by Scott Hanselman.