Monday, November 11, 2013

Be Aware Of the Shell You Are Using

I used to get this wired error when I was trying to redirect both stdout and stderr to a file. What I did was, 

    "ls > foo.log 2>&1"

If you search for output redirecting, all articles online would tell you this is correct. However my shell kept complaining "Ambiguous output redirect."

This is a csh/tcsh error message for which the correct redirection is supposed to be
    "ls >& foo.log"

So, apparently I was using a csh/tcsh, rather than BASH shell. The former was in BASH syntax.

To find out what shell you are using, type
    "ps -p $$" on whatever shell you are working on, it will tell you.

Wednesday, March 27, 2013

[SOLVED]fastboot wired errors


Problem:

When trying to flash a device using fastboot, i.e. via commands "fastboot -w flashall", get errrors like

"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"

or

"error: error: could not load android-info.txt"

Solution:

First, you want to make sure the environment variable ANDROID_PRODUCT_OUT is properly set to the out/target/product/your_product/ directory

Second, double check if all images(boot.img, system.img, userdata.img, caches.img, recovery.img) are there in that directory and an text file "android-info.txt" exits.

If all images are generated and ANDROID_PRODUCT_OUT is set, then you might have to flash images one by one. It seems that the "flashall" command is problematic sometimes.

Commands:

fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
...

Thursday, March 7, 2013

[SOLVED]""required virtual size does not fit available size: requested=(2304, 768), minimum=(320, 200), maximum=(1280, 1280)""

Platform:
                 Ubuntu 11.10(or other releases, not sure)
Diagnosis:
                 Unable to set up dual(multi)-displays, with an error message like ""required virtual size does not fit available size: requested=(2304, 768), minimum=(320, 200), maximum=(1280, 1280)""
Solution:
                 Modify /etc/X11/xorg.conf file, to set the "Virtual" parameters properly.
                 sudo vim /etc/X11/xorg.conf
                 Locate section "Screen", create a subsection "Display" with a parameter "Virtual" with the values indicated as required in the error message, e.g. 2304 and 768 here.
                 Subsection "Display"
                ... // other parameters if any
               Virtual 2646 1024
         EndSubsection
                  Log out and log in, go to "Displays...", uncheck "Mirror displays", apply.

[COPIED]Install fcitx on Ubuntu 11.10

The default repositories of Ubuntu 11.10 cannot find fcitx. You need to install through ppa.


小企鹅fcitx的安装方法:
fcitx与scim输入法有冲突,安装之前首先确认scim是否安装,如果安装了scim,就先卸载scim。
1
sudo apt-get purge scim
然后开始安装fcitx:
1
2
3
4
5
6
7
8
9
sudo add-apt-repository ppa:fcitx-team/nightly

sudo apt-get update

sudo apt-get install fcitx fcitx-config-gtk fcitx-sunpinyin

sudo apt-get install fcitx-table-all

im-switch -s fcitx -z default #设为默认输入法
最后注销用户再重新登录,小企鹅fcitx输入法就生效了。
fcitx支持自定义皮肤。现在网上有一些很漂亮的fcitx皮肤,可惜这些皮肤只支持fcitx 4.0,通过PPA源安装的fcitx是最新版本fcitx 4.1.2, 我只找到一款支持fcitx 4.1.2的皮肤 – 四叶草:四叶草 fcitx 4.1.2皮肤下载地址。下载完,解压文件,然后把解压出来的文件夹放到~/.config/fcitx/skin/文件夹下,如果没有skin文件夹,就新建一个。
fcitx 最新版4.1.2 四叶草皮肤 截图
如果想让老皮肤fcitx 4.0支持最新版本的fcitx 4.1.2,有两种解决方法:
1.解压皮肤,然后按照上面的提示信息修改文件,按照你使用fcitx的版本号进行修改
2.使用你机器上fcitx的默认皮肤,然后打开fcitx配置工具,参照现有皮肤参数一点点修改…

Source Link:

[SOVLED]"E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages."

Platform:
                  Ubuntu 11.10(or other releases, not sure)
Diagnosis:
                 A "Forbidden" sign shown at the notification center, with an error message "E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages."

Reason:
                Some package installed have unmet dependencies.
Solution:
                sudo apt-get dist-upgrade
                Command above gives you the information that which package(s) are problematic.
                sudo apt-get remove problematic_package(s)

Sunday, January 20, 2013

[Copied]Using Spell Checking in Vim


Mark Twain has been quoted as saying that he respected a person who could spell a word more than one way. Unfortunately, Twain's enthusiasm for creative spelling isn't widely shared today, at least in the professional world. If you need a little help in the spelling department, but prefer the old school way of editing text, you can turn to Vim's spelling support.
Support for spell checking was added in Vim 7. Before that, a few scripts were available to hack spell checking support into Vim — or you could do what I did and use ispell or aspell, but inline spell checking is much nicer.
If you're new to Vim and/or using Vim in text mode, it's not obvious that Vim even supports spell checking. But it does, and it's easy to use once you turn it on. You'll need to be in command mode and switch to last line mode, then run this:
:set spell spelllang=en_us
You might not want to be that specific, or you might want a different region. The "en_us" specifies English, U.S. style. You might want to use "en_ca" instead, if you're in Canada, or "en_gb" for Great Britain, or "en_au" for Australia. And, of course, this works for other languages as well.
If you're using Vim to write code and prose, you might want to turn spell checking on only in the local buffer. To do that, use:
:setlocal spell spelllang=en_us
Once you've set this, Vim will highlight misspelled words. If you're using Vim in text mode, you should see the entire word highlighted, or if you're using Gvim, you should see a squiggly underline for any word that is misspelled.
Vim does more than just highlight misspelled words, it actually categorizes misspelled words, it also highlights rare words, words that aren't capitalized (but should be), and words that have the wrong spelling for the specified region. For example, I've set Vim to check for U.S. spelling (spelllang=en_us), so it should highlight words that are spelled correctly in another region but might be considered incorrect for the local region.
Vim uses different colors for each type of word. This may vary depending on the colors you have set up in your terminal or how you have Gvim set up, but on my system I see misspelled words highlighted with red, an orange for rare words, blue for words that aren't capitalized, and so on.
Getting tired of seeing the highlighting? You may want to turn spell checking off if you're working with code or something like that. Use the nospell directive to turn this off:
:set nospell

Using Spellchecking

Spell checking wouldn't be very useful if you didn't have any help correcting the misspelled words, or a way to tell the program that the word is actually correct. Let's start with correcting words.
To move to a misspelled word, use ]s and [s. The ]s command will move the cursor to the next misspelled word, the [s command will move the cursor back through the buffer to previous misspelled words.
Once the cursor is on the word, use z=, and Vim will suggest a list of alternatives that it thinks may be correct. For instance, if I highlight autocompletion and then use z=, I see something like figure 1:
Figure 1: Word suggestions in Vim
Figure 1: Word suggestions in Vim

Just hit Enter if none of the suggestions work, or enter the number for the correct word.
What if Vim is wrong, and the word is correct? Use the zg command and Vim will add it to its dictionary. Simple as pie. You can also mark words as incorrect using zw.
If you don't want to keep telling Vim explicitly every time you restart to turn on spelling, just add the following to your .vimrc:
set spell spelllang=en_us
Substitute the appropriate region, of course.
Vim's combination of syntax highlighting, autocompletion (using CTRL-p and CTRL-n), abbreviations and mappings, and spell-checking makes it a killer editor to write in. Even when I need to share materials with clients in ODF or Word format, I usually write first in Vim with HTML and then copy and paste into OpenOffice.org, which usually handles the formatting just fine.
Have some writing tips with Vim you'd like to share? Something you'd like to know how to do in Vim? Speak up in the comments!

Source Link: https://www.linux.com/learn/tutorials/357267:using-spell-checking-in-vim

PS, you need to have a ~/.vim/spell directory for the command "zg" to work. Vim uses this directory to store the spelling dictionary.

Comnand: mkdir -p ~/.vim/spell