| /** | |
| * Translates a HTMl page in the web l10n style from the Add-on SDK with | |
| * WebExtensions strings. | |
| * Large parts of the logic are very similar to the SDK implmentation. | |
| * All you have to do to use this in a document is load it. | |
| * | |
| * It supports some additional attributes: | |
| * - The "translate" attribute is fully respected (see | |
| * https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/translate) | |
| * - "data-l10n-nocontent" means that the text content of the element |
If you work across many computers (and even otherwise!), it's a good idea to keep a copy of your setup on the cloud, preferably in a git repository, and clone it on another machine when you need.
Thus, you should keep the .vim directory along with your .vimrc version-controlled.
But when you have plugins installed inside .vim/bundle (if you use pathogen), or inside .vim/pack (if you use Vim 8's packages), keeping a copy where you want to be able to update the plugins (individual git repositories), as well as your vim-configuration as a whole, requires you to use git submodules.
Initialize a git repository inside your .vim directory, add everything (including the vimrc), commit and push to a GitHub/BitBucket/GitLab repository:
cd ~/.vim
| <LexerType name="json" desc="JSON" ext=""> | |
| <WordsStyle name="DEFAULT" styleID="0" fgColor="E0E2E4" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle name="NUMBER" styleID="1" fgColor="FFCD22" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle name="STRING" styleID="2" fgColor="EC7600" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle name="STRINGEOL" styleID="3" fgColor="808080" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle name="PROPERTYNAME" styleID="4" fgColor="678CB1" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle name="ESCAPESEQUENCE" styleID="5" fgColor="FF8409" bgColor="293134" fontName="" fontStyle="1" fontSize="" /> | |
| <WordsStyle name="LINECOMMENT" styleID="6" fgColor="008000" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle name="BLOCKCOMMENT" styleID="7" fgColor="008000" bgColor="293134" fontName="" fontStyle="0" fontSize="" /> | |
| <WordsStyle |
| #! /usr/bin/env python3 | |
| import os.path | |
| import glob | |
| import sqlite3 | |
| import json | |
| def main(): | |
| styles_glob = os.path.expanduser('~/AppData/Roaming/Mozilla/Firefox/Profiles/*.default/stylish.sqlite'); | |
| styles_path = glob.glob(styles_glob)[0]; |
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.
On March 22, npm fired several members of the open source and community team for discussing workplace conditions and other labor organizing activities. As a result, core employee contributors to the npm cli were removed from the project, and others have left in solidarity or put their work on hold.
Multiple claims were filed with the NLRB on this matter. The NLRB has investigated and found sufficient evidence of validity to proceed. The National Labor Relations Act of 1935 protects US employees' right to engage in discussions of workplace concerns without threat of retaliation -- and awareness of the importance of how we treat each other is something I valued so much in collaborating with the cli team. How can we work together if we aren't free to discuss what we need?
It's disappointing for all of us to find the work we were doing interrup
In this gist, you can find the steps to run Minecraft 1.16.4 natively on Apple Silicon (AS), without needing Rosetta 2 translation of the dependencies (mainly LWJGL and related libraries).
While it's possible to use a launcher like MultiMC to have a prettier way to run the game on AS, it requires installing even more dependencies (like QT) which take time and are difficult to distribute. Therefore, I've put together a command line-based launcher tool using a couple shell & Python scripts.
To get up and running quickly, follow the steps below. Otherwise, for more detail, watch my YouTube video.
| /* | |
| Handy tools & articles for developing eslint rules: | |
| https://astexplorer.net/ | |
| https://www.webiny.com/blog/create-custom-eslint-rules-in-2-minutes-e3d41cb6a9a0 | |
| https://blog.maximeheckel.com/posts/how-to-build-first-eslint-rule/ | |
| Developing: | |
| (make changes) | |
| yarn add --dev file:./eslint && yarn eslint . | |
| */ |
