Friday, December 19, 2008
Friday, December 12, 2008
Tabbed terminal under Cygwin using mrxvt tabs
mrxvt is a multi-tabbed terminal emulator that does not depend on various toolkits in Gnome or KDE. And even though the download page of the materm wiki says "Cygwin - currently not available" ... You can get mrxvt up and running under Cygwin as follows:
1) Live on the edge and download the latest unstable version of mrxvt from here to the root directory of the c: drive.
2) In a cygwin bash shell do the following:
$ cd c:/
$ tar -zxf mrxvt-0.5.4.tar.gz
$ cd mrxvt-0.5.4
$ ./configure --enable-everything --disable-debug
$ make
$ make install
$ XWin -nolock -multiwindow -clipboard -silent-dup-error &
$ export DISPLAY=yourIpAddress:0
$ # for example: export DISPLAY=127.0.0.1:0
$ mrxvt -fn fixed -fg green -bg black -g 150x45 --highlightColor green -ls &
NOTE: Many other packages are required to be installed under cygwin for this procedure above to get mrxvt up and running ... here are a few off the top of my head:
1) Cygwin base install
2) gcc
3) make
4) autoconf
5) automake
6) libiconv
7) the entire X11 category of packages
8) all of the cygwin rxvt packages
9) font-misc-misc
NOTE 1: This procedure has been tested on Windows XP Service Pack 2 and 3, Windows Server 2000 Service Pack 4, Windows Server 2003 Service Pack 1, Vista Enterprise, and Windows 7. Please let us know if you get this working under other conditions.
NOTE 2: You can try switching between tabs by using either SHIFT RIGHT/LEFT ARROW (the KDE default) ... or CTRL PAGE-UP/DOWN (the Gnome terminal default)
NOTE 3: if you get the following error when configuring the mxrvt package:
checking for X... noThen you will need to make sure you installed the "make" package from cygwin.
configure: error: Mrxvt requires the X Window System libraries and headers.
NOTE 4: There is no bootstrap.sh in the mrxvt-0.5.4.tar.gz download, so it is no longer needed for installation.
NOTE 5: the startxwin.sh is no longer distributed with Cygwin/X ... if you were using that script or a custom script from your /usr/X11R6/bin directory you will need to remove the PATH, XAPPLRESDIR=/, XCMSDB, XKEYSYMDB, and XNLSPATH environment variable declarations at the top, since all of the X11R6 directories are moving around with these latest releases of Cygwin/X packages.
Hope that helps.
Tuesday, December 02, 2008
Software caused connection abort
Have you ever gotten an error like this when using ssh?
And then ssh back into the box.
Hope that helps.
NOTE 1: if you use ssh -v (verbose) when this error occurs you may see something like this:
debug1: connect to address myFavoriteIpAddr port 22: Software caused connection abort
NOTE 2: This error occured using: OpenSSH_5.1p1, OpenSSL 0.9.8h 28 May 2008
NOTE 3: If you would like to use a tabbed terminal window try using mrxvt under cygwin
ssh: connect to host myhost.com port 22: Software caused connection abortTry removing the entry for myhost.com from your ~/.ssh/known_hosts file.
And then ssh back into the box.
Hope that helps.
NOTE 1: if you use ssh -v (verbose) when this error occurs you may see something like this:
debug1: connect to address myFavoriteIpAddr port 22: Software caused connection abort
NOTE 2: This error occured using: OpenSSH_5.1p1, OpenSSL 0.9.8h 28 May 2008
NOTE 3: If you would like to use a tabbed terminal window try using mrxvt under cygwin
Tuesday, November 25, 2008
Thursday, November 20, 2008
Missing Dependency: libx264.so.58()(64bit) is needed by package cinelerra-2.1-0.18.svn20080514.fc9.kwizart.x86_64
For those of you fedora users who have gone here and have tried this on your fc9 box:
yum install cinelerra --enablerepo=kwizart
and gotten errors like this:
You may want to try what I did ... at your own risk :-)
yum install cinelerra-cv --enablerepo=kwizart-rawhide --enablerepo=rawhide --enablerepo=rpmfusion-free-rawhide
This worked for me.
By the way "-cv" means it is the community version.
Hope that helps.
yum install cinelerra --enablerepo=kwizart
and gotten errors like this:
cinelerra-2.1-0.18.svn20080514.fc9.kwizart.x86_64 from kwizart has depsolving problems
--> Missing Dependency: libx264.so.58()(64bit) is needed by package cinelerra-2.1-0.18.svn20080514.fc9.kwizart.x86_64 (kwizart)
Error: Missing Dependency: libx264.so.58()(64bit) is needed by package cinelerra-2.1-0.18.svn20080514.fc9.kwizart.x86_64 (kwizart)
You may want to try what I did ... at your own risk :-)
yum install cinelerra-cv --enablerepo=kwizart-rawhide --enablerepo=rawhide --enablerepo=rpmfusion-free-rawhide
This worked for me.
By the way "-cv" means it is the community version.
Hope that helps.
Wednesday, November 19, 2008
Before the holidaze ...
Saturday, November 08, 2008
Someone ... written by Kara
.
Kara wrote and composed this poem for her teacher, Mrs. Puyau.
Kara wrote and composed this poem for her teacher, Mrs. Puyau.
Someone near to me
Someone dear to me
Someone who teaches me
Someone who brings peaches to me
Someone who is in my class
Someone who can break through glass
Someone who plays games with me
All day with me
Someone who doesn't like to tie her shoe
and her favorite color is blue
Her father calls her 'Jewels'
She loves to use math tools
Her name starts with a 'P'
She likes you and me
Guess who?
Guess who?
It's Mrs. Puyau,
who doesn't like to tie her shoe
At Grandma B's ...
Monday, November 03, 2008
Taking a nap ...
Thursday, October 30, 2008
Vietnamese unicode and the BlackBerry
NOTE: The issue described below was occurring while using BlackBerry OS version 4.0 and 4.1. The newer 5.0 version of the BlackBerry OS does not exhibit these issues.
Apparently the BlackBerry does a good job of rendering decomposed unicode characters into readable characters. But the BlackBerry does not appear to be able to render precomposed characters (which is what most pages on the internet use).
So to make a long story short, if you copy, let's say, some Vietnamese from a web page, and paste it into an email ... that email will not render very well on a BlackBerry.
Well, here is a hack that may help someone out. Decompose the characters, and send those decomposed characters in an email. If you do that, the email will likely render "fine" in a normal email client as well as a BlackBerry email client. I call this a hack because the W3C generally recommends to exchange texts in NFC ... well most BlackBerry email clients will not render all precomposed characters (NFC).
For example, if you are NOT using a windows box, try cutting and pasting the following into an email:
Now, try the same with this "decomposed" text:
I'm not sure why I feel like including a small java program I wrote to help folks create emails that render better for the BlackBerry, but here it is:
I've only tested this methodology with Vietnamese, and because the incident at the tower of Babel was so confusing, all bets are off with other languages.
By the way, it looks to me like neither NFC nor NFKD render correctly in AndroidMail as of today's build, so we should end up seeing complaints about Vietnamese not rendering well on the G1, unless the developers get it fixed soon. Maybe we will have a follow up post with more on that subject.
UPDATE: A great write up on unicode and the BlackBerry is here on the Logicmail website. LogicMail is a J2ME E-Mail client supporting IMAP and POP, and designed to run on RIM BlackBerry handheld devices.
NOTE:
1) For more help with the definitions of the normalization forms mentioned above try here. It is a good document to be familiar with if you are planning to do i18n or l10n.
- i18n stands for internationalization
- l10n stands for localization
2) for those of you who just want a quick overview ...
- These terms are roughly equivalent for this discussion:
compatibility decomposition (NFKD)
canonically decomposed characters
composite unicode
composite characters
the "separated" diacritical marks and letters used in Vietnamese without combining
- These terms are also roughly equivalent, and should not be confused with those just above:
compatibility composition (NFKC)
NFC - normalization form canonical composition
precompound unicode
unicode dựng sẵn
composed characters
recomposed characters (by canonical equivalence)
precomposed characters
decomposable characters
pre-composite characters
ligatures
the set of completed characters (including all markings)
If you think there is a problem with the terms or equivalencies drawn above, please let's discuss it via email. If there are things that need to be corrected, I am open to that, just let me know.
Apparently the BlackBerry does a good job of rendering decomposed unicode characters into readable characters. But the BlackBerry does not appear to be able to render precomposed characters (which is what most pages on the internet use).
So to make a long story short, if you copy, let's say, some Vietnamese from a web page, and paste it into an email ... that email will not render very well on a BlackBerry.
Well, here is a hack that may help someone out. Decompose the characters, and send those decomposed characters in an email. If you do that, the email will likely render "fine" in a normal email client as well as a BlackBerry email client. I call this a hack because the W3C generally recommends to exchange texts in NFC ... well most BlackBerry email clients will not render all precomposed characters (NFC).
For example, if you are NOT using a windows box, try cutting and pasting the following into an email:
Subject: NFC (like most of the web)You'll find that emails sent with these characters render fine in a normal desktop email client, or even a web email client like Gmail, but they do not render correctly in the BlackBerry email client.
Chúa yêu em lòng em vui thay
Kia Kinh Thánh đã tỏ cho hay
Các con thơ thuộc Jê-sus đây
Chúng yếu nhưng Ngài khỏe mạnh hoài
Jê-sus yêu em lắm
Phải em được Chúa yêu
Jê-sus yêu em lắm
Chính trong lời Chúa dạy nhiều
Now, try the same with this "decomposed" text:
Subject: NFKD (a decomposed form)While the two texts may look similar on this web page, they are different, trust me. And you'll find that these characters render well in Gmail, Outlook, Evolution, but also render well on the BlackBerry.
Chúa yêu em lòng em vui thay
Kia Kinh Thánh đã tỏ cho hay
Các con thơ thuộc Jê-sus đây
Chúng yếu nhưng Ngài khỏe mạnh hoài
Jê-sus yêu em lắm
Phải em được Chúa yêu
Jê-sus yêu em lắm
Chính trong lời Chúa dạy nhiều
I'm not sure why I feel like including a small java program I wrote to help folks create emails that render better for the BlackBerry, but here it is:
import java.util.Scanner;This program would be used as follows from a command line:
import java.text.Normalizer;
import java.text.Normalizer.Form;
public class d {
public static void main(String[] args) {
Scanner sc = new Scanner(System.in);
sc.useDelimiter("Yes, my Java is terrible ...");
String foo = sc.next();
CharSequence c = foo.subSequence(0,foo.length());
Normalizer.Form nf = Normalizer.Form.valueOf("NFKD");
System.out.println(nf + " Compatability Decomposed:\n" + Normalizer.normalize(c,nf));
}
}
$ cat myFileWithPrecomposedCharacters | java dSo you could paste NFC characters from, say, a Vietnamese web page, into a file, and then run the file through the program to generate NFKD which you can then paste into an email you're sending, and that email should render in a readable way using a desktop email client, a web email client, or a BlackBerry.
I've only tested this methodology with Vietnamese, and because the incident at the tower of Babel was so confusing, all bets are off with other languages.
By the way, it looks to me like neither NFC nor NFKD render correctly in AndroidMail as of today's build, so we should end up seeing complaints about Vietnamese not rendering well on the G1, unless the developers get it fixed soon. Maybe we will have a follow up post with more on that subject.
UPDATE: A great write up on unicode and the BlackBerry is here on the Logicmail website. LogicMail is a J2ME E-Mail client supporting IMAP and POP, and designed to run on RIM BlackBerry handheld devices.
NOTE:
1) For more help with the definitions of the normalization forms mentioned above try here. It is a good document to be familiar with if you are planning to do i18n or l10n.
- i18n stands for internationalization
- l10n stands for localization
2) for those of you who just want a quick overview ...
- These terms are roughly equivalent for this discussion:
compatibility decomposition (NFKD)
canonically decomposed characters
composite unicode
composite characters
the "separated" diacritical marks and letters used in Vietnamese without combining
- These terms are also roughly equivalent, and should not be confused with those just above:
compatibility composition (NFKC)
NFC - normalization form canonical composition
precompound unicode
unicode dựng sẵn
composed characters
recomposed characters (by canonical equivalence)
precomposed characters
decomposable characters
pre-composite characters
ligatures
the set of completed characters (including all markings)
If you think there is a problem with the terms or equivalencies drawn above, please let's discuss it via email. If there are things that need to be corrected, I am open to that, just let me know.
Thursday, October 23, 2008
Android Email application
First of all ... Android is an amazing platform. So, for those of us who want details about what we are getting before we make that purchase decision ... Let's just take a quick look at one application, the Email application that Google released the source to a couple of days ago.
I compiled AndroidMail and deployed it to the Android emulator, and here are screenshots (click to enlarge them):
Here is the opening screenshot of my gmail inbox showing an email that I just sent to myself using the emulator running the AndroidMail application ...
Here is that same email fully rendered with the subject "Droid Emulator" in the AndroidMail application.
Here is the account setup screen. If you click "Next" with the information given, it sets up a Gmail inbox flawlessly. If you click on "Manual Setup" you get the screenshot below ...
It supports IMAP, Yay! Although, it does not appear to support IMAP idle ... yet.
Here we are prompted for the type of security and port numbers and such for incoming mail on the account ... I just clicked next, even though the information did not look correct yet ...
Here is what happened when I clicked on the "Next" button with my gmail address given in the previous screen ... I thought gmail supported IMAP already. Actually I know it does, because I access my gmail using another email app for the black berry called LogicMail. LogicMail supports IMAP, and can access my gmail via IMAP just fine.
It says ...
If you can't tell why I'm showing an error screen here, well ... you can learn quite a bit about an application by how it handles errors. And AndroidMail has nerd-love error screens. Yes, we are strange ... we have to see how it responds to failure. And that may explain our social problems too.
Anyway, it is great to see a phone running Linux AND a clean Java app. Overall ... Good job, Android team!
NOTES:
1) mydroid took 32 minutes to build on this Intel Core2 Duo 3GHz fc8 box.
2) Yes, the Android SDK, and eclipse ADT work great on Fedora ... let me know if you'd like a rundown on the packages needed to get the Android SDK, and/or the entire Android platform building and working on your Fedora box.
3) Screenshots made with Android Emulator, imglib, and the (super)+drawbox capture functionality provided by compiz-fusion.x86_64
4) UPDATE: I have found that I have to run the eclipse ADT (ganymede) with at least a 1.5GB virtual machine (./eclipse -vmargs -Xms512m -Xmx1536m) in order to get Android Email to completely build and run in the emulator from Eclipse ... otherwise I get errors like "Could not find AndroidMail.apk!" ... this is because the builds were not completing (because of out of memory issues) and not producing the AndroidMail.apk file
I compiled AndroidMail and deployed it to the Android emulator, and here are screenshots (click to enlarge them):
Here is the opening screenshot of my gmail inbox showing an email that I just sent to myself using the emulator running the AndroidMail application ...
Here is that same email fully rendered with the subject "Droid Emulator" in the AndroidMail application.
Here is the account setup screen. If you click "Next" with the information given, it sets up a Gmail inbox flawlessly. If you click on "Manual Setup" you get the screenshot below ...
It supports IMAP, Yay! Although, it does not appear to support IMAP idle ... yet.
Here we are prompted for the type of security and port numbers and such for incoming mail on the account ... I just clicked next, even though the information did not look correct yet ...
Here is what happened when I clicked on the "Next" button with my gmail address given in the previous screen ... I thought gmail supported IMAP already. Actually I know it does, because I access my gmail using another email app for the black berry called LogicMail. LogicMail supports IMAP, and can access my gmail via IMAP just fine.
It says ...
Sorry! The application Email (process com.android.email) has stopped unexpectedly. Please try again.
If you can't tell why I'm showing an error screen here, well ... you can learn quite a bit about an application by how it handles errors. And AndroidMail has nerd-love error screens. Yes, we are strange ... we have to see how it responds to failure. And that may explain our social problems too.
Anyway, it is great to see a phone running Linux AND a clean Java app. Overall ... Good job, Android team!
NOTES:
1) mydroid took 32 minutes to build on this Intel Core2 Duo 3GHz fc8 box.
2) Yes, the Android SDK, and eclipse ADT work great on Fedora ... let me know if you'd like a rundown on the packages needed to get the Android SDK, and/or the entire Android platform building and working on your Fedora box.
3) Screenshots made with Android Emulator, imglib, and the (super)+drawbox capture functionality provided by compiz-fusion.x86_64
4) UPDATE: I have found that I have to run the eclipse ADT (ganymede) with at least a 1.5GB virtual machine (./eclipse -vmargs -Xms512m -Xmx1536m) in order to get Android Email to completely build and run in the emulator from Eclipse ... otherwise I get errors like "Could not find AndroidMail.apk!" ... this is because the builds were not completing (because of out of memory issues) and not producing the AndroidMail.apk file
Wednesday, October 01, 2008
Tuesday, September 30, 2008
For those of you we've missed ... part 3
.
Ok ... on to part 3
Random picture of Val ...
Ask this girl what her new name is today ...
Ask this one to read her new poem to you that she wrote for her teacher
Another random picture of Val ...
Click to enlarge 'cuz David's livin' large.
Enjoy.
Let us know when you're ready ... the next set of pictures is awaiting your comments.
Ok ... on to part 3
Random picture of Val ...
Ask this girl what her new name is today ...
Ask this one to read her new poem to you that she wrote for her teacher
Another random picture of Val ...
Click to enlarge 'cuz David's livin' large.
Enjoy.
Let us know when you're ready ... the next set of pictures is awaiting your comments.
For those of you we've missed ... part 2
.
We will have some more recent pictures later, but here are some that are more important for now ...
Hi, Grandma ...
Looking through the pictures from the birthday party ...
Whose face is that in the mirror at the shine party?
Hi, David.
Hi, Mommy.
Great! A group photo from a while back ... make sure you click on this one to see it full size.
How have you been since we last posted? Just leave a comment below when your ready ... part 3 with new pictures is ready to post.
May the Lord bless you and keep you ...
We will have some more recent pictures later, but here are some that are more important for now ...
Hi, Grandma ...
Looking through the pictures from the birthday party ...
Whose face is that in the mirror at the shine party?
Hi, David.
Hi, Mommy.
Great! A group photo from a while back ... make sure you click on this one to see it full size.
How have you been since we last posted? Just leave a comment below when your ready ... part 3 with new pictures is ready to post.
May the Lord bless you and keep you ...
Monday, September 29, 2008
configure: error: INSERT_PACKAGE_X_HERE requires INSERT_PACKAGE_Y_HERE libraries and headers.
.
This may happen under cygwin when you are running the configure command as part of the configure, make, make install procedure for some package ... and you forgot to install "make".
You may have automake, autoconfigure, and several other packages installed, thinking that make must also have been installed as a dependency ... do not be so naive like I was. Install the make package from cygwin, and you error may just go away.
Hope that helps.
This may happen under cygwin when you are running the configure command as part of the configure, make, make install procedure for some package ... and you forgot to install "make".
You may have automake, autoconfigure, and several other packages installed, thinking that make must also have been installed as a dependency ... do not be so naive like I was. Install the make package from cygwin, and you error may just go away.
Hope that helps.