(C-x means ctrl+x, M-x means alt+x)
The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:
| // Using Singleton on Kotlin | |
| public object MySingleton { | |
| public fun foo() { | |
| } | |
| } | |
| // And use it on Kotlin | |
| MySingleton.foo() |
| package id.bitcase.ocafe.utility; | |
| import android.bluetooth.BluetoothAdapter; | |
| import android.bluetooth.BluetoothDevice; | |
| import android.bluetooth.BluetoothSocket; | |
| import android.graphics.Bitmap; | |
| import android.os.AsyncTask; | |
| import android.util.Log; | |
| import java.io.IOException; |
There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.
The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.
When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].
When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.
| $ ffmpeg -i input.mp4 -vcodec h264 -acodec mp2 output.mp4 |
| class Adder implements Function { | |
| call(int a, int b) => a + b; | |
| } | |
| class Incrementer implements Function { | |
| int _amt; | |
| Incrementer(this._amt); | |
| call(int a) => a + _amt; | |
| } |
| void main() { | |
| runApp(MyApp()); | |
| } | |
| class MyApp extends StatelessWidget { | |
| @override | |
| Widget build(BuildContext context) { | |
| return MaterialApp( | |
| title: 'Flutter Demo', | |
| theme: ThemeData( |