- Copy the file below into one called
testez.yml
- In
selene.toml
, replacestd = "roblox"
withstd = "roblox+testez"
(setq show-paren-style 'expression) | |
(show-paren-mode 2) | |
(menu-bar-mode -1) | |
(tool-bar-mode -1) | |
(setq make-backup-files nil) ; Don't want any backup files | |
(setq auto-save-list-file-name nil) ; Don't want any .saves files | |
(setq auto-save-default nil) ; Don't want any auto saving |
--[[ | |
ProFi v1.3, by Luke Perkin 2012. MIT Licence http://www.opensource.org/licenses/mit-license.php. | |
Example: | |
ProFi = require 'ProFi' | |
ProFi:start() | |
some_function() | |
another_function() | |
coroutine.resume( some_coroutine ) | |
ProFi:stop() |
This is a quick guide to OAuth2 support in GitHub for developers. This is still experimental and could change at any moment. This Gist will serve as a living document until it becomes finalized at Develop.GitHub.com.
OAuth2 is a protocol that lets external apps request authorization to private details in your GitHub account without getting your password. All developers need to register their application before getting started.
- Redirect to this link to request GitHub access:
This is a guide to Vim Script development for Python developers. Sample code for the various expressions, statements, functions and programming constructs is shown in both Python and Vim Script. This is not intended to be a tutorial for developing Vim scripts. It is assumed that the reader is familiar with Python programming.
For an introduction to Vim Script development, refer to usr_41.txt, eval.txt and Learn Vimscript the Hard Way
For a guide similar to this one for JavaScript developers, refer to Vim Script for the JavaScripter
This guide only describes the programming constructs that are present in both Python and Vim. The constructs that are unique to Vim (e.g. autocommands, [key-mapping](https://vimhelp.org/map.txt.html#key-m
I did not submit this to Hacker News and did not intend that this post would have high circulation but have no real problem with it being there or with it having such. I have more recent comments below. This post is from January 2020 and predates the Modular Font Editor K (MFEK) project.
I have not worked on Rust projects in quite a while, and don't know if I ever will again. I feel many crate maintainers are way too perfectionist, for example, despite all the developer hours that went into this PR, it took the effort within years to be (halfway) merged.
There's always a reason not to merge, isn't there? It would be better done with a new nightly language feature, or the function signature should have a where clause, or the documentation is not perfect. There's always a new nit to pick in the world of Ru
#!/usr/bin/env bash | |
help_string=$(cat <<EOF | |
Usage: $0 [-h|-l] APPLICATION | |
Set a video player as the default. | |
Example: | |
# List candidate desktop files for media players. |
#!/usr/bin/env python3 | |
trans_dict = { | |
'\U0000f500': '\U000f0001', # vector_square | |
'\U0000f501': '\U000f0003', # access_point | |
'\U0000f502': '\U000f0002', # access_point_network | |
'\U0000f503': '\U000f0004', # account | |
'\U0000f504': '\U000f0005', # account_alert | |
'\U0000f505': '\U000f0006', # account_box | |
'\U0000f506': '\U000f0007', # account_box_outline |