Atom as a code editor just becomes slower and slower with the burden of massive plugins, requiring near 15s on my MBP to initially display file contents. In comparison, VSCode with similar extensions just takes 5s to show file text upon launch. There must be some architectural issues in the Atom startup process, as both are based on Electron. The memory/cpu footprint also has huge differences as this old post shows. Atom sometime even stops responding and asks to wait for editor window to run.
While speed performance is an important factor, all kinds of mysterious long pending bugs are really killing it. In my scenario, the vertical scrollbar sometime just turns into a white bar. Some issues are reported, analyzed, but just doesn’t reach a fix. And the git interface cannot stage lines for files with unicode filename, but is only able to stage the whole file. The nuclide file tree is unusable as constantly steals text editor focus! All of such problems are long existed nuisances to bear with.
Fortunately, VSCode now also enjoys the affluence of extensions. Almost all of my Atom plugins find their counterparts in VSC. The only advantage of Atom is the beautifulness in contrast to the VSCode default theme’s coarseness (the blue status bar is horrible), but hopefully the Atom One Dark theme and keymap extensions are the cure.
Just after Microsoft successfully bought Github, it seems the right time to switch from Atom to VSCode finally.
Test Analytics is a quite good project from Google for testing analysis practice. It is open sourced at http://code.google.com/p/test-analytics/. However the documentation is quite limited and not straight forward for configuration and setup.
Just spend quite a few hours to make it run on GAE with Google Apps account. Here is the steps:
Create target GAE application in GAE (https://appengine.google.com) with your Google Apps account, select user authentication to Google Apps and set your apps domain (i.e. xxxx.com)
In your Google Apps Administrator Homepage (https://www.google.com/a/xxxx.com/), add services with GAE application id set to the created one
Download or git clone the test analytics project code
In the pom.xml at project dir, add following lines into the maven-gae-plugin <plugin> element:
Just encounter some build problem in 10.7 with latest sunpinyin git:
1)when compiling xib there’s a warning says TableViewColumns identifier expects NSString in 10.7, it could be fixed by manually set the TableViewColumn’s identifier to a string in Interface Builder. And note: manually set the english version xib, the zh_CN version will be auto generated
2)an build error suggest cp’s usage: in the build phrase, add quotation mark with the directory part, there could be space in the path
For Adium 1.4.2, the chat transcript log doesn’t appear in spotlight search result even though the word is exactly in the chat logs. Yeah, it’s no big deal, but a bit annoyance, especially when Adium’s own transcript search won’t return good results.
After some research, a few tryouts were taken: Using mdimport to force spotlight reindex the logs folder seems not work. Followed instruction of this ticket to move the chat logs folder to user documents folder, still not work. Then, this ticket has the culprit bug revealed. The
GetMetadataForXMLLog function doesn’t handle the chatlog bundle correctly. Just appending the xml path before parsing the xml file and rebuilding the project will exactly fix the spotlight search issue.
Therefore the reverse steps are the final solution:
1) Get my bug fixed version of AdiumSpotlightImporter (or compile the bugfix version by yourself), unzip and copy to /Applications/Adium.app/Contents/Library/Spotlight, and make sure the importer is used by spotlight in “mdimport -L”
2) Move the adium chat log folder to your documents folder as the above ticket shows, so that spotlight will not exclude it under the system library folder
3) mdimport “your new adium chat log folder” to merge into the spotlight index
4) Search words in spotlight, the adium result now will show in search results under the mail category
It’s quite sad that QSB (Google Quick Search Box) doesn’t update anymore, according to this thread, it goes to maintain mode. QSB is quite intuitive and allows mutlibyte/unicode text input that Quick Silver lacks, and if you have the services plugin to utilize OSX’s services, you can almost do anything with QSB in Mac like with QuickSilver’s plugins. Especially, you can add your custom services with automator and apple script! However, the promised 2.0.3789 compatible services.hgs plugin might not come in a foreseeable future.
Well, Do It Yourself.
Just spent some efforts last week in figuring out how to make the old mkhl plugin to work in QSB 2.0. Although not well documented, QSB service plugin works finally. Thanks to mkhl and qsb-mac’s good coding. You can now download the release version from my following link. In order to avoid constantly read service info, this plugin load info upon start, therefore restart QSB to load service info if new service is installed.
If you find QSB useful, you may also contribute to it and provide bugfixes. Have fun for the updated services plugin on QSB 2.0.3789!