Re: Problem with charset
* Michael Elkins on Thursday, January 03, 2013 at 01:14:16 + > Good catch. I just commmited a patch that will print > +/-NCURSES_WIDECHAR next to the ncurses version to make it clear which > lib mutt is compiled against. Not sure whether it gives reliable diagnostics everywhere: $ uname -mprsv Darwin 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 i386 $ mutt -v | fgrep -i curses ncurses: ncurses 5.9.20121229 (compiled with 5.9) -NCURSES_WIDECHAR Configure options: '--prefix=/usr/local' '--disable-nls' '--enable-hcache' '--with-idn=/sw' '--with-homespool=Maildir' '--with-curses=/usr/local' '--with-libiconv-prefix=/sw' $ otool -L `which mutt` /usr/local/bin/mutt: /usr/local/lib/libncursesw.5.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/local/lib/libtokyocabinet.9.dylib (compatibility version 9.0.0, current version 9.11.0) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /sw/lib/libidn.11.dylib (compatibility version 18.0.0, current version 18.5.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.7) Shouldn't that yield +NCURSES_WIDECHAR? c -- theatre - books - texts - movies Black Trash Productions at home: http://www.blacktrash.org Black Trash Productions on Facebook: http://www.facebook.com/blacktrashproductions
Re: Transitioning to IMAP & maildir. Howto define ~/mail instead of ~/Mail?
* s. keeling [2013-01-02 22:05:29 -0700]: > ... and it's entirely possible that I don't know what I'm doing there. > I'm very new to IMAP (never used it before). spoolfile used to be > "/var/mail/keeling" when I POPped mail from my ISP (and then procmail > picked it up ...). When I login to ISP's webmail, all I can tell is > "https://webmail.nucleus.com/Inbox.aspx";. I'm using OfflineIMAP --> > ~/mail, so ... As you're using offlineimap, you will have a configuration file for that program somewhere, usually you set up your own options in ~/.offlineimaprc. The options set within this file will determine where the program is putting your mail. It's been sometime since I used it but I believe its default is ~/Mail or ~/Maildir. So, you will need to edit its configuration file to tell it to store your mail where you want it: ~/mail. Check the man page and you'll find out how to do that. It's very trivial to set up. Then, you need to set $folder in muttrc - which you've done. Because the default for mutt is ~/Mail, so you need to override that default. You can set $spoolfile as well to the main Maildir (your inbox) or you can set the $MAIL environment variable to that directory. Personally, i'd do that. So, if your using a bourne-style shell, it would look something like this: export MAIL="$HOME/mail/inbox" ... then each time you log in to a shell this will be set in the environment and mutt will use it to find the spoolfile. So, the steps are: 1 - read offlineimap man page to find what options you need to change so get it to put your mail where you want it. 2 - set or check that you've set $folder in ~/.muttrc to ~/mail 2 - set the $MAIL environment variable in your shell configuration file to the spoolfile you have asked offlineimap to use; i.e. ~/mail/inbox That *should* get you going. Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Problem with charset
On Wed, Jan 02, 2013 at 10:20:56AM +0100, Andrea Hanke wrote: > Hello together, > > I have a problem with mutt and charset configuration. > > I am working with Ubuntu and my local settings are there: > > LANG=de_DE.utf8 > LANGUAGE= > LC_CTYPE="de_DE.utf8" > LC_NUMERIC=de_DE.UTF-8 > LC_TIME=de_DE.UTF-8 > LC_COLLATE="de_DE.utf8" > LC_MONETARY=de_DE.UTF-8 > LC_MESSAGES="de_DE.utf8" > LC_PAPER=de_DE.UTF-8 > LC_NAME=de_DE.UTF-8 > LC_ADDRESS=de_DE.UTF-8 > LC_TELEPHONE=de_DE.UTF-8 > LC_MEASUREMENT=de_DE.UTF-8 > LC_IDENTIFICATION=de_DE.UTF-8 > LC_ALL= > > Also I have a charset configuration in my .muttrc: > > set charset="utf-8" > > The aim is, that mutt runs in the language german and with äüöß. I don't know if this will help but a while back I was having issues with international characters displaying properly in a consistent fashion between mutt and vim on Solaris 11. What I ended up doing was simplifying my setup so that only GDM_LANG=en_US.UTF-8 (for Gnome apps) and LANG=en_US.UTF-8 language related parameters were exported in my shell's environment. I compiled mutt to use /usr/lib/libncurses.so.5 and vim to use /usr/lib/libcurses.so.1 and I ran mutt in a gnome-terminal which supports UTF-8. I removed any mutt/vim parameters that modified the charset. At this point I'm now seeing proper, consistent international character display in mutt and vim. -- Will Fiveash
Re: Problem with charset
Good morning together, and thanks a lot for the lot of replies! I try to give the feedback to several questions/ideas: 1.) 10 minutes ago I try to recompile my mutt, to make sure that the source is compiled with the same terminal settings like in the moment. But nothing becames better :-( 2.) Yes I rebootet my pc after changing my charset in the /etc/defaults/locale 3.) I checked with aptitude the "libncurses5" and "libncursesw5" -> both is installed 4.) In the compiler output i could not found anything about "libncurses5" or "libncursesw5" ... what mother google says us...or have I set any parameter on compiling or anything else? Thanks a lot to all! cheers andy [ Andreas Kneib - 02.01.2013 19:41:26 ]: > * Sander Smeenk schrieb am 02.01.2013 um 16:08 Uhr: > > > Quoting Andreas Hanke (andreas.ha...@r-kom.de): > > > > But if switch back to mutt the ü is an M-CM-< -> also in the menues. > > > any ideas? > > > Read your mails with vim. :-)) > > :-D > > Mother Google give me this hint: > > , > | > | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg3.html > | > | I am running Debian Lenny and Weechat-curses 0.2.6 from Debian's own package > | has swedish characters working fine both in command line and in xterm and > | urxvt in X, but when I downloaded 0.2.7 dev version and compiled it, "å ä > | ö" looks like "M-CM-%M M-CM-$M-CM-6". > | > ` > > , > | > | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg8.html > | > | Problem was link against libncurses instead of libncursesw. > | I'll add warning with cmake when this library is not found (it's not > | required, but recommended if standard ncurses does not have wide char > | support). > ` > > > Andreas > R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
Good morning together, and thanks a lot for the lot of replies! I try to give the feedback to several questions/ideas: 1.) 10 minutes ago I try to recompile my mutt, to make sure that the source is compiled with the same terminal settings like in the moment. But nothing becames better :-( 2.) Yes I rebootet my pc after changing my charset in the /etc/defaults/locale 3.) I checked with aptitude the "libncurses5" and "libncursesw5" -> both is installed 4.) In the compiler output i could not found anything about "libncurses5" or "libncursesw5" ... what mother google says us...or have I set any parameter on compiling or anything else? Thanks a lot to all! cheers andy [ Andreas Kneib - 02.01.2013 19:41:26 ]: > * Sander Smeenk schrieb am 02.01.2013 um 16:08 Uhr: > > > Quoting Andreas Hanke (andreas.ha...@r-kom.de): > > > > But if switch back to mutt the ü is an M-CM-< -> also in the menues. > > > any ideas? > > > Read your mails with vim. :-)) > > :-D > > Mother Google give me this hint: > > , > | > | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg3.html > | > | I am running Debian Lenny and Weechat-curses 0.2.6 from Debian's own package > | has swedish characters working fine both in command line and in xterm and > | urxvt in X, but when I downloaded 0.2.7 dev version and compiled it, "å ä > | ö" looks like "M-CM-%M M-CM-$M-CM-6". > | > ` > > , > | > | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg8.html > | > | Problem was link against libncurses instead of libncursesw. > | I'll add warning with cmake when this library is not found (it's not > | required, but recommended if standard ncurses does not have wide char > | support). > ` > > > Andreas R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
No Folder Bar?
In the mercurial version of mutt (changeset 5620) the folder bar (not sure if the name is correct, the corresponding setting is: 'folder_format') seems to be missing. Greetings, -- b.d (| |) ^ ^
Re: Problem with charset
On Thu, Jan 03, 2013 at 10:14:30AM +0100, Andreas Hanke wrote: 3.) I checked with aptitude the "libncurses5" and "libncursesw5" -> both is installed You need to make sure the development package is also installed. # apt-get install libncursesw5-dev Make sure to rerun mutt's configure script after you install the package.
Re: Problem with charset
Incoming from Andreas Hanke:
> Good morning together,
Buenos dias! Que pasa?
> and thanks a lot for the lot of replies!
This's always been a great list. I can't really offer much help on
your specific problem other than to tell you what's working here and
how, and offering suggestions. This's Debian "testing"/wheezy, so
should be roughly equivalent (upstream) to your Ubuntu (I think):
--
(1) infidel /home/keeling_ locale
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
LC_CTYPE="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_PAPER="en_CA.UTF-8"
LC_NAME="en_CA.UTF-8"
LC_ADDRESS="en_CA.UTF-8"
LC_TELEPHONE="en_CA.UTF-8"
LC_MEASUREMENT="en_CA.UTF-8"
LC_IDENTIFICATION="en_CA.UTF-8"
LC_ALL=
--
> I try to give the feedback to several questions/ideas:
>
> 1.) 10 minutes ago I try to recompile my mutt, to make sure that the
I'm impressed, but I have to say I've never had any need to "roll my
own" mutt. I doubt that Ubuntu/Canonical have done anything wrong in
their build.
> 2.) Yes I rebootet my pc after changing my charset in the
> /etc/defaults/locale
That's a typo?
--
(0) infidel /home/keeling_ cat /etc/default/locale
# File generated by update-locale
LANG=en_CA.UTF-8
LANGUAGE="en_CA:en"
--
> 3.) I checked with aptitude the "libncurses5" and "libncursesw5" ->
> both is installed
True here as well.
So, now I'm down to just offering sugestions:
i) Try other terminal emulators. I use "uxterm" with mutt. Some
terminal emulators just don't do utf-8.
ii) Can you use emacs? It has no problems with utf-8 (though I
doubt vim does either).
set editor="/usr/bin/emacs '%s'"
iii) Re-describe the problem in your eyes now that you've expended
all this effort learning about it?
Have fun. :-) Bon chance.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|:& };:
- -
Re: No Folder Bar?
On Thu, Jan 03, 2013 at 02:39:07PM +0100, Bastien Dejean wrote: In the mercurial version of mutt (changeset 5620) the folder bar (not sure if the name is correct, the corresponding setting is: 'folder_format') seems to be missing. The "sidebar" patch is not officially supported by the mutt project, but you can find it here: http://www.lunar-linux.org/mutt-sidebar/
Re: Problem with charset
Hi Michael, now it works! What I do: 1.) apt-get install libncursesw5-dev 2.) ./configure in my mutt directory 3.) make clean 4.) make 5.) make install 6.) Enjoy! :-) Wow!!! Thanks a lot to the whole mutt world! cheers andy [ Michael Elkins - 03.01.2013 16:45:34 ]: > On Thu, Jan 03, 2013 at 10:14:30AM +0100, Andreas Hanke wrote: > >3.) I checked with aptitude the "libncurses5" and "libncursesw5" -> > >both is installed > > You need to make sure the development package is also installed. > > # apt-get install libncursesw5-dev > > Make sure to rerun mutt's configure script after you install the > package. R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Accents and other diacriticals - was Re: Problem with charset
On Wed, Jan 02, 2013 at 08:13:01PM -0600, Dale A. Raby wrote:
>
> Mein Deutsch ist nicht gut, aber the umlaut characters disply just
> fine on my system. What I would like to know is how you type them on an
> English keyboard. Is there some way to do that?
>
Yes, but it depends. In recent xorg, with a GB keyboard the dead
keys appear to come along automatically. The compositions are in
/usr/share/X11/locale/en_US.UTF-8/Compose (you can also use a
Compose key, but I haven't had recent success with that - only tried
it for some not-defined things, dead keys are easier) and the
symbols are in /usr/share/X11/xkb/symbols/us [ for the common case
of US-style QWERTY keyboards and latin alphabets ].
In practice, the dead keys are to the right of the main keys. On my
GB keyboard the keys are laid out as
0 - and _ then = and +
O P [ and { then ] and }
K L ; and : then ' and @ then # and ~
M comma and < . and > then / and ?
[ anything after a 'then' above is a dead key when used with AltGr]
and I get the following: (hope you have enough fonts for all of
these : to people not reading in xorg, sorry about all the � you
[should] see for the glyphs which your console font does not cover
;-)
AltGr = is dead cedilla, e.g. ç ķ
(i.e. AltGr with the last key of the 'A' row, then a letter)
AltGr + is dead ogonek e.g. ǫ
AltGr [ is dead diaeresis or umlaut, e.g. ä ë
AltGr { is dead ring å ů
AltGr ] is dead tilde e.g. ñ õ
AltGr } is dead macron e.g. ā ē
AltGr ; is dead acute e.g. á ć
AltGr : is dead double acute ő ű
AltGr ' is dead circumflex e.g. â ĉ
AltGr @ is dead caron e.g. č ď ȟ
AltGr # is dead grave e.g. à ò
AltGr ~ is dead breve e.g. ă ğ
AltGr / is dead dot below e.g. ạ ḅ
AltGr ? is dead dot above or dotless lowercase 'i' e.g. ḃ ċ İ ı
On a US keyboard, some of those keycap symbols will differ.
This is all typed in rxvt-unicode - that also allows me to type the
[ISO 1475] codes directly, e.g. ctrl-alt-2-5-9 for ə [ latin schwa ]
and ctrl-alt-2-1-9 for ș [ latin s with comma below ].
The dead keys, and things in my Xmodmap, work in other apps such as
libreoffice.
For some other xorg terminals you may find that much of this does
NOT work - I imagine that gnome, for example, requires you to do
things its own way.
For non-xorg terminals on linux and using kbd, there are various
compose tables which might suit you, and at least one is probably
picked up automatically. If you are using linux and kbd, take a
look at the keymap you are using - Compose might need to be defined,
you can then probably use Compose '"' 'a' for a-umlaut.
Distros using console-tools are different, and I haven't used them
enough to work around all their differences. For other systems I
have no idea.
In my case I have enough trouble remembering some of the correct
dead keys, so I wanted to use similar sequences on the rare occasions
I'm using the console. The compose tables are limited, and the
first match cannot be overwritten later, so I do not use the
standard compose tables. I'll quote a few lines from my own keymap,
to illustrate the principles:
|# right windows key and right menu key both mapped to Compose -
|# my normal keyboards have one or other of these
|keycode 126 = Compose
|keycode 127 = Compose
|
|# for some reason, although vim is using utf-8 encoding (:set enc)
|# it thinks the file is in latin1, which royally screws up the examples
|# : set fenc=utf-8 is needed here
|compose '#' 'a' to U+00E0 # a grave à
|compose '[' 'a' to U+00E4 # a diaeresis ä
HTH, in which case have fun experimenting, and remember to back up
any definitions you edit - breaking a keymap can do surprising
things (I once list the control keys from my on kmap - only noticed
when ^C did nothing to stop a compilation).
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
Re: Transitioning to IMAP & maildir. Howto define ~/mail instead of ~/Mail?
Incoming from Jamie Paul Griffin:
> * s. keeling [2013-01-02 22:05:29 -0700]:
>
> > picked it up ...). When I login to ISP's webmail, all I can tell is
> > "https://webmail.nucleus.com/Inbox.aspx";. I'm using OfflineIMAP -->
> > ~/mail, so ...
>
> As you're using offlineimap, you will have a configuration file for that
> program somewhere, usually you set up your own options in
> ~/.offlineimaprc. The options set within this file will determine where
That's working fine, I think. I'm still learning about how it works
and what it actually does.
> You can set $spoolfile as well to the main Maildir (your inbox) or you
> can set the $MAIL environment variable to that directory. Personally,
> I'd do that. So, if you're using a bourne-style shell, it would look
Huh. My "MAIL" was unset (empty), but I see "MAILDIR" was set to
"~/Mail". Thanks for pointing that out. I hadn't thought of looking
there. Will test.
> That *should* get you going.
Actually, it's going pretty nicely. This is a very small problem and
easily worked around. Thanks for the tips.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|:& };:
- -
Re: Accents and other diacriticals - was Re: Problem with charset
On Thu, Jan 03, 2013 at 06:21:47PM +, Ken Moffat wrote: > > (I once list the control keys from my on kmap - only noticed > when ^C did nothing to stop a compilation). > Typo : I once _lost_ the control keys. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce
why my mutt usually lose some email ?
hi, I find my mutt usually lose some email . how to fix it ? how to make mutt receive email automatic? thanks!
Re: why my mutt usually lose some email ?
Incoming from horse_rivers:
> hi,
Hi. :-)
> I find my mutt usually lose some email.
What does that mean?
> how to fix it ?
By editing muttrc, I'm guessing.
> how to make mutt receive email automatic?
... from what, and how? Are you popping mail, or are you trying to
connect via IMAP, or what? You haven't given us much to go on. :|-|
I use Debian testing/wheezy + OfflineIMAP + mutt + emacs (& etc), but
there's lots of ways to do it. How are you trying to do it?
Please explain what you're trying to do, and with what you're trying to
do it. Linux (which?), Windows (which?), ...
uname -a
locale
echo $SHELL
What terminal emulator are you using?
What's MAIL (echo $MAIL) set to? What's MAILDIR set to?
Have fun. :-) It's an adventure!
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|:& };:
- -
Re: why my mutt usually lose some email ?
* horse_rivers [2013-01-04 12:56:14 +0800]: > hi, > > I find my mutt usually lose some email . > > how to fix it ? > > how to make mutt receive email automatic? > > thanks! > First and foremost, you need to understand that mutt is merely a mail reading browser - it doesn't receive mail but it does have some smtp capability to send mail to a receiving MTA (mail transfer agent). It's primary functiontion is just to read messages stored in a local folder, either a UNIX directory (Maildir) or a UNIX file (mbox). (It can use other mailbox formats but lets not confuse the issue too much by delving into those yet.) As well as the local mailboxes just mentioned it can read messages on a remote machine using the POP protocol and the IMAP protocol, like you would if you were using something like Apple Mail or Thunderbird, for example. So, you need to explain more about your mail set up: do you want to read mail from an account like Gmail or 126.com which I see is the mail provider you have used to send your message to the list or are you intending on setting up a server with your own domain to receive messages from the internet to a server you maintain. Then do you wish to use IMAP or local mailboxes; do you a UNIX system (i'm guessing you are or will be) perhaps you could tell us which system you're using. If you can provide more information and also have a read through the mutt website and wiki that will help us to assist further. www.mutt.com http://dev.mutt.org/trac/wiki/MuttWiki These two links will provide lots of information to get you started. Jamie. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
