Thore Strassburg weilbith

This configuration is not maintained anymore. You should think twice before using it, Breaking change and security issue will likely eventually happens as any abandonned project.

	" This was taken from
	" https://github.com/tjdevries/config_manager/blob/master/xdg_config/nvim/after/plugin/_load_lua.vim

	let s:load_dir = expand('<sfile>:p:h:h:h')
	exec printf('luafile %s/lua/init.lua', s:load_dir)

	vim ~/.ctags
	--langdef=Solidity
	--langmap=Solidity:.sol
	--regex-Solidity=/^contract[ \t]+([a-zA-Z0-9_]+)/\1/c,contract/
	--regex-Solidity=/[ \t]*function[ \t]+([a-zA-Z0-9_]+)/\1/f,function/
	--regex-Solidity=/[ \t]*event[ \t]+([a-zA-Z0-9_]+)/\1/e,event/
	--regex-Solidity=/[ \t](struct[ \t]+[a-zA-Z0-9_]+)([ \t]\{)/\1/v,variable/
	--regex-Solidity=/[ \t](enum[ \t]+[a-zA-Z0-9_]+)([ \t]\{)/\1/v,variable/
	--regex-Solidity=/[ \t]mapping[ \t]+\(([a-zA-Z0-9_]+)[ \t]=>[ \t]*([a-zA-Z0-9_]+)\)[ \t]+([a-zA-Z0-9_]+)/\3 (\1=>\2)/m,mapping/

	"""
	This module implements an Ansible plugin that is triggered at the start of a playbook.

	The plugin dynamically generates a tag for each role. Each tag has the same name as its role.
	The advantage of this is that it saves you some boilerplate, because you don't have to wrap
	all tasks of a role in an additional block and assign a tag to that.
	Additionally, it works automatically when you add new roles to your playbook.

	Usage is exactly the same as without this plugin:

	set realname = "Guillaume Brogi"
	set from = "[email protected]"
	set use_from = yes
	set user_agent = yes

	set sendmail = "/usr/bin/msmtp"
	set editor = "nvim +/^$/+1 +':noh'"
	set charset = "utf-8"
	set send_charset = "utf-8"
	set assumed_charset = "utf-8"

	interface Option<T> {
	map <U>(fn: (a: T) => U): Option<U>;
	isSome(): boolean;
	isNone(): boolean;
	isSomeAnd(fn: (a: T) => boolean): boolean;
	isNoneAnd(fn: () => boolean): boolean;
	unwrap(): T;
	unwrapOr(def: T): T;
	unwrapOrElse(f: () => T): T;
	map<U>(f: (a: T) => U): Option<U>;