| package main | |
| import ( | |
| "net" | |
| "os" | |
| ) | |
| func main() { | |
| strEcho := "Halo" | |
| servAddr := "localhost:6666" | |
| tcpAddr, err := net.ResolveTCPAddr("tcp", servAddr) |
| "Alfred 2"; idea;Thunder*; iTerm; Terminal;php; Dropbox; Sparrow; "Sequel Pro"; python; ruby; wget; curl; GitHub; git-remote-https; npm; node; perl;prl*;itunes; sftp; whois;traceroute;stroke;ssh;ALiWangwang;MacUpdate*;git*;Git;fzs*;mail;flickr*;xulr*;imess*;com.apple.im*;Airmail;Adium;Prot*;Tokens;Ali*;Lite*;file*;ssh;ftp;Adobe*;PDApp*;Creative*;Vbox*;xulrunner;Virtual*;PDApp;Bit*;Domainers;fire*;plugin*;Atom*;Tokens;.com.realmacsoftware*;Xcode;java;httpd; |
| # I'm getting Amethyst for my dual-monitor work setup | |
| # | |
| # For laptop, I'm replacing good-old Spectacle with Slate | |
| # just for its Grid / Hint and versionable configuration | |
| # to start with. | |
| # https://github.com/jigish/slate | |
| bind 0:alt,cmd relaunch | |
| bind 1:alt,cmd grid 0:6,4 | |
| bind 2:alt,cmd hint |
$ text-builder -index /path/to/index.txt
Or run $ sh build-all to build all your index files.本人不提供任何保证和技术支持，使用者自负风险。
There are no guarantees, no any support. Use it at your own risk.
| [General] | |
| skip-proxy = 127.0.0.1, 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12, 100.64.0.0/10, localhost, *.local, ::ffff:0:0:0:0/1, ::ffff:128:0:0:0/1 | |
| bypass-tun = 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12 | |
| # dns-server = 119.29.29.29, 223.5.5.5, 114.114.114.114 | |
| loglevel = notify | |
| [Proxy] | |
| BJ-All = custom | |
| BJ-HK-Azure = custom | |
| BJ-US-Azure = custom |
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
