Re: japanese with devel mutt
On Sat, Nov 11, 2000 at 09:40:18PM -0500, Josh Huber wrote: I'm trying out mutt version 1.3.11i, mostly because it has support for automatically switching the charset= line in outgoing emails to the proper encoding. Here's the problem: I can't get japanese to display properly without using something like LANG=ja_JP /usr/local/bin/mutt, which causes subprocessies (like gpg) to run with that language envionment. I'd like it to display text without setting the LANG variable, so I looked at the charset variable, and tried setting it to iso-2022-jp, which didn't seem to do anything, except prevent me from viewing japanese text. (of all things) am I clueless here? anyone have hints on how to set this up? I'm using xemacs with canna for input/sending email, btw. also, is this the proper place for these questions? people on -dev might have a better idea :) thanks in advance, OK here is my take: There are two xterms you can choose to display Japanese character set. However I have only tried the more popular shift-jis encoding, which the other one is deprecated, I think. One is Kanjiterm, Kterm in short. However, it is a bit hard to find. The other one is Aterm, which is called the Afterstep Term. You have to compile Aterm with somthing like "--enable-kanji" with configure. Once you have it compiled. Start Aterm, fire up lynx and load the page "http://www.yahoo.co.jp/". Notice: lynx support for Japanese and Chinese encoding is a bit broken. Enlightened Term (Eterm) said to support Kanji (which is a bad description), I have yet to get it to work, you might need to set the locale variables. However, if you use emacs, you should try out MULE, which is a multi-lingual edition for emacs. If you want X apps to display Japanese, there are more you have to do then just the xterm. Anyone would like to comment further?
Re: Muttrc, IMAP errors over SSH
* Brian Stearns [EMAIL PROTECTED] [11/11/00, 13:59:18]: I've configured OpenSSH at home, and I'm using PuTTY at work to establish a secure terminal session from work to home. Yet again, works great. It's not a PuTTY issue. I use it at work and it works :) Finallly, I thought perhaps that this was some strange interaction I'm seeing with PuTTY. However, if I use PuTTY to SSH into my box, then telnet to localhost from the same PuTTY terminal, the problem goes away. Brendan's idea seems the right one.. HTH Kai -- Kai Blin Webmasterof http://www.uni-tuebingen.de/uni/thm/molgen/ Univ. of Tuebingen Inst. of Human Genetics fon +49-7071-2974890 Wilhelmstrasse 27 Dept. of Molecular Genetics fax +49-7071-295233 D-72074 Tuebingen Do molecular biologists wear designer genes?
Re: Pager oddity
On Fri, Nov 10, 2000 at 04:00:21PM -0600, David Kanter wrote: This is nothing earth-shattering, but rather annoying: Mutt has what looks like an extra cursor lying on top of the highlighting bar over the last character in the message index window. I'm using the slang-based Mutt of OpenBSD. It happens with both rxvt and xterm. This is what happened when the cursor is not being switched off/hidden. In Slang, I believe it is possible to hide the cursor using a Slang function call. If you compile Mutt with Ncurses, the cursor is hidden by default. Also, Ncurses program looks better since it will work with transparent terms while Slang set the background color to black.
Re: Pager oddity
On 13, Nov, 2000 at 12:28:38AM +0800, Anthony Liu wrote: On Fri, Nov 10, 2000 at 04:00:21PM -0600, David Kanter wrote: This is nothing earth-shattering, but rather annoying: Mutt has what looks like an extra cursor lying on top of the highlighting bar over the last character in the message index window. I'm using the slang-based Mutt of OpenBSD. It happens with both rxvt and xterm. This is what happened when the cursor is not being switched off/hidden. In Slang, I believe it is possible to hide the cursor using a Slang function call. If you compile Mutt with Ncurses, the cursor is hidden by default. Also, Ncurses program looks better since it will work with transparent terms while Slang set the background color to black. I see the same thing with mutt-1.2.5i-curses on OpenBSD in an xterm. mutt -v says: Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: OpenBSD 2.8 [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK -USE_FCNTL +USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/etc/mutt" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. It works flawlessly in all respects, and I actually hadn't thought of this as a bug before now ... :-) HAND Morten -- UNIX, reach out and grep someone!
Re: limiting to message size
On Tue, Nov 07, 2000 at 02:46:40PM -0600, David Champion wrote: [snip original discussion of word/character counting] However, I can imagine a pattern expression that pipes each message through a command, and matches based on that command's exit status: if 0, match; else, no match. This could work like: ~Z 'set -- `wc %s`; [ $2 -gt 1000 ] true || false' Just as a side note - the ' true || false' part is redundant - the shell evaluates and || based purely on the last command's exit status; so the ' true || false' expression is only useful for turning a "zero / non-zero" exit code into a "zero / one". In this particular case, the last command is '[' a.k.a. 'test' - which in all its incarnations I've seen so far returns zero or one. G'luck, Peter -- What would this sentence be like if pi were 3?
Re: Muttrc, IMAP errors over SSH
1) Apologies for the lack of line wraps; I forgot to turn on auto-fill-mode in Emacs. 2) You were exactly right. An evil, old version of mutt in /usr/bin, which apparently is prepended to my path only when I ssh into my box, not telnet. I'll have to look into that. It always seems to be the simple things that trip me up. Thanks for the quick catch, and the patience to reply. Cheers! B- On Sat, Nov 11, 2000 at 02:18:04PM -0500, Brendan Cully wrote: On Saturday, 11 November 2000 at 13:59, Brian Stearns wrote: When I telnet into my home machine, I run mutt from the command line. It comes up immediately, automatically connects to my IMAP server, and allows me to browse my IMAP folders. When I SSH into my machine, running mutt from the command line results in a long series of .muttrc errors (mostly regarding my PGP commands, which some other errors mixed in). I then am told "Secure login is unavailable. Use cleartext login? ([n]/y):". Finally, when I answer "y", when I attempt to change folders (by pressing "c"), and then attempt to browse my folders (by pressing "?"), I get this message: "IMAP folder browsing is not currently supported". 1. Please wrap your text! 2. These are very clear signs that you aren't running the same version of mutt in both cases. You must have another binary lying around. Do the results of 'which mutt' match up under telnet vs ssh? You say the environment is the same, but I have a feeling your PATHs are different. -Brendan -- Don't make Godzilla mad! -- Brian Stearns ([EMAIL PROTECTED]) http://chiastic.net/thppt/
