| " vim-bootstrap 2021-05-31 12:00:51 | |
| "***************************************************************************** | |
| "" Vim-Plug core | |
| "***************************************************************************** | |
| let vimplug_exists=expand('~/.vim/autoload/plug.vim') | |
| if has('win32')&&!has('win64') | |
| let curl_exists=expand('C:\Windows\Sysnative\curl.exe') | |
| else | |
| let curl_exists=expand('curl') |
| # using-wget-with-socks-proxy | |
| # This should work for everything includeing curl, pip, pipenv, etc | |
| # TLDR: Use proxychains (https://github.com/haad/proxychains) | |
| ## INSTALL PROXY CHAINS ## | |
| $ sudo apt update -y | |
| $ sudo apt install proxychains | |
| ## EDIT PROXYCHAINS CONFIG ## |
Services declared as oneshot are expected to take some action and exit immediatelly (thus, they are not really services,
no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.
Let's create a example foo service that when started creates a file, and when stopped it deletes it.
Create executable file /opt/foo/setup-foo.sh:
[ Update 2020-05-31: I won't be maintaining this page or responding to comments anymore. The list of supporting software reflects the known state as of this date. ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
Suppose you have weird taste and you absolutely want:
sudo dnf install dkms
sudo dnf install kernel-devel
| # Synchronize history between bash sessions | |
| # | |
| # Make history from other terminals available to the current one. However, | |
| # don't mix all histories together - make sure that *all* commands from the | |
| # current session are on top of its history, so that pressing up arrow will | |
| # give you most recent command from this session, not from any session. | |
| # | |
| # Since history is saved on each prompt, this additionally protects it from | |
| # terminal crashes. |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j