From: Mihai M. <io...@io...> - 2010-07-21 17:54:28
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hey all, as I've been using iTerm for quite some time now, I have experienced its benefits, as well as its problems. One of those is that iTerm seems to be unable to draw full lines correctly, or actually mangles them quite a bit. That is to say, sometime a line is repeated over and over again, sometimes there are just blank lines popping out of nowhere. The problem with this bug: it's hard to track, I'd rather say almost impossible, as it's not very reproducible. Fixing it manually works fine through: just scroll up until the "borken" parts are, well, scrolled away and scroll down again. Most likely iTerm will redraw those previously borken regions without any problem (and for that matter, as they should look like.) It may be related to the Blur or transparency option, not sure about that. I'll try running it without the Blur option as soon as I've got some time. Next, there is the cruel world of keyboard mappings and special character input. Let's start with the first one. I'd like to map word jumping (back and forth) to Cmd/Apl + Left/Right Arrow Key. In Terminal.app, I have defined two keybindings for those two, both echoing an escape sequence. The sequence in question was \033b (backwards jumping) and \033f (forwards jumping.) However, I have not been able to bind those keys or escape sequences in iTerm. I have tried with [033b/f, 033b/f, even translated it to hex (that is, 0x1bb/0x1bf) or whatever. Every effort was unsuccessful and the given examples in the xterm keyboard profile didn't really shed a light on me, so I'm kinda lost. Do you know how to do that right? Then again, I've got some real problems with UTF8 input (and most impressively, also output.) For once, my Option (Alt) key is not set to "Meta", so this shouldn't cause any problems. When I try to input something like an Umlaut, iTerm and zsh composes the two chars fine to one one Umlaut (e.g. ¨+ U = Ü.) Now, trying to access any directory or file with Umlauts will be a pain in the ass, as 1.) completion does not work. Actually, something like "cd Ütest" will work, but zsh (version 4.3.10, that is, UTF-8 aware) won't be able to auto complete the path or anything. Also, such files or directories will be listed as so: "Ü test". Completion does ONLY work when trying to complete stuff via "U<Tab>", which will cause such output: ls U<0308> (Where <0308> is highlighted black on white, whilst my normal color scheme is white on black.) So I guess this whole composing stuff is broken, but I'm not sure whether it's iTerm or zsh. The locale is set to en_US.UTF-8, so it ACTUALLY should work fine. Another problem is iTerm's tab handling. The look and feel is set to Aqua, though I don't know whether it changes anything but the how it looks, anyway. When clicking on a tab, however, it's very likely that nothing happens. Only clicking on it again will activate it - and for that matter also open up the "Info" window about this very tab. I guess that's some sort of a bug. So, any ideas? :) Best regards, Mihai Moldovan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJMRzRMAAoJEB/WLtluJTqHPb0P/2wtCSoFvKLdrtp9/PT9OMWD ZtqgkfVQ/+ZCAIy94Q4jFufW/veiG3jfyYIjU0MjV2tgCwjqWS6blhcZXOtfFPJD p5MsNR29Nu7TUx2nmGWGFj76DlFEqnouSTSveHTLPqhIcEnW59HCncEsoJRVVdq1 dTvhr8wgmczqX/bBTEb/VhfKv0bwqsyGFHb58xpwrU0XTBRK7+/+iIXbGqMw5fTz iIFxih5kE/ngnDKagKDH4sNzMg+PrGVZ9K/6KLeVFXkoX2Wg3/DGS2exEYwTql2W aCcJizT8uKR8Mat/3ra59D7Rwu+mjOX9P2GTq/mb0hfL1r3PFLZMM9ikZDvt79eY acuRiIZGjEYo9yiHPUGZIq4N7ztGS6TAJcE3HNIKAeiNQy8YEG9ET83msaYj4mvR 1V3UtrktRVcY64t/X124he+fape7rVj0mS9ZqL4HWXyRnNKFT7zpkQ/OorM+HrOF 0tUlxssx1gTZEWew+sQZ0Pt5D4N5K49VbjllFzug8qTz0jvS5IeL/sP4BsyAI1Zm ewbjhN4nybTQnQk5rpp81hTRN7lMJaF1LDTSbV4TGYPFaM5zlj5WZSTUeuGiScqK ekvYYqhFzwvXzIs8sKTG8xN9TbXB6LdXObAGbn4Q7Rt/F+VCvHDbO2OcqpHwHOhQ YRkw8JZEYKBg5Bjy9+lS =dFkk -----END PGP SIGNATURE----- |