-
To provide Nix repositories with an easy and standard way to reference other Nix repositories.
-
To allow such references to be queried and updated automatically.
-
To provide a replacement for
nix-channel,NIX_PATHand Hydra
tags: Auburn, Auburn University, WPA2, WPA2 Enterprise
Auburn University is gracious enough to provide instructions to Ubuntu users on how to connect their hosts to the Auburn University WiFi Network.
Many Universities use WPA2 Enterprise authentication on their networks. This allow you to track WHO is connected where and have granular control over who's able to access the WiFi network.
For tinkerers and experimenters with Raspberry Pi, Particle Photon, and other embedded systems, this poses a problem because many simplier IoT devices do not support WPA2 Enterprise natively or not without some hassle.
Raspbian Jesse and earlier will display a WPA2 Enterprise network from its dropdown list, but it will be greyed out. The workaround is to manually connect to it:
| var EMAIL_DRAFTED = "EMAIL DRAFTED"; | |
| function draftMyEmails() { | |
| var sheet = SpreadsheetApp.getActiveSheet(); // Use data from the active sheet | |
| var startRow = 2; // First row of data to process | |
| var numRows = sheet.getLastRow() - 1; // Number of rows to process | |
| var lastColumn = sheet.getLastColumn(); // Last column | |
| var dataRange = sheet.getRange(startRow, 1, numRows, lastColumn) // Fetch the data range of the active sheet | |
| var data = dataRange.getValues(); // Fetch values for each row in the range | |
| Basic | |
| ===== | |
| [Shift]+[Mod]+[Enter] - launch terminal. | |
| [Mod]+[b] - show/hide bar. | |
| [Mod]+[p] - dmenu for running programs like the x-www-browser. | |
| [Mod]+[Enter] - push acive window from stack to master, or pulls last used window from stack onto master. | |
| [Mod] + [j / k] - focus on next/previous window in current tag. |
- Learn-Vim -- A modular tutorial on the Vim editor.
- Creating an ag.vim script -- A critically-acclaimed gist on creating a grep-wrapper for Vim.
- Managing plugins in Vim -- A comprehensive gist on different ways of managing plugins in Vim.
- Better global searches -- Wrapping the
:gcommand in Vim to behave in a more useful way.
- Vim-Commentor -- An easy way to comment (and uncomment) blocks of code in Vim.
| <div class="question-text">{{Question}}</div> | |
| <div class="all-variants to-split">{{AllVariants}}</div> | |
| <div id="splitted-question"></div> | |
| <script language="javascript"> | |
| var FB_DB_NAME = '...'; | |
| // Renders possible answer variants. |
| # ------------------------------------------------------------------------------ | |
| # tlp - Parameters for power saving | |
| # See full explanation: http://linrunner.de/en/tlp/docs/tlp-configuration.html | |
| # dir: /etc/default/tlp | |
| # Hint: some features are disabled by default, remove the leading # to enable | |
| # them. | |
| # Set to 0 to disable, 1 to enable TLP. |
| # inciude" studio.h" | |
| main() | |
| { | |
| printf(for,i>=1,/n); | |
| for(%n,%m,%k,/); | |
| printf(for,x,x++;y,y--;/); | |
| studio(for"n,m,k,x,y";/n,m,k,x,y/); | |
| printf("0<=x<m;0<=y<m;y<x); | |
| } | |
| { |
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