Re: http://www.mutt.org/mail-lists.html -- Request to change
On Mon, Oct 14, 2002 at 02:50:52PM +0200, Thorsten Haude wrote: Hi, * Steve Kennedy [EMAIL PROTECTED] [02-10-14 13:36]: On Sun, Oct 13, 2002 at 03:25:44PM +0200, Lukas Ruf wrote: a few seconds ago, I wanted to re-subscribe under a different name on http://www.mutt.org/mail-lists.html A thing I did not like there was the way how you offer the different mailing lists: You offer them as radio-buttons instead of checkboxes. Why? Using mozilla 1.0, I was not unable to uncheck a radio-button without pressing Reset. This deleted also my email address. Would anyone of the administrators mind changing the radio-buttons into checkboxes? The idea was that you should only sub to the main list or the digest list (i.e. either/or) which is why radio buttons are used. You're the first to complain. I've had the same tiny problem. I recall seeing some comments to the effect that some non-compliant browsers allow one to submit a form with no radio buttons checked. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Autoview images in the pager - w3m
On Sat, Oct 05, 2002 at 03:18:23PM +0200, Sven Guckes wrote: mutt, w3m trio in a way that html messages could be shown in autoview with graphics inside? well, w3m already does what you want - so please use it. ... and you probably need a fairly recent version of w3m for this, too. however, w3m's changelog is not very elaborate... w3m's changelog is like links' - most of the detail is missing, and of what remains, some is useless or simply misleading at best. (however, w3m's graphics are sometimes useful in traversing some sites where the parasites are too intrusive for Netscape or Opera ;-) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Autoview images in the pager - w3m
On Sat, Oct 05, 2002 at 04:28:48PM +0200, Elimar Riesebieter wrote: AFAIK w3m-img doesn't work for vt's. I use sometimes links combined with fbi. zgv should work as well. is someone working on zgv again? (the last I looked, it wasn't working that well) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Default Colour on NetBSD
On Sat, Oct 05, 2002 at 05:59:08PM +0200, Hanspeter Roth wrote: On Oct 01 at 16:15, Thomas Dickey spoke: On Tue, Oct 01, 2002 at 09:52:34PM +0200, Hanspeter Roth wrote: If I could manage to build a mutt linked against an standard ncurses5.x then shoud there be a working use_default_colors() available? yes - I added the feature with ncurses 4.2 Bear in mind that when I'm building applications with ncurses, it is usually not using the *BSD ports - I frequently see problems reported that are due to that. I installed ncurses 5.2 in a separate path /usr/opt/ncurses-5.2. Then I built mutt 1.2.5.1: ./configure --prefix=/usr/opt/mutt-1.2.5.1 \ --includedir=/usr/opt/ncurses-5.2/include \ --libdir=/usr/opt/ncurses-5.2/lib --with-curses=/usr/opt/ncurses-5.2 It requires xterm-16color or similar. But still it doesn't recognize default as background color. but what does the output of the configure script look like? For example, the related section when I configure: checking for ispell... /usr/bin/ispell checking for initscr in -lncurses... yes checking for ncurses.h... yes checking for start_color declaration... yes checking for typeahead declaration... yes checking for bkgdset declaration... yes checking for curs_set declaration... yes checking for meta declaration... yes checking for use_default_colors declaration... yes checking for resizeterm declaration... yes checking for ANSI C header files... yes (the use_default_colors line is needed). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Default Colour on NetBSD
On Sat, Oct 05, 2002 at 06:55:04PM +0200, Hanspeter Roth wrote: Hm. In deed it seems to be off. Does it depend on the ncurses configuration? I just did: ./configure --prefix=/usr/opt/ncurses-5.2 The --prefix option of configure scripts is used to tell where the application should be installed -- not where to find applications. I would do something like this: export CPPFLAGS=-I/usr/opt/ncurses-5.2/include export LDFLAGS=-L/usr/opt/ncurses-5.2/lib -lncurses ./configure -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Where config mutt to use lynx and *not* Galeon?
On Wed, Oct 02, 2002 at 12:22:17PM -0700, Will Yardley wrote: Thomas E. Dickey wrote: On Wed, 2 Oct 2002, Elimar Riesebieter wrote: text/html; w3m -dump -T text/html %s; copiousoutput w3m for me is better for viewing tables. how much email do you get that uses tables? A lot, although very little that's not spam. I don't look closely at it though. Apparently a few people use it, both mostly it uses people. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Where config mutt to use lynx and *not* Galeon?
On Wed, Oct 02, 2002 at 05:40:56PM +0200, Elimar Riesebieter wrote: On Wed, 02 Oct 2002 the mental interface of Thomas E. Dickey told: On Wed, 2 Oct 2002, Elimar Riesebieter wrote: [...] (there are several ways to do it) i.e. text/html; w3m -dump -T text/html %s; copiousoutput w3m for me is better for viewing tables. how much email do you get that uses tables? Probably much more than you ;-) undoubtedly. I don't have a lot of use for email which can't be edited with a plain-text editor. (I can format things with lynx+vile, but that doesn't make it any better if I'm responding to something with pine on my his.com account). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Colour problem on NetBSD
On Tue, Oct 01, 2002 at 09:52:34PM +0200, Hanspeter Roth wrote: On Oct 01 at 06:06, Thomas E. Dickey spoke: NetBSD has a strong not-invented-here faction, which is busily porting chunks of ncurses into their native BSD curses. It's not complete, but the latest version reportedly has use_default_colors(). If the entrypoint exists, but does not work as expected that's a NetBSD bug rather than mutt's. If I could manage to build a mutt linked against an standard ncurses5.x then shoud there be a working use_default_colors() available? yes - I added the feature with ncurses 4.2 Bear in mind that when I'm building applications with ncurses, it is usually not using the *BSD ports - I frequently see problems reported that are due to that. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: replying to unwrapped messages with vi
On Tue, Oct 01, 2002 at 07:38:35AM -0400, Thomas E. Dickey wrote: On Tue, 1 Oct 2002, kevin lyda wrote: i find fmt to be more standard across unicies. that's arguable (fmt is likely to be installed, but like most Unix utilities would have version dependencies - par is a relative latecomer and is not installed). There's a difference between installed and standard of course - X/Open documents the latter. now that I'm home can look it up, I see that by its omission from X/Open's list, fmt can be regarded as nonstandard. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Coloring full line in header
On Wed, Sep 25, 2002 at 06:34:33PM -0700, John Iverson wrote: * On Wed, 25 Sep 2002, Thomas Dickey wrote: On Wed, Sep 25, 2002 at 03:34:58PM -0700, John Iverson wrote: * On Wed, 25 Sep 2002, D. J. Bolderman wrote: I want to color my headers, but something goes wrong here. For example: I have the subject colored white, with a blue background, but the rest of the line stays black... I've searched the archives but didn't find a proper solution. I'm using 'color index white blue ^Subject: I think the consensus is that this is an ncurses issue. I fixed it for myself by compiling with s-lang instead of ncurses. uh no - it's a mutt issue. I stand corrected. However, I did experience the same problem of the coloring not extending to the end of the line, and the problem (or behavior or whatever) definitely went away when I switched to s-lang. I spent a few hours looking at it tonight, and saw that (for the case I examined), slang treats the use of colors incompatibly with curses. X/Open curses (e.g., ncurses) essentially stores the information for blanks in what is denoted the background character. Slang doesn't distinguish text and blanks. Mutt makes some calls to set the background character (and sometimes only sets the window attribute, which affects only nonblank text), but the effect of these doesn't match the behavior between slang and curses. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Colour problem on Solaris
On Fri, Sep 27, 2002 at 11:28:55AM +0100, Chris Green wrote: As Sven just pointed out I have been using rather old versions of mutt I have upgraded all my mutts (four of them) to version 1.4i. All of the Linux ones were no problem, just ./configure with the required options, make and install and it worked like clockwork. However the Solaris 2.6 one is proving a bit more difficult. perhaps a library conflict between libncurses and /usr/lib/curses (or the corresponding header files). That's easily spotted in config.log First it didn't add '-liconv' to the Makefile line for linking, I fixed that by adding it manually to the Makefile. Secondly, and more significant, is that colours are not working correctly any more. When mutt loads it complains:- Error in /home/chris/.mutt/muttrc, line 27: default: no such color Error in /home/chris/.mutt/muttrc, line 28: default: no such color ... ... etc. I'm using ncurses 5.0 on both the Solaris version and the Linux versions and the 'default' colour works fine on the Linux versions. I have a sneaking feeling that I remember having this problem before but unfortunately I can't remember how to fix it. -- Chris Green ([EMAIL PROTECTED]) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Where config mutt to use lynx and *not* Galeon?
On Sat, Sep 28, 2002 at 09:13:27AM -0700, [EMAIL PROTECTED] wrote: Default Red Hat 7.3 uses Galeon to read html email in mutt. Where do I change this to lynx??? in your $HOME/.mailcap, a line like this for instance: text/html; lynx-cs -force_html -stdin (there are several ways to do it) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Coloring full line in header
On Wed, Sep 25, 2002 at 03:34:58PM -0700, John Iverson wrote: * On Wed, 25 Sep 2002, D. J. Bolderman wrote: I want to color my headers, but something goes wrong here. For example: I have the subject colored white, with a blue background, but the rest of the line stays black... I've searched the archives but didn't find a proper solution. I'm using 'color index white blue ^Subject: I think the consensus is that this is an ncurses issue. I fixed it for myself by compiling with s-lang instead of ncurses. uh no - it's a mutt issue. ncurses and slang have comparable capabilities in this area, the issue is that mutt isn't calling ncurses to achieve the effect. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Coloring full line in header
On Thu, Sep 26, 2002 at 01:24:29AM +0200, D. J. Bolderman wrote: On Wed, 25 Sep 2002, Thomas Dickey wrote: I want to color my headers, but something goes wrong here. For example: I have the subject colored white, with a blue background, but the rest of the line stays black... I've searched the archives but didn't find a proper solution. I think the consensus is that this is an ncurses issue. I fixed it for myself by compiling with s-lang instead of ncurses. uh no - it's a mutt issue. ncurses and slang have comparable capabilities in this area, the issue is that mutt isn't calling ncurses to achieve the effect. So how do I get Mutt to call ncurses then ? Do I have to recompile or something ?? mutt does - but there are some missing pieces. The calls using the macro BKGDSET are either incomplete, or there is needed some related calls to the bkgd function. #if !defined(USE_SLANG_CURSES) defined(HAVE_BKGDSET) #define BKGDSET(x) bkgdset (ColorDefs[x] | ' ') #else #define BKGDSET(x) #endif (if I had less work to do, I'd have a patch for mutt, but have been busy on - besides my day job - xterm, lynx, ncurses and vile within the past month). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Coloring full line in header
On Thu, Sep 26, 2002 at 02:01:25AM +0200, D. J. Bolderman wrote: On Wed, 25 Sep 2002, Thomas Dickey wrote: So how do I get Mutt to call ncurses then ? Do I have to recompile or something ?? mutt does - but there are some missing pieces. The calls using the macro BKGDSET are either incomplete, or there is needed some related calls to the bkgd function. #if !defined(USE_SLANG_CURSES) defined(HAVE_BKGDSET) #define BKGDSET(x) bkgdset (ColorDefs[x] | ' ') #else #define BKGDSET(x) #endif Would this problem be solved if I upgrade mutt to the cvs version ? Or do I just create more problems then :) no - I haven't noticed any discussion of people working on this. When it first came up a few years ago, I pointed out some of the places and they were addressed. (Actually, when I first saw the slang-configuration for this, I regarded that as a bug - tastes differ though). If someone added it, I would make sure it was optional). (if I had less work to do, I'd have a patch for mutt, but have been busy on - besides my day job - xterm, lynx, ncurses and vile within the past month). Cool, well maybe someone else could write a patch (I don't have the knowledge) because I noticed more people are having this problem. I guess the mutt developers are more interested in other details. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Help with installing mutt 1.4 on AIX
On Tue, Sep 17, 2002 at 03:08:04PM -0400, Bright, Frank wrote: Hi, We are trying to install mutt on AIX. This is version 1.4 of mutt and AIX 4.3.3. The zip is untarred but the program will not execute saying Error opening terminal: wy50. perhaps it was compiled with the location of the terminfo directory set to a nonstandard location (or uses libraries that aren't compatible with AIX's terminfo). There are a few possibilities. Running 'strings' on the binary should show terminfo and/or termcap. If it shows only the former, it is compiled against curses or ncurses; setting TERMINFO to something like /usr/lib/terminfo may fix it. If the latter (termcap), it won't work with AIX's terminfo, but requires a termcap file. Has anyone experienced this problem and how to solve it? Thanks in advance! Frank M. Bright, Jr. Administrative Computing [EMAIL PROTECTED] University of the Arts (A15) www.uarts.edu 320 S. Broad St. 215-717-6081(w) Philadelphia, PA 19102 215-717-6087(f) Colleague 16.461 AIX 4.3.3 Unidata 5.139 -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Following URLs under Cygwin-mutt
On Tue, Sep 10, 2002 at 08:01:33AM +0200, Thomas Baker wrote: It sounds like Gary Johnson's suggestion above (calling Mozilla from w3m) could do the trick, though I guess what I'd really like to do is hand the message off immediately to, say, the mailer in Netscape or Mozilla. or lynx - depending. I noticed the 'M feature in w3m last year and added comparable functionality to lynx - repeating the 'external' viewer lines in lynx.cfg makes it display a menu when invoking the external viewer. For example EXTERNAL:ftp:w3m %s:TRUE EXTERNAL:file:w3m %s:TRUE EXTERNAL:http:w3m %s:TRUE EXTERNAL:ftp:netscape %s:TRUE EXTERNAL:file:netscape %s:TRUE EXTERNAL:http:netscape %s:TRUE -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Following URLs under Cygwin-mutt
On Mon, Sep 09, 2002 at 09:06:24PM +0200, Thomas Baker wrote: In my admittedly limited experience with text browsers, alot of the links came up with unhelpful results like like just Frame 1 and Frame 2, or exited with an error message before showing anything. One could curse those Web editors for making such unfriendly pages, but there are alot of pages like that out there and I guess we have to live with them. I'd be willing to stick it out with text browsers and workarounds if I knew that others really do live with them comfortably. I haven't noticed any html email with frames. (Most html email that I do see is spam, though - and I don't look closely at that). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt colors
On Wed, Sep 04, 2002 at 01:49:26PM +0200, Elimar Riesebieter wrote: Hi all, one of my colorsets is color hdrdefault blackcyan The text, but _only_ the text of my headers is black on cyan. Is it possible to get the whole lines backgrounded in cyan? Tested in xterm, aterm and ttyx. yes - by modifying mutt. It's the way mutt sets up the calls to ncurses which produces this behavior. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt colors
On Wed, Sep 04, 2002 at 02:08:45PM +0200, Elimar Riesebieter wrote: On Wed, 04 Sep 2002 the mental interface of Thomas Dickey told: On Wed, Sep 04, 2002 at 01:49:26PM +0200, Elimar Riesebieter wrote: Hi all, one of my colorsets is color hdrdefault blackcyan The text, but _only_ the text of my headers is black on cyan. Is it possible to get the whole lines backgrounded in cyan? Tested in xterm, aterm and ttyx. yes - by modifying mutt. It's the way mutt sets up the calls to ncurses which produces this behavior. I've seen some screenshots with the behaviour I want in the net? Can't remember the adresses. The slang configuration does this. (I'm offering advice only, since some time ago I sent patches for mutt more than once which were ignored). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: flaming is art - dammit!
On Mon, Sep 02, 2002 at 10:31:15AM +0200, Oliver Fuchs wrote: Hi, for all who are wondering about awnsers on this list please get 'How To Ask Questions The Smart Way' by Eric S. Raymond (utfi). a poor reference, since he rarely posts, does not engage in what one would call dialog, and almost never provides useful information. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: flaming is art - dammit!
On Mon, Sep 02, 2002 at 12:08:33PM +0200, Oliver Fuchs wrote: Thank you for your advice. ( no problem ;-) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt color limitations
On Tue, Aug 20, 2002 at 11:16:55PM +0100, Lee J. Moore wrote: On Tue, 20 Aug 2002, Philip Wittamore wrote: Hmm.. I compiled mutt with slang, and I discovered that contrary to ncurses, the headers now had background colour to the end of the line, but brightblack no longer worked. (tried with xterm, rxvt, aterm and konsole) ROFL (slang, cited as a standard) Yep, same here. Considering the number of terminals I've used and the fact that they all support sixteen colours with other apps, I find it difficult to believe it's not Mutt at fault. No amount of googling turns up solutions, nor posting to the list. Maybe it's only a minority of Mutt users who want more than eight colours. 8 colors are standard (the majority of those 16-color applications are assuming that bold colors are bright - which is not a valid assumption in many cases). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: option description - always give default value
On Sun, Aug 04, 2002 at 04:22:03AM +0200, Sven Guckes wrote: * Cameron Simpson [EMAIL PROTECTED] [2002-08-04 01:02]: On my systems I frequently have several mutts installed. Each has its own manual page because each has its own install tree. The /usr/local/bin/mutt is a symlink to the appropriate mutt binary in its respective tree, and so is the manual entry. Users wanting the nondefault mutt put /opt/mutt-version/bin in their PATH and /opt/mutt-version/man in their MANPATH. Users like history majors and non-cs minors never edit their PATH because they no freakin' clue about this. that's too broad a generalization. Last week I was having a nice chat with a fellow whose field of expertise is economics. He's also a well-known contributor to XEmacs... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: exceptional people
On Sun, Aug 04, 2002 at 08:00:07PM +0200, Sven Guckes wrote: * On Sun, Aug 04, 2002 at 04:22:03AM +0200, Sven Guckes wrote: Users like history majors and non-cs minors never edit their PATH because they no freakin' clue about this. * Thomas E. Dickey [EMAIL PROTECTED] [2002-08-04 15:52]: that's too broad a generalization. Last week I was having a nice chat with a fellow whose field of expertise is economics. He's also a well-known contributor to XEmacs... and i met a composer who programs in assembler and i met a surgeon who gave courses on unix. but these people *are* exceptions! true. but among the population of programmers, the fraction that produce anything useful is also so small as to be negligible (certainly less than 5%). however, there are many people who open Word to send an email. and i would never suggest that they should be using mutt. after all i dont want the RSPCA chasing me.. ever done support for a newbie? i bet some of you know how it is: sure - as well as get tech-support from people who work from a checklist (did you set $PATH, did you set $DISPLAY). fortunately for my state of mind, the worst of those are over in Redhat's mailing lists, to which I won't subscribe because of the volume... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Setting tab size in pager
On Mon, Jul 29, 2002 at 01:22:53PM -0700, Jim Osborn wrote: How can I control the number of spaces a tab character uses when reading mail in the pager? Mutt 1.3.99i. It appears to be hardcoded (to 8). Most versions of curses assume 8. (ncurses allows you to set it in the TABSTOP variable - which I noticed recently is not in the manpage). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Setting tab size in pager - set pager=vim -c ts=4 -
On Tue, Jul 30, 2002 at 01:53:57AM +0200, Sven Guckes wrote: * Thomas E. Dickey [EMAIL PROTECTED] [2002-07-29 21:37]: On Mon, Jul 29, 2002 at 01:22:53PM -0700, Jim Osborn wrote: How can I control the number of spaces a tab character uses when reading mail in the pager? Mutt 1.3.99i. It appears to be hardcoded (to 8). Most versions of curses assume 8. yes, the builtin pager has no options. however, you can use other pagers such as vim which would allow this. set pager=vim -c ts=4 - I added the ^T (toggle tabs) to tin sometime around 1994. There are a lot of newspostings that assume tabs are set to 4. So it's probably useful in some contexts. People tend to not format their email quite as rigorously... (But it's generally useful to be able to switch easily, since some files are a mixture of tab styles). (ncurses allows you to set it in the TABSTOP variable - which I noticed recently is not in the manpage). tsk tsk tsk... ;-) ;-) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Numeric Keypad Malfunction -- Mutt, Vim, Gnome-Terminal
On Fri, Jul 26, 2002 at 07:09:23PM -0400, John P Verel wrote: On 07/26/02 16:41 -0400, John P Verel wrote: Upon further investigation, I find that the keypad works fine under vim, run in an xterm and in rxvt. So, the culprit, I suppose, is gnome-terminal. I'll head on over the the RedHat Limbo beta list and see if I can learn anything there. I've learned that this numpad/vim issue is a well know bug with the current gnome-terminal. I've also learned that the Redhat Limbo Beta version of gnome-terminal is 100% re-written and that it is working correctly. maybe (I reviewed it, and was not able to see numeric keypad working properly) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Header color - color header fg bg regexp
On Thu, Jul 25, 2002 at 02:35:34PM -0700, John Iverson wrote: * On Thu, 25 Jul 2002, Sven Guckes wrote: * V_Suresh [EMAIL PROTECTED] [2002-07-25 08:09]: How do I set the bg/fg color for the whole line, for a particular header field?? Not just for the header alone, but the whole line should have the same bg color?? How is this possible?? color header fg bg regexp I think he means that this command is only coloring to the end of the last word in the header and not all the way to the end of the line on his screen. I noticed this behavior before, too, and when I switched from ncurses to s-lang, it started doing the whole line. It may depend on terminal settings or something else, too? either that (not choosing a terminal type that tells whether it can clear using the background color), or one of the cases where mutt doesn't setup the curses calls properly -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Header color - color header fg bg regexp
On Thu, Jul 25, 2002 at 04:43:30PM -0600, Rob 'Feztaa' Park wrote: This has come up before; I could be wrong, but I thought the general consensus was that ncurses won't do the whole line, while slang does. Maybe I'm imagining things, though ;) no - the issue (for mutt/ncurses) is whether mutt calls the functions that tell ncurses to fill the line with the background color. I pointed out some of those a couple of years ago to someone who submitted patches for mutt, while some other cases were less obvious. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Numeric Keypad Malfunction -- Mutt, Vim, Gnome-Terminal
On Thu, Jul 25, 2002 at 07:05:43PM -0400, John P Verel wrote: I cannot get my numeric keypad to work with Mutt. Here's my environment: I run Mutt 1.4-2 in gnome terminal, provided by gnome-core-1.4.0.4-54. My editor is vim 6.1-2. I start vim with this command: set editor =vim +/^$ +'set nobackup' The numeric keypad works correctly within gnome-terminal (e.g. writing code), works fine within mutt, if run from xterm or rxvt. However, if I edit with vim, within mutt, run in a gnome-terminal, the numeric keypad does not work correctly. For example, I press the number 1 on the keypad, I get the letter q inserted above the current line. for xterm it's simple to see what's going on - look at the control/middle/mouse menu at the Enable Application Keypad line. When you run a full-screen app it generally initializes the cursor- and numeric-keypads to application mode. xterm emulates a vt100 in this area, which sends escape sequences for the numeric keypad. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: UTF 8 / ACS question
On Thu, Jul 18, 2002 at 02:16:03PM -0400, Ken Weingold wrote: The Mac OS X Terminal does not have much support for anything but vt100, so the mutt threading has to be set to with ascii_chars. In the next release of OS X, 10.2, the terminal has UTF 8 support. I don't know much about this, and the mutt manual says that threading by default uses ACS characters. Are these two related in that the new Terminal will display the mutt threading correctly with ascii_chars set to no? not really (ACS standards for alternate-character-set - which does not apply to Unicode or UTF-8). It's coincidental - mutt has hardcoded UTF-8 strings for the line-drawing characters that correspond to the vt100 alternate character set. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: color of indicator bar
On Wed, Jul 17, 2002 at 02:39:20PM +0200, Rocco Rutte wrote: Hi, I remember to have a read about about a patch making the indicator bar always exactly the same color as specified. The problem is that if the color of the message in the index is ``bright...'', the foreground color of the bar gets bold, too. But I want it to be ``black'' instead of ``brightblack'' on some messages. Hints? You can't (in general). bold/bright/whatever attribute applies to both foreground and background colors (it's actually terminal-dependent). If you have a terminal that implements 16-colors you may be able to do that - with ncurses or slang. Regular curses implements 8 colors. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 internal pager, Screen 3.09.11: right-padded spaces
On Thu, Jul 11, 2002 at 07:14:38PM -0700, Rick Moen wrote: Quoting Thomas Dickey ([EMAIL PROTECTED]): [my infocmp output snipped] ...and no bce. Recent versions of screen allow you to set bce in its configuration, but you have to install a terminfo entry for screen which adds 'bce', so it will work properly. I fear we might be trying to solve the wrong problem, here. You see, I've only had defbce on in /etc/screenrc and the aforementioned ~/.terminfo/s/screen entry (symlinked to /usr/share/terminfo/s/screen-bce ) to inform screen that the terminal supports BCE for _two days_, and the symptom appeared a year or so ago. but your listing from infocmp didn't show that. Ordinarily, I'm very careful not to introduce more variables into a diagnostic situation: I chanced enabling Background Color Erase support two days ago only because I kept careful track of those steps, so I could reverse them. Which I've just done: I commented out defbce on in /etc/screenrc, removed ~/.terminfo/ , terminated screen, and restarted it. Running infocmp again (under screen), one now sees: the same as before: the 'screen' terminfo which has no 'bce' capability. :r! infocmp # Reconstructed via infocmp from file: /etc/terminfo/s/screen screen|VT 100/ANSI X3.64 virtual terminal, am, km, mir, msgr, xenl, -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Home/End mapping on Sun keyboard
On Fri, Jul 12, 2002 at 10:10:37AM -0400, Mark J. Reed wrote: I get the Key is not bound message on my Linux PC, too. Where did you see the reference in the documentation? There may be a more significant problem, though. On the PC, both keys actually send something to the terminal window (Home key sends ESC[1~; End key sends ESC[4~). On my Sun, pressing the keys sends an event that X recognizes but no characters to the terminal window at all, so there's no way a terminal program like mutt can do anything with them. generally that's done in the system-level app-defaults file for xterm (though I recall this in the context of pageup/pagedown, which Sun prefers to map to the scrollbars). In that case, it's possible to override it by tweaking your .Xdefaults file. You could use xmodmap to modify the bindings on those keys to something that a terminal program can detect, but then they would stop working properly in GUI applications. ;-) however, since he's getting key-not-bound, none of this applies... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 internal pager, Screen 3.09.11: right-padded spaces
On Fri, Jul 12, 2002 at 11:49:29AM -0700, Rick Moen wrote: I do find it odd that the symptom showed up _only_ with mutt's internal pager, and not when using less in its place. But all's well that ends well. less doesn't know anything about color, so it would simply erase rather than fill. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 internal pager, Screen 3.09.11: right-padded spaces
On Wed, Jul 10, 2002 at 09:04:09PM -0700, Rick Moen wrote: When I ssh in from my X11 desktop to my server (both Debian 3.0) and start sessions under GNU Screen (v. 3.09.11), among which are Mutt (v. 1.3.28) instances, I get a weird effect with Mutt's internal pager: If I highlight text from Mutt's internal pager and use X11 copy/paste to copy it to elsewhere, there is right-side padding of all lines of text. Most lines get padded all the way to column 80. Some shorter lines get less (and I'm not sure what the pattern is). Text copied/pasted from vim (as Mutt editor), or from less used in place of the internal pager, don't show this symptom. If I exit from Screen entirely, then start up Mutt and use its internal pager, X11 copy/pastes from the internal pager do NOT show that effect. So, something unhealthy's going on between Mutt's internal pager and Screen. :r! echo $TERM screen but what does infocmp show? (screen's terminfo normally doesn't say bce) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt window copy/paste (Correction)
On Mon, Jul 08, 2002 at 09:01:53PM -0700, Deb wrote: Thomas Dickey [EMAIL PROTECTED] had this to say, On Fri, Jul 05, 2002 at 01:13:47PM -0700, Deb wrote: I forgot to mention that I'm using xterm-166, with terminfo xterm-color, on Solaris, Sparc. Not sure the xfree86 is appropriate for this platform? But xterm-color usually says that the terminal doesn't implement back color erase (bce). In that case, most full-screen applications will write explicit blanks, which xterm's select/paste will preserve. Hold on. The behavior holds for *both* xterm and xterm-color, and I just tested F-secure ssh Windoze client - and it also exhibits the same behaviour - the only common denominator is using mutt and copying/ pasting text from a displayed message. not if we're talking about the same thing. xterm stores a null in each cell for places which are erased, and a non-zero code otherwise. When someone selects data, it supplies blanks in place of embedded nulls, but does not change trailing nulls to blanks. It stores a flag to tell if the text was wrapped, so selections of wrapped lines work as expected. So the only real issue (for xterm) is whether the application wrote trailing blanks to the screen. Since XFree86 xterm implements bce and (unless you're running FreeBSD ;-), xterm-color doesn't mention bce, applications using $TERM set to xterm-color will fill cells with explicit blanks, while using the terminfo which I supplied with xterm, they'll rely on the terminal's behavior - and generally not use blanks except where it's faster than some other way. Applications such as 'screen' tend to confuse the issue of course. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt window copy/paste (Correction)
On Mon, Jul 08, 2002 at 09:01:53PM -0700, Deb wrote: I would consider this a bug. ( sure - but not in mutt or xterm ;-) I still respectfully disagree (see above). You may find this enlightening (man xterm): highlightSelection (class HighlightSelection) If ``false'', selecting with the mouse highlights all positions on the screen between the beginning of the selection and the current position. If ``true'', xterm highlights only the positions that contain text that can be selected. The default is ``false.'' -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt window copy/paste (Correction)
On Tue, Jul 09, 2002 at 08:23:17AM -0700, Deb wrote: Thomas Dickey [EMAIL PROTECTED] had this to say, You may find this enlightening (man xterm): highlightSelection (class HighlightSelection) If ``false'', selecting with the mouse highlights all positions on the screen between the beginning of the selection and the current position. If ``true'', xterm highlights only the positions that contain text that can be selected. The default is ``false.'' Yes, it is. The F-secure window is vt100, which perhaps does confuse the issue. F-secure isn't the same program as xterm anyway - but it's likely that it makes analogous tradeoffs for keeping track of selections. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt window copy/paste (Correction)
On Fri, Jul 05, 2002 at 07:40:17PM +0200, Vincent Lefevre wrote: On Fri, Jul 05, 2002 at 10:18:01 -0700, Deb wrote: When I copy multiple lines of text from a message I'm reading in mutt, then paste that text into a different window, all the lines are post-appended with space padding and a NL is on the end of the line at the window edge. This is a FAQ. You should use a terminal that have bce support (like the Xfree86 xterm) and terminfo data that announce bce. If you use ncurses 5.2 terminfos, TERM=xterm-xfree86 and TERM=xterm-vt220 should be OK for the Xfree86 xterm. BTW, this doesn't solve all the problems. I sometimes notice trailing spaces in headers. There's more than one possibility here (including bugs, of course). For instance, the header may have been written on top of some existing blanks, and the optimization takes that into account. For xterm, the spaces that are copied via mouse-selection are from explicit writes to those positions since the last clearing operation, e.g., erase-display, erase-line. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt window copy/paste (Correction)
On Fri, Jul 05, 2002 at 01:13:47PM -0700, Deb wrote: I forgot to mention that I'm using xterm-166, with terminfo xterm-color, on Solaris, Sparc. Not sure the xfree86 is appropriate for this platform? But xterm-color usually says that the terminal doesn't implement back color erase (bce). In that case, most full-screen applications will write explicit blanks, which xterm's select/paste will preserve. I suspect what Thomas Dickey stated is closest to the truth, that the spaces are explicit writes to those positions. And a test with both the /usr/openwin/bin/xterm and xterm-166 both show this to be the case - but ONLY when using mutt. It doesn't seem related to the window interface at all, but instead to how mutt is drawing the picture. I would consider this a bug. ( sure - but not in mutt or xterm ;-) deb * Thomas Dickey [EMAIL PROTECTED] [2002-07-05 13:56:52 -0400]: On Fri, Jul 05, 2002 at 07:40:17PM +0200, Vincent Lefevre wrote: On Fri, Jul 05, 2002 at 10:18:01 -0700, Deb wrote: When I copy multiple lines of text from a message I'm reading in mutt, then paste that text into a different window, all the lines are post-appended with space padding and a NL is on the end of the line at the window edge. This is a FAQ. You should use a terminal that have bce support (like the Xfree86 xterm) and terminfo data that announce bce. If you use ncurses 5.2 terminfos, TERM=xterm-xfree86 and TERM=xterm-vt220 should be OK for the Xfree86 xterm. BTW, this doesn't solve all the problems. I sometimes notice trailing spaces in headers. There's more than one possibility here (including bugs, of course). For instance, the header may have been written on top of some existing blanks, and the optimization takes that into account. For xterm, the spaces that are copied via mouse-selection are from explicit writes to those positions since the last clearing operation, e.g., erase-display, erase-line. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net -- If it dies, it's biology. If it blows up, it's chemistry, and if it doesn't work, it's physics. -- University bathroom graffito ô¿ô ~ -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: displaying folder name in xterm title
On Thu, Jul 04, 2002 at 04:17:13PM +0200, Aragon Gouveia wrote: Hi, There must be a way. It should just be a matter of sending the right escape sequence to the terminal. You can probably do this in the status_format. The question's come up a few times - I don't recall the answer, myself. It has to be done outside the normal screen operations since those would translate the escape sequence into readable form. I think the escape sequences are as follows: \033]0;whatever you want in the title\007 There are also escape sequences for the window name and the icon name. Probably \033]1; and \033]2; respectively. I'm not sure which is which. But googling it should reveal something. That's likely (they're documented in a number of places including of course xterm). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: forcing mutt to think in mono
On Fri, Jun 28, 2002 at 08:44:09PM -0500, David T-G wrote: Hi, all -- Since I've moved over to FreeBSD I've found a few things different from the Linux world, and I'm starting to adjust to them :-) For one, now mutt insists on being all colorful, which just sucks for me. Is there any way to force mutt into mono mode? I've found colors that are kinda right but when, for example, I pipe a message I have to watch this screen repaint of all black (the default background) and then all white (my chosen background) and then the same thing when the job is done; it's a real bummer. Not only is it distracting, but it's slow; mutt has to repaint the entire screen. is that in the console, or xterm? -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: forcing mutt to think in mono
On Fri, Jun 28, 2002 at 09:02:42PM -0500, David T-G wrote: Hi! ...and then William Park said... % % On Fri, Jun 28, 2002 at 08:44:09PM -0500, David T-G wrote: ... % For one, now mutt insists on being all colorful, which just sucks for me. % Is there any way to force mutt into mono mode? % % Mutt defaults to colour in Linux too. So, copy over your .muttrc to new % machine. No dice; I did (and found that BSD regexps are different from GNU regexps, so I had to rewrite some of it -- and I've added this color junk, too!). Perhaps it's not fair to say that mutt defaults to color; perhaps it's a different implementation of xterm (my term type) or vt100 (what screen tells the apps I am). recent (since last year) versions of screen add you use back-color-erase (bce) to its terminfo description - so that would save on painting things to the background color. bce [on|off] Change background-color-erase setting. If bce is set to on, all characters cleared by an erase/insert/scroll/clear operation will be displayed in the current background color. Otherwise the default background color is used. screen uses 'vt100' if there's nothing more suitable (and it isn't really emulating vt100 anyway - it's compatible, which is not the same thing). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt+X+jpg viewing
On Sat, Jun 15, 2002 at 10:36:10AM +0100, Dean Richard Benson wrote: Hi all I normally use mutt through a konsole session in KDE. (for my sins). At the moment when an email contains a jpg/gif image, I have an auto converter to ascii art, which is great. But I have been thinking is it possible for mutt/my environment to detect that I am in X and launch an x graphics viewer instead somehow? it's possible to modify mutt - but depending on how your mailcap is setup, may be just as easy to modify the script that runs the viewer. what's involved - an application is needed to quietly check if the X display can be opened. This topic has come up occasionally, and usually devolves into a discussion of the $DISPLAY variable, which can be misleading. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Display problems with non-7bit text
On Fri, Jun 14, 2002 at 10:34:14AM +0100, Richard Curnow wrote: I've been following the UTF-8 discussion. For me, I can't even get iso-8869-1 characters in the 128-255 range to display correctly. you don't mention what your locale is set to (e.g., $LC_ALL and related environment variables). That's independent of slang/ncurses. mutt is supplying the ?'s. To display UTF-8 with ncurses, you need the wide-character version libncursesw. ISO-8859-1 works either way. The content-type line in the message looks like: Content-Type: text/plain; charset=iso-8859-1 and if I 'more' or 'cat' the message to the terminal (I'm using maildir), the accented characters show up fine, so the terminal is basically up to the job and has a font with the characters in it. However, inside mutt's pager I get varying forms of junk depending on the setting of charset, e.g. charset=us-ascii gives e? charset=iso-8859-1 gives \344\341\337\351e\350 charset=utf-8 gives \303\244\303\241\303\237\303\251e\303\250 (OK, not much of a surprise) The output of 'cat' correctly shows the 6 characters: a-umlaut a-acute scharfes-S e-acute plain e e-grave This is mutt 1.4i, I have the problem with either xterm or rxvt, and with both slang and ncurses builds of mutt. Where's my problem? Cheers Richard -- Richard \\\ SuperH Core+Debug Architect /// .. At home .. P./// [EMAIL PROTECTED] /// [EMAIL PROTECTED] Curnow \\\ http://www.superh.com//// www.rc0.org.uk Speaking for myself, not on behalf of SuperH -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Display problems with non-7bit text
On Fri, Jun 14, 2002 at 10:18:12AM -0400, Mark J. Reed wrote: On Fri, Jun 14, 2002 at 10:10:42AM -0400, Mark J. Reed wrote: Could you direct me to an appropriate site whence I can download [libncursesw]? Never mind, I answered my own question with some web searching; standard ncurses source will build libncursesw if configured with the --enable-widec option. Thank you anyway. :) you really need the post-5.2 patches, since ncursesw was only tentative at that point. The rollup patch should be sufficient - ftp://invisible-island.net/ncurses/5.2 -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: weird color behaviour with aterm rxvt
On Sun, Jun 02, 2002 at 01:41:55PM +0200, Maximilian Szengel wrote: Hi, I've just edited my mutt colors to have a white background. (color normal black white etc.) I am using aterm and when I call mutt with the white background setting it looks awful, not white. Have a look at the screenshot [1]. I tried it with rxvt and it looks the same. Am I doing something wrong? Maybe it's not mutt's fault, then just ignore this post and I am going to find help somewhere else. 1. http://che23.de/mutt_aterm.jpg That looks like you're using ncurses 5.2 with the experimental $COLORTERM support (it doesn't work for bright backgrounds). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: weird color behaviour with aterm rxvt
On Sun, Jun 02, 2002 at 07:11:15PM +0200, Maximilian Szengel wrote:
Basically what happens is that it's specifying a background color 15,
while the terminfo says there's only 8 colors. (I considered adding
a special case for this, but decided that the proper solution would be
to use an appropriate terminfo).
How can I edit the terminfo to a proper one?
for example, running tic on this, and setting $TERM to rxvt-bright:
rxvt-bright|variant which works with bright backgrounds,
ncv#32,
bold@,
setab=\E[1m\E[4%p1%dm,
use=rxvt,
That's assuming that rxvt was not compiled with bright-color support, and
is just trying to fake a bright background. Another variant would be
analogous to xterm-16color:
rxvt-16color|using aixterm 16-color sequences,
colors#16,
pairs#256,
setab=\E[%?%p1%{8}%%t%p1%'('%+%e%p1%{92}%+%;%dm,
setaf=\E[%?%p1%{8}%%t%p1%{30}%+%e%p1%'R'%+%;%dm,
I tried the first on Debian whose rxvt is 2.6.4 (which doesn't support
bright colors as in the second example).
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: vi :s vs sed
On Sat, May 25, 2002 at 12:00:21PM +0200, Nicolas Rachinsky wrote: * Cameron Simpson [EMAIL PROTECTED] [2002-05-25 19:00:05 +1000]: On 02:15 25 May 2002, Sven Guckes [EMAIL PROTECTED] wrote: | If you mess up, u undoes any number | of edits. [Cntrl]R undoes the undos. | will work for elvis and vim only. | won't work when vi is nvi. Of course, unless you've been careless, one level of undo is plenty. I speak, of course, as another happy nvi user. There are multiple levels of undo with nvi. Press u and then multiple times .. u again and ... is the redo operation. certainly (and it's well-documented). but since it's normally not bound to ^R, perhaps Sven regarded that as the deficiency. vile uses ^X-r (control/X followed by r). I also have that mapped to alt-r. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt colors with X
On Mon, May 20, 2002 at 05:04:53AM -0400, Andy Saxena wrote: On Sun, May 12, 2002 at 12:23:06AM -0600, Rob 'Feztaa' Park wrote: Alas! Will Yardley spake thus: if you're using xterm, you probably want to set TERM to xterm-xfree86. For the record, I use xterm's exclusively on my system, and I've got $TERM set to xterm-color, and everything colors just great. Mutt, Vim, everything ;) Just a quick question for you - is the background on your xterm dark or light? I am asking because vim sets background correctly for me in the console, but fails to detect the black background in an xterm/konsole window. The same goes for mutt, it colorizes as though the background was light colored. generally it _cannot_ detect whether the background is light or dark. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: bind ^H to backward-char in editor
On Sat, May 18, 2002 at 01:50:30PM +0200, Wojciech Krygier wrote: Under xterm $TERM was also 'linux' (I don't even remember why and when I've changed 'xterm' to 'linux' for xterms :-). After setting it to if you don't know, then it's a little hard to help... (start by reading the xterm manpage) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: bind ^H to backward-char in editor
On Tue, May 14, 2002 at 10:23:38AM +0200, Wojciech Krygier wrote: Just in case it might be helpful: bind editor \ch backward-char works fine here, even without unbinding its previous action, so it seems that it isn't mutt fault. I would check the terminal definitions instead. Try console first. it does sound as if mutt's getting control-h bound to one of the KEY_xxx symbols in curses/ncurses based on the terminfo and therefore not seeing the conflicting rebind of control-h -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: ugly thread tree display
On Sun, Apr 21, 2002 at 05:37:05AM +0200, Sven Guckes wrote:
* Alain Bench [EMAIL PROTECTED] [2002-04-14 21:57]:
I use mutt in 3 ways:
...
- running remotely on a Linux box, Mutt started from Cygwin thru it's
own /bin/telnet.exe (again in a Bash session inside a cmd.exe window).
Same thing: Nice charset, bad trees. Note I had to copy Cygwin's
terminfo definition file to the Linux disk for this to work at all.
telnet.exe sucks. use putty.exe. nuff said.
...and for the benefit of those who will (I fear inevitably) followup
with the advice to set $TERM to xterm-color
comparing putty to xterm-color.
comparing booleans.
OTbs: F:T.
bw: T:F.
ccc: T:F.
comparing numbers.
comparing strings.
blink: '\E[5m', NULL.
civis: '\E[?25l', NULL.
cnorm: '\E[?25h', NULL.
ech: '\E[%p1%dX', NULL.
hpa: '\E[%i%p1%dG', NULL.
initc:
'\E]P%?%p1%{9}%%t%p1%{10}%-%'a'%+%c%e%p1%d%;%p2%{255}%%Pr%gr%{16}%/%Px%?%gx%{9}%%t%gx%{10}%-%'A'%+%c%e%gx%d%;%gr%{15}%%Px%?%gx%{9}%%t%gx%{10}%-%'A'%+%c%e%gx%d%;%p3%{255}%%Pr%gr%{16}%/%Px%?%gx%{9}%%t%gx%{10}%-%'A'%+%c%e%gx%d%;%gr%{15}%%Px%?%gx%{9}%%t%gx%{10}%-%'A'%+%c%e%gx%d%;%p4%{255}%%Pr%gr%{16}%/%Px%?%gx%{9}%%t%gx%{10}%-%'A'%+%c%e%gx%d%;%gr%{15}%%Px%?%gx%{9}%%t%gx%{10}%-%'A'%+%c%e%gx%d%;',
NULL.
kbs: '\177', '^H'.
kcbt: '\E[Z', NULL.
meml: NULL, '\El'.
memu: NULL, '\Em'.
oc: '\E]R', NULL.
op: '\E[39;49m', '\E[m'.
rmam: '\E[?7l', NULL.
rmso: '\E[27m', '\E[m'.
rmul: '\E[24m', '\E[m'.
sgr:
'\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;m%?%p9%t\016%e\017%;', NULL.
smam: '\E[?7h', NULL.
vpa: '\E[%i%p1%dd', NULL.
freely translated:
I suppose it'll work, but with less functionality than I'd like.
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: ugly thread tree display
On Sat, Apr 20, 2002 at 09:45:29PM -0600, Rob 'Feztaa' Park wrote: Alas! Sven Guckes spake thus: telnet.exe sucks. use putty.exe. nuff said. I disagree. /usr/bin/ssh beats both of them ;) ssh (usually) doesn't do terminal emulation. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Blank index?!?
On Sun, Apr 07, 2002 at 02:12:55PM -0700, jennyw wrote: I was using mutt and everything was fine. Then I exited and ran mutt again ... The index didn't show any subjects, froms, etc.! I logged out and logged in again ... same thing. I su'ed to root and ran the same muttrc and it worked okay. Very weird. Then I su'ed to another user and ran the same muttrc and I got the same blank-ish screen. Any ideas? I'm currently logged in as root to send this, since it's the only way I can get a functioning mutt ... I'm attaching a copy of the text screen (it has terminal characters in it ... I'm not really sure how to do a screen capture, so I just did muttblankmutt and killed mutt). that doesn't always work as you would like. this case maybe - but 'script' is a good tool to capture the output. (no, I don't know why mutt would do that, either - there was some report a few weeks ago where the pager came up blank). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: syntax highlighting in mutt
On Fri, Apr 05, 2002 at 07:56:14PM -0500, David T-G wrote: Shawn -- ...and then Shawn McMahon said... % % begin quoting what David T-G said on Fri, Apr 05, 2002 at 06:01:44PM -0500: % % I don't know of any pagers (ie, not meant to be an editor but instead % just a file viewer) that do syntax highlighting, though that doesn't at % all mean that they aren't out there. % % vim, if called as view, is a pager. Well, yeah; the same as if you use -R. But it's an editor that's simply in read-only mode, not a pager, and so it is a little clunkier to jump forward by whole pages (you can't just hit the space bar like you do with the rest of your mail messages). you could make a shell-script wrapper to customize the keys. I do something like that for vile (not for keys, but to format a manpage on-the-fly and view it with vile). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: line drawings showing threads gone with REMOTE session!?!?!?
On Mon, Mar 25, 2002 at 04:03:29PM -0800, Christian Seberino wrote: My .muttrc is set up to sort mail by threads rather than exclusively by date. Mutt draws nice lines and indents child emails of a thread nicely. I tried to log into this PC REMOTELY and these REMOTELY via what type of connection or terminal emulator? nice features did NOT come out anymore?!!? How do I get these lines again remotely??? Thanks, Chris -- === | Dr. Christian Seberino || (619) 553-7940 (office) | | SPAWARSYSCEN 2363 || (619) 553-2836 (fax)| | 53560 HULL ST || | | SAN DIEGO CA 92152-5001 || [EMAIL PROTECTED] | === -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: spaghetti threads
On Sun, Mar 24, 2002 at 02:51:28PM +, jmc wrote: Hi! Is anyone else having trouble with threads that look like spaghetti? The following is from one of my mail boxes: 5 L Mar 23 [EMAIL PROTECTED] willing slave 6 L Mar 23 Artur Grabowski |-- 7 L Mar 23 Morten Liebach | |-- 8 L Mar 23 Robert Urban| |- 9 L Mar 23 Justin Honold| |-- 10 L Mar 23 Theo de Raadt| |-- 11 L Mar 23 Jeremy Kuhnash||-- 12 L Mar 23 ecoli |-* 13 L Mar 23 Matt Westfall a.k.a. Erkdog |-- 14 L Mar 23 shrimpcookie |-- Obviously I cannot draw the threads, so I used the |. That's not the problem, it's the lack of alignment - the thread is *never* aligned. I think perhaps I have changed some setting and screwed it all up without meaning to, but I don't know what. some problem with locale perhaps (when one part of the program doesn't keep track properly of how many cells an accented character takes up). The picture you show doesn't quite look like a problem with tab expansion, though that's also something to look for. All thread variables are as default in the Muttrc file, the only things I have set are: set sort=threads set strict_threads=no Oh yeah, it's Mutt 1.3.27i, +HAVE_COLOR and +HAVE_CURS_SET. well, with HAVE_CURS_SET, that sounds like curses or ncurses. I don't see any clues about version or platform. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: spaghetti threads
On Sun, Mar 24, 2002 at 03:33:19PM +, jmc wrote: Sorry, it's running on GNU/Linux, no platform :-) Home made. Ncurses version 5.2. I really don't know anything about locale, I simply run the machine at UCT, and always compile with --disable-nls, because I only use US_English settings. If it's relevant I also have -LOCALES_HACK. Also I never had this problem running Mutt 1.2.25i, it's only since running 1.3.27i that it's started although my libc was upgraded about the same time. Tab expansion? Sorry, I don't follow. How could I check? that's simpler to see (but less likely). ncurses can be configured to send tab characters (making some optimizations a little better), but not all terminals/drivers are setup properly. I'd just run mutt in 'script' and see if the resulting typescript has tab characters (that would tell me if I might want to look further, e.g., if tabs are expanded at every 8th column). diagnosing a problem with the locale stuff is harder to see where to start... Thanks for your reply, if you have any other thoughts or need any more info. I'd be happy to hear them. Ta, jmc. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Tue, Mar 19, 2002 at 09:46:08PM -0600, Jeremy Blosser wrote: $COLORFGBG is marked as an experimental feature. I've gotten 2-3 reports of this particular problem - but only months after I stumbled on it myself. Apparently one or more of the rpm's last year turned that feature on, though it was in the code almost a year. Well, I think it was more the other bug where it would get turned on if other development features like hard-tabs were turned on. It was apparently a combination of these two. I suppose so - though both features are in the same category (not part of the default options): Development Code: --with-develop enable all development options --enable-colorfgbg compile with $COLORFGBG code --enable-hard-tabs compile with hard-tabs code --disable-root-environ limit environment when running as root --enable-xmc-glitch compile with limited support for xmc (noting now that colorfgbg is development rather than experimental, I guess my reasoning at the time was that it was a small feature that wouldn't break much ;-). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Fri, Mar 15, 2002 at 03:40:57PM -0500, Pavel Roskin wrote: Hello! I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. what $TERM value? It turns out that the default configuration uses ncurses-5.2. I tried configuring Mutt with slang-1.4.4. It works fine. My guess is that Mutt does something with page switching that the newer versions of ncurses don't like. I believe it's a major bug that will be a frequently asked question as soon as mutt-1.4 is released. I checked the lists to see if it's not already a frequently asked question. There is a very similar description of the problem, except that it's not specific about software versions: http://marc.theaimsgroup.com/?l=mutt-usersm=101062129425997w=2 That doesn't sound the same. The closest I can recall from this list is one that says the pager comes up blank - both ncurses and slang. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: editors and paragraphs
On Thu, Mar 14, 2002 at 09:21:49AM +, Dave Pearson wrote: * Sven Guckes [EMAIL PROTECTED] [2002-03-13 17:40:27 +0100]: * MuttER [EMAIL PROTECTED] [020313 14:17]: Many editors would have difficulty recognizing and parsing your date format. Which editors parse for dates? examples? (anyone?) Some people consider emacs to be an editor. the standard joke on that topic is that emacs is an operating system in need of a good editor (ymmv). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Subject: Re: Opening html links in text mail
On Thu, Mar 14, 2002 at 02:40:27PM -, The spice must flow wrote: * On Wed, Mar 13, 2002 at 10:09:09PM -0500, Joel Hammer wrote: I used to highlight and copy the address into the browser (netscape). But, this seems a bit clumsy. It was clumsy, in fact. For the Cygwin mutt users among us, I do the following to view URLs in IE by highlighting the link then pressing F11 (it uses Window's start, assumes you are using rxvt and have installed perl and misc-0.9.2-1.tar.gz): 1. Create shell script viewurl: #!/bin/sh clipboard=`getclip | perl -pe 's/\n?\r?//g'` start $clipboard 2. Add this to .muttrc: macro pager F11 ! viewurl\n Simulate the real urlview by spawning IE which part is dependent upon rxvt? (other terminal windows, including the console-window that cygwin runs in would suffice). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: OT: date references as [yymmdd]
On Wed, Mar 13, 2002 at 09:04:19AM +, Simon White wrote: 13-Mar-02 at 09:35, Sven Guckes ([EMAIL PROTECTED]) wrote : I started using [yymmdd] as a date indicator on my webpages before Markus Kuhn wrote ISO-8601 (in 1995) - so sue me! ;-) Well, that's no excuse for not having become year 2000 compliant. The big your use of the word compliant is an abuse (try to think about what you're saying before you start typing). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: NetBSD build problems - -lcposix?
On Tue, Mar 12, 2002 at 01:32:01PM -0800, Ken Weingold wrote: I am trying to build mutt even with no configure options, and get this in config.log: configure:1109: checking for strerror in -lcposix configure:1128: gcc -o conftest -g -O2 conftest.c -lcposix 15 /usr/bin/ld: cannot open -lcposix: No such file or directory that's normal (the script is checking if strerror() is in the cposix library, which doesn't happen for many platforms - a special case so it can add -lcposix to the library list if needed). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: NetBSD build problems - -lcposix?
On Tue, Mar 12, 2002 at 03:10:27PM -0800, Ken Weingold wrote: On Tue, Mar 12, 2002, Thomas Dickey wrote: Oh, so then maybe it's not related to why make crapped out. Here's the error: pgpkey.o: In function `pgp_ask_for_key': /tmp/hazmat/mutt-1.3.27/pgpkey.c:701: undefined reference to `beep' beep() is a function in the curses (or ncurses) library. Huh. Would that cause make to error out? I now get this. I think the difference was using 'gcc3'. I get undefined reference all over the place, btw. yes - I don't see the whole log of course, but the warnings you're seeing are due to the link either missing the curses library altogether or having the wrong library. The NetBSD curses library for instance is an incomplete subset of X/Open curses (especially compared to ncurses ;-) Perhaps the configure script didn't find ncurses (which is a port), or was fooled into trying to use the NetBSD curses library (not recommended). /tmp/hazmat/mutt-1.3.27/pgpkey.c:701: undefined reference to `beep' resize.o: In function `mutt_resize_screen': /tmp/hazmat/mutt-1.3.27/resize.c:79: undefined reference to `resizeterm' collect2: ld returned 1 exit status gmake[2]: *** [mutt] Error 1 gmake[2]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake: *** [all-recursive-am] Error 2 -Ken -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt configuration tool
On Sun, Mar 10, 2002 at 12:24:27PM +0100, Thomas Baker wrote: At any rate, I am not aware of win32 binaries -- either in Cygwin or native-win32 -- for other important mutt-related utilities such as procmail or urlview. urlview should be simple to port. procmail probably has more directory filename issues. contrast to pine which I've read does have a native win32 port... Baochun Li has done a Cygwin port of Pine, see http://www.eecg.toronto.edu/~bli/personal.html, but in my experience it only runs in an xterm window, requiring XFree86 or Exceed. However, I am not aware of a native win32 port other than PC-PINE, which is really not quite the same program and uses a proprietary mailbox file format. that's surprising (I would assume that pine, which uses termcap, would run properly in a cygwin window or rxvt). Maybe not - I do know that there are problems with cygwin switching between raw/cooked I/O modes that show up when I spawn a subprocess from an ncurses application. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Pager problems in 1.3.27
On Wed, Mar 06, 2002 at 03:01:39PM +0100, Raymond A. Meijer wrote: On Wed, 06 Mar 2002, 08:58, Thomas E. Dickey wrote: thanks (will look at this when I'm done with work - on my home machine I can analyze it properly) Cool! Thanks for trying to help me out! I'm looking - but still don't see the immediate problem. Your typescript file doesn't show any sign of black-on-black masking the characters - they simply aren't shown. Running it slowly, I don't see any extra cursor movement either - it just doesn't show anything in the pager. From other comments (and my own checks), it's not related to ncurses. So it looks like a problem with mutt (or something obscure with your Linux configuration, such as a broken iconv). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Deleting text in subject flea
On Mon, Mar 04, 2002 at 10:08:39PM -0500, MuttER wrote: * David DeSimone [EMAIL PROTECTED] [03-04-02 15:55] crowed: Simon White [EMAIL PROTECTED] wrote: This seems to happen specifically when I have input more than 8 characters, which is usual for filenames with full paths and email addresses. I wonder if you could try running stty -tabs before you start Mutt. That takes care of delete and backspace but not 'home' and 'end' keys?? that's what terminfo is for. ftp://invisible-island.net/ncurses/terminfo.src.gz -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt paints over background image
On Wed, Feb 27, 2002 at 03:11:21PM +0100, Dominik Vogt wrote:
On Wed, Feb 27, 2002 at 08:37:22AM -0500, Thomas E. Dickey wrote:
On Wed, 27 Feb 2002, Dominik Vogt wrote:
I have been using mutt in an rxvt window with a background xpm
for a long time, using the version from the SuSE distribution
withouth compilling myself. Since SuSE 7.2 however, rxvt covers
the background image with a black character background itself. I
guess this has something to do with slang vs. ncurses. The older
versions were using ncurses and the new ones are compiles with
slang.
Is there any way to get back my background image without having to
compile mutt myself?
it's most likely the choice of $TERM (the terminfo entry should have
'op' using \E[39m;\E[49m, for instance).
Ahem, could you explain that again for complete idiots? I don't
have the terminfo sources installed, so I can't check the settings
in the rxvt terminfo file (unless someone tells me how to do it).
the color terminfo for rxvt should look like this (I used infocmp to dump
it, could use tic on the same text to install it):
# Reconstructed via infocmp from file: /usr/lib/terminfo/r/rxvt
rxvt|rxvt terminal emulator (X Window System),
am, bce, eo, km, mir, msgr, xenl, xon,
colors#8, cols#80, it#8, lines#24, pairs#64,
acsc=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM, dl1=\E[M, ed=\E[J,
el=\E[K, el1=\E[1K, enacs=\E(B\E)0, flash=\E[?5h\E[?5l,
home=\E[H, ht=^I, hts=\EH, ich=\E[%p1%d@, ich1=\E[@,
il=\E[%p1%dL, il1=\E[L, ind=^J, is1=\E[?47l\E=\E[?1l,
is2=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l,
kDC=\E[3$, kEND=\E[8$, kHOM=\E[7$, kLFT=\E[d, kNXT=\E[6$,
kPRV=\E[5$, kRIT=\E[c, ka1=\EOw, ka3=\EOy, kb2=\EOu, kbs=^H,
kc1=\EOq, kc3=\EOs, kcbt=\E[Z, kcub1=\E[D, kcud1=\E[B,
kcuf1=\E[C, kcuu1=\E[A, kdch1=\E[3~, kel=\E[8\^,
kend=\E[8~, kent=\EOM, kf1=\E[11~, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf13=\E[25~, kf14=\E[26~,
kf15=\E[28~, kf16=\E[29~, kf17=\E[31~, kf18=\E[32~,
kf19=\E[33~, kf2=\E[12~, kf20=\E[34~, kf3=\E[13~,
kf4=\E[14~, kf5=\E[15~, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~,
kf9=\E[20~, kfnd=\E[1~, khome=\E[7~, kich1=\E[2~,
kmous=\E[M, knp=\E[6~, kpp=\E[5~, kslt=\E[4~, op=\E[39;49m,
rc=\E8, rev=\E[7m, ri=\EM, rmacs=^O, rmcup=\E[2J\E[?47l\E8,
rmir=\E[4l, rmkx=\E, rmso=\E[27m, rmul=\E[24m,
rs1=\E\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H,
rs2=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l\E,
s0ds=\E(B, s1ds=\E(0, sc=\E7, setab=\E[4%p1%dm,
setaf=\E[3%p1%dm, sgr0=\E[m\017, smacs=^N,
smcup=\E7\E[?47h, smir=\E[4h, smkx=\E=, smso=\E[7m,
smul=\E[4m, tbc=\E[3g,
Bye
Dominik ^_^ ^_^
P.S.: Please cc me, I'm not subscribed to the list.
--
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: colours in SecureCRT
On Wed, Feb 20, 2002 at 11:22:21AM -0500, Sridhar Srinivasan wrote:
hi,
i use SecureCRT to connect to my mailserver (a Solaris 8 box) whenever
i'm in windows. i'm unable to get it display my colour settings
properly even though i have tried changing the terminal type to linux,
ansi, etc. with some combinations of $TERM, i do get some zany colours
but not my normal scheme.
( perhaps xterm-color ;-)
If it's the same product family, I did this terminfo for CRT a few years
ago (in ncurses):
# Reconstructed via infocmp from file: /usr/lib/terminfo/c/crt
crt|crt-vt220|CRT 2.3 emulating VT220,
am, bce, mir, msgr, xenl, xon,
colors#8, cols#80, lines#24, pairs#64, vt#3,
acsc=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m$2, bold=\E[1m$2, civis=\E[?25l,
clear=\E[H\E[2J$50, cnorm=\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub1=^H, cud1=\E[B, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH$10, cuu1=\E[A, dch1=\E[P,
dl1=\E[M, ed=\E[J$50, el=\E[K$3, home=\E[H, ht=^I,
hts=\EH, if=/usr/share/tabset/vt100, il1=\E[L,
ind=\ED$20/, is2=\E[1;24r\E[24;1H, kbs=^H, kcub1=\E[D,
kcud1=\E[B, kcuf1=\E[C, kcuu1=\E[A, kdch1=\E[3~,
kend=\E[4~, kf1=\EOP, kf10=\E[29~, kf2=\EOQ, kf3=\EOR,
kf4=\EOS, kf5=\E[17~, kf6=\E[18~, kf7=\E[19~, kf8=\E[20~,
kf9=\E[21~, khome=\E[1~, kich1=\E[2~, knp=\E[6~, kpp=\E[5~,
op=\E[39;49m, rc=\E8, rev=\E[7m$2,
rf=/usr/share/tabset/vt100, ri=\EM$14/,
rmacs=\E(B$4, rmam=\E[?7l, rmir=\E[4l, rmso=\E[27m,
rmul=\E[24m, rs2=\E\E[?3l\E[?4l\E[?5l\E[?7h\E[?8h,
sc=\E7, setab=\E[4%p1%dm, setaf=\E[3%p1%dm,
setb=\E[4%p1%dm, setf=\E[3%p1%dm,
sgr=\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p4%t;5%;%?%p1%p3%|%t;7%;m%?%p9%t\E(0%e\E(B%;,
sgr0=\E[m$2, smacs=\E(0$2, smam=\E[?7h, smir=\E[4h,
smso=\E[7m, smul=\E[4m, u6=\E[%i%d;%dR, u7=\E[6n,
u8=\E[?1;2c, u9=\E[c,
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: ncurses or slang
On Tue, Feb 19, 2002 at 04:27:21PM +0100, Manuel Hendel wrote: Actually I allways used ncurses with mutt. Some days ago, I upgraded to mutt 1.3.27 and compiled it with slang because this is default! I default on which system (I understand some ports such as FreeBSD do this). wanted to use my old muttrc but there seems to be some problems with the colors. Where's the difference? What's going wrong here? perhaps it's a problem with the port... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: ncurses or slang
On Tue, Feb 19, 2002 at 07:31:13PM +0100, Martin Karlsson wrote: On Tue Feb 19, 2002 at 04:27:21PM +0100, Manuel Hendel wrote: [...snip...] wanted to use my old muttrc but there seems to be some problems with the colors. Where's the difference? What's going wrong here? When I moved from ncurses to slang, I had to change color header green default ^date: ^^^ to color header green black ^date: It seems slang won't accept 'default' as a color (for me anyway ;) both ncurses and slang do. but there may be a problem with the port. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: ncurses or slang
On Tue, Feb 19, 2002 at 10:36:37PM +0100, Manuel Hendel wrote: Where's the advantage in using slang instead of ncurses? this question is asked about once a week... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: ncurses or slang
On Wed, Feb 20, 2002 at 12:02:14AM +0200, Artem Okounev wrote: On Tue, Feb 19, 2002 at 04:44:22PM -0500, Thomas Dickey wrote: On Tue, Feb 19, 2002 at 10:36:37PM +0100, Manuel Hendel wrote: Where's the advantage in using slang instead of ncurses? this question is asked about once a week... Probably in mutt-devel, but not here. Explain please. or perhaps my sense of time is warped. The mutt configuration with ncurses or slang provides roughly equal capabilities (there are different bugs in each, btw, though people who want to use slang tend to gloss over that aspect). I use ncurses, of course, and am familiar with many of the ways ports/distributions add bugs to it. FreeBSD adds another layer of bugs (over what's in mutt) because the ports don't integrate properly. There are pros/cons on Linux regarding UTF-8 support, but my impression is that FreeBSD is not viable for that anyway, so it's a moot point. The main impact on ncurses is that occasionally I see reports of library conflicts between the native copy of ncurses and a ported version. That shouldn't be a problem post-4.0 FreeBSd, but you might be surprised - anyway the BSD loader uses some sort of weak binding that is easily confused by libraries containing similar symbols. Since there's only one version of slang (ports tend to do that), there's no conflicts. Another is the frequent misadvice to use the xterm-color termcap entry - which kills the use of default colors (unless of course one has the compensating bug of slang apps that check $COLORTERM to decide when to ignore the termcap ;-) However - as reported by someone recently, since slang is looking first at termcap, that has an adverse effect on line-drawing characters (unless propped up by yet another kludge to ignore the termcap, since the xterm-color termcap is too small to provide that capability). ncurses uses terminfo - not a problem there (though FreeBSD does wedge that termcap stuff in there, providing additional problems for the unwary). Summary - there's no real advantage, but some of the troubleshooting of setting the configuration up for a novice is alleviated by slang's workarounds. But the result is only superfically ok - some loss of functionality results. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt flea
On Fri, Feb 15, 2002 at 03:10:35PM +, Simon White wrote: You probably all use save-hooks and all that, but on my setup: I hit s, then backspace to get rid of the default, and as I hit backspace the string gets 'corrupted', i.e. what I see on screen is a mix of what I typed and what I had before. If I hit backspace loads of times to be sure the buffer is clear I still have a few letters left behind but the path I put in works. Is this a curses issue, or is it Mutt? probably curses is doing what mutt told it to do... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: [OT] Re: your mail
On Mon, Jan 28, 2002 at 09:40:43AM +0100, Martin Karlsson wrote:
On Sun Jan 27, 2002 at 02:08:08PM -0800, Dale Morris wrote:
Oh, if I'm in X using xterm, there's no color in mutt but I can
backspace to delete text. If I'm in rxvt I have color in mutt but can't
backspace/delete.
Hi. If you're using xfree86/x-term, put the following in your
~/.Xdefaults (_instead_ of mucking around with $TERM):
xterm*termName: xterm-color
That should fix you no-colour while in x-term-problem.
...while adding other problems:
comparing xterm-color to xterm-xfree86.
comparing booleans.
OTbs: T:F.
bce: F:T.
mc5i: F:T.
npc: F:T.
comparing numbers.
comparing strings.
blink: NULL, '\E[5m'.
cbt: NULL, '\E[Z'.
civis: NULL, '\E[?25l'.
cnorm: NULL, '\E[?25h'.
ech: NULL, '\E[%p1%dX'.
el1: NULL, '\E[1K'.
enacs: '\E)0', '\E(B\E)0'.
flash: NULL, '\E[?5h$100/\E[?5l'.
hpa: NULL, '\E[%i%p1%dG'.
ich: NULL, '\E[%p1%d@'.
invis: NULL, '\E[8m'.
is2: '\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E', '\E[!p\E[?3;4l\E[4l\E'.
kDC: NULL, '\E[3;2~'.
kEND: NULL, '\EO2F'.
kHOM: NULL, '\EO2H'.
kIC: NULL, '\E[2;2~'.
kLFT: NULL, '\EO2D'.
kNXT: NULL, '\E[6;2~'.
kPRV: NULL, '\E[5;2~'.
kRIT: NULL, '\EO2C'.
kb2: NULL, '\EOE'.
kcbt: NULL, '\E[Z'.
kend: NULL, '\EOF'.
kent: NULL, '\EOM'.
kf1: '\E[11~', '\EOP'.
kf13: '\E[25~', '\EO2P'.
kf14: '\E[26~', '\EO2Q'.
kf15: '\E[28~', '\EO2R'.
kf16: '\E[29~', '\EO2S'.
kf17: '\E[31~', '\E[15;2~'.
kf18: '\E[32~', '\E[17;2~'.
kf19: '\E[33~', '\E[18;2~'.
kf2: '\E[12~', '\EOQ'.
kf20: '\E[34~', '\E[19;2~'.
kf21: NULL, '\E[20;2~'.
kf22: NULL, '\E[21;2~'.
kf23: NULL, '\E[23;2~'.
kf24: NULL, '\E[24;2~'.
kf25: NULL, '\EO5P'.
kf26: NULL, '\EO5Q'.
kf27: NULL, '\EO5R'.
kf28: NULL, '\EO5S'.
kf29: NULL, '\E[15;5~'.
kf3: '\E[13~', '\EOR'.
kf30: NULL, '\E[17;5~'.
kf31: NULL, '\E[18;5~'.
kf32: NULL, '\E[19;5~'.
kf33: NULL, '\E[20;5~'.
kf34: NULL, '\E[21;5~'.
kf35: NULL, '\E[23;5~'.
kf36: NULL, '\E[24;5~'.
kf37: NULL, '\EO6P'.
kf38: NULL, '\EO6Q'.
kf39: NULL, '\EO6R'.
kf4: '\E[14~', '\EOS'.
kf40: NULL, '\EO6S'.
kf41: NULL, '\E[15;6~'.
kf42: NULL, '\E[17;6~'.
kf43: NULL, '\E[18;6~'.
kf44: NULL, '\E[19;6~'.
kf45: NULL, '\E[20;6~'.
kf46: NULL, '\E[21;6~'.
kf47: NULL, '\E[23;6~'.
kf48: NULL, '\E[24;6~'.
kfnd: '\E[1~', NULL.
khome: NULL, '\EOH'.
kslt: '\E[4~', NULL.
mc0: NULL, '\E[i'.
mc4: NULL, '\E[4i'.
mc5: NULL, '\E[5i'.
op: '\E[m', '\E[39;49m'.
rmam: NULL, '\E[?7l'.
rmcup: '\E[2J\E[?47l\E8', '\E[?1049l'.
rmso: '\E[m', '\E[27m'.
rmul: '\E[m', '\E[24m'.
rs1: NULL, '\Ec'.
rs2: '\E7\E[r\E8\E[m\E[?7h\E[?1;3;4;6l\E[4l\E', '\E[!p\E[?3;4l\E[4l\E'.
setb: NULL,
'\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m'.
setf: NULL,
'\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m'.
sgr: NULL,
'\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\016%e\017%;'.
sgr0: '\E[m', '\E[m\017'.
smam: NULL, '\E[?7h'.
smcup: '\E7\E[?47h', '\E[?1049h'.
vpa: NULL, '\E[%i%p1%dd'.
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: your mail
On Sun, Jan 27, 2002 at 02:08:08PM -0800, Dale Morris wrote: I've just recently installed FreeBSD. I've got most all of my mail functioning properly, but I'm having a problem with mutt. When I am in a console, the bottom messages don't appear. For example I enter q and at the bottom of the screen is a black spaced indent and then the cursor. No text. If I type y mutt quits. It sounds as if your choice of $TERM is resetting colors to black-on-black. I'm using mutt 1.25 and Roland Rosenfeld's .muttrc and setup files icewm-gnome .xinitrc .tcsh Oh, if I'm in X using xterm, there's no color in mutt but I can backspace to delete text. If I'm in rxvt I have color in mutt but can't backspace/delete. same problem (the terminfo entry tells the application what to expect for backspace - kbs - and delete - kdch1). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: your mail
On Sun, Jan 27, 2002 at 02:24:22PM -0800, Will Yardley wrote: i usually use xterm-color in FreeBSD even though you really shouldn't ever use 'xterm-color' since color 'ls' only works (AFAIK) when $TERM is set to this. on linux, i use xterm-xfree86, or sometimes just xterm. xterm-color is always incorrect for xterm and rxvt... (it happens to work if you don't care much about how well). see http://dickey.his.com/xterm/xterm.faq.html#xterm_terminfo color 'ls' ignores the termcap and terminfo databases, btw. experiment with different TERM settings and terminal programs and see what works for you. personally i find Eterm nicer looking (after you mess with the default colors and stuff) than xterm or rxvt, although it can be a bit of a memory hog. Both (XFree86) xterm and rxvt implement default colors, have done so since long before Eterm was written. (There's no difference, except of course if you're setting $TERM to xterm-color for one of the latter). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: your mail
On Sun, Jan 27, 2002 at 02:50:16PM -0800, Will Yardley wrote: Thomas Dickey wrote: On Sun, Jan 27, 2002 at 02:24:22PM -0800, Will Yardley wrote: i usually use xterm-color in FreeBSD even though you really shouldn't ever use 'xterm-color' since color 'ls' only works (AFAIK) when $TERM is set to this. on linux, i use xterm-xfree86, or sometimes just xterm. It's trivial to fix this (FreeBSD's termcap is badly-undermaintained). All you need to do is take the termcap that's part of the xterm distribution, paste it at the front of your /usr/share/misc/termcap, and regenerated the termcap database. Any competant sys-admin can do this. xterm-color is always incorrect for xterm and rxvt... (it happens to work if you don't care much about how well). color 'ls' ignores the termcap and terminfo databases, btw. I had in mind (having forgotten that FreeBSD has a not-invented-here mentality) that they'd implemented a copy of the GNU 'ls', and didn't consider that they may have fixed one problem while introducing another... CLICOLOR Use ANSI color sequences to distinguish file types. See LSCOLORS below. In addition to the file types mentioned in the -F option some extra attributes (setuid bit set, etc.) are also displayed. The colorization is dependent on a terminal type with the proper termcap(5) capabilities. The default ``cons25'' console has the proper capabilities, but to display the colors in an xterm(1), for example, the TERM variable must be set to ``xterm-color''. Other it's still wrong even if it's in the manpage (I think I'm more familiar with this stuff than the ostensible author of this manpage). i use Eterm, but haven't had any problems with xterm-color. i know that it's incorrect, but it works for me ok. you won't get default colors (by anything that relies on the termcap settings). hardcoded programs, of course, are not affected. if anyone knows a better workaround, let me know. I haven't been counting, but I'm certain I've mentioned it at least once a week for the past year. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: html email
On Fri, Jan 25, 2002 at 09:52:26PM -0800, David Ellement wrote: The best ones are from the IT department, rejoicing in their latest efficiency measures... worse - the ones that have the message in plain text, along with a 500kb attachment in M$ Word repeating word-for-word the same information. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: html email
On Sat, Jan 26, 2002 at 09:17:14AM -0800, Michael Maibaum wrote: My favorite was the last bi-monthly report from our (win NT dominated...) IT dept...It was a 4Mb word document for about a page and I'm not able to top that. (There are some instances where individuals have sent larger attachments - some because they don't think to compress a file, and others who make a habit of attaching the relevant files - more than once - even though I already have the files). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: different color problems
On Thu, Jan 17, 2002 at 12:04:50PM -0800, Carl B. Constantine wrote: I solved my color problems with mutt-1.3.25. I did specify the curses param incorrectly. It's fixed and I'm happily using the new mutt. However, I have a different color issue to ask about. Under my new compile of mutt with ncurses 5.2, I see yellow color as yellow (dtterm). However, under my Linux system (gnome terminal) yellow looks more orange/brown in color. Well, gnome-terminal does combine bold with colors (I looked at the 'gnome' terminfo entry and retested gnome terminal in case I'd missed this detail). Perhaps you're specifying a $TERM that says it does not. In that case (based on the 'ncv' value in terminfo), ncurses would rather set colors than bold or other conflicting attribute. When I ssh from my solaris 8 box to my home machine, color works correctly (including yellow). However, when I ssh from my home machine to my work-solaris 8 machine, mutt is in mono color though editing (using vim) does show up in color, just not mutt's indexes and such. Does ssh pass through your $TERM settings? (It depends on the configuration, does sometimes, and sometimes not, so it would default to something like vt100, leaving vim to rely on its builtin tables). Anyone seen that before? I'm using Debian at home and I installed packages for ncurses and mutt as opposed to compiling them myself. ideas? -- Carl B. Constantine University of Victoria Programmer Analysthttp://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED] -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: different color problems
On Thu, Jan 17, 2002 at 03:48:09PM -0800, Will Yardley wrote: Cameron Simpson wrote: Colours are really just specified as slot numbers (1-8 standard, another 8 in some more recent terminal emulators). So the actual hue you get for a colour slot is a quality of implementation issue. My Linux console shows my yellow prompt as an orange/brown too :-( Rxvt and xterm show yellow. well in terminal emulators like rxvt and xterm, you can change the colors from default in your .Xdefaults; i'd assume you might be able to do this for dterm as well. no, dtterm does not implement the same color model -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: problem with 1.3.25
On Wed, Jan 16, 2002 at 04:12:40PM -0800, Carl B . Constantine wrote: I'm using mutt 1.2.5 on Solaris 8 Intel. It works fine. I'm using ncurses 5.2 with it. I see color and everything. However, I today compiled mutt 1.3.25 and made sure I compiled it with ncurses support. However, upon launch I get a bunch of errors that the color 'default' is not defined: probably the configure script is (as noted in the previous report) not adding -lncurses to $LIBS and is finding the Solaris curses library instead. (Another clue is that resizeterm isn't found). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: problem with 1.3.25
On Wed, Jan 16, 2002 at 04:25:54PM -0800, Will Yardley wrote: i'm using the sunfreeware ncurses: ...which is perhaps a problem in itself (I've several reports that this package is installed with conflicting names versus the Solaris curses library). imho, that package should be deleted. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: $display_filter and allow_ansi
On Tue, Jan 15, 2002 at 10:42:02AM +, John Levon wrote: So I set up $display_filter and allow_ansi to view syntax-highlighted messages through mutt's pager, and it works, but my ANSI color settings are setting the background to black for the coloured lines, instead of the terminal default. I've heard tell the same problem can happen with mutt internal color command. Any ideas on what the problem is and how to fix it ? I am using xterm-color on a BSD box ssh'd from Linux. The $display_filter is attached. TERM=xterm-color will always do this (except for some hardcoded crap I've seen), since it's telling the screen library that the terminal cannot do default colors. I've searched archives etc. to no avail it's an faq... The XFree86 xterm supports ANSI color and VT220 emulation There's an faq at http://dickey.his.com/xterm/xterm.faq.html ftp://dickey.his.com/xterm The current version of ncurses is 5.2 (20001021) There's an faq at http://dickey.his.com/ncurses/ncurses.faq.html -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: 1.3.25 builds with S-LANG - PuTTy colors now munged
On Sun, Jan 06, 2002 at 04:18:19PM -0500, Jack Baty wrote: Now, before I go around messing with trying to go back to using ncurses, I'd like to know if anyone knows if there's a way to fix the color issue while still using slang, since that seems to now be recommended. I know nothing not recommended. slang users just tend to be a lot louder (and there are more slang users than developers...) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Good vim configuration?
BTW, regarding those other suggestions involving binding fmt or par to a key, isn't it slow to fork a process every time you press the rejustify key, or is that overhead negligible? it really depends on how often you do it (I don't do this one, but have equivalent cases in mind). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Good vim configuration?
On Tue, Dec 25, 2001 at 12:14:19PM +, Thomas Hurst wrote: * Philip Mak ([EMAIL PROTECTED]) wrote: How can I achieve the same thing in vi? I'd like to be able to bind a key such that when I press it, it automatically refills the current paragraph smartly. Some automatic line wrapping would be nice, too... I'm wondering what configurations for .vimrc do you guys use for use with mutt? I use par(1), http://www.cs.berkeley.edu/~amc/Par/ It (flowing with mail-quotes) is a builtin in vim and vile. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Wy30 terminal
On Sun, Dec 09, 2001 at 12:37:12PM -0600, Skylar Thompson wrote:
I have a Wy30+ serial terminal that is currently sitting in my living room.
It is currently connected to my workstation in my room, which in turn is
connected to my mail server in my basement via Cat-5. I would like to be
able to use mutt using the serial terminal, so I don't have to get up to read
me mail. ;)
The problem is that mutt does not display correctly on the terminal. I can
get the header and footer of the main screen to display, but not all the
messages are displayed, and some of them are wrapped over onto the next line,
which throws everything underneath it off.
I use ssh to connect to the mail server, and I am using the wy30 entry
/etc/termcap for terminal emulation. I have attached the output of stty -a
to this message.
mutt probably isn't using /etc/termcap, but terminfo instead. This is
what I would guess for wy30:
# Reconstructed via infocmp from file: /usr/lib/terminfo/w/wy30
wy30|wyse30|Wyse 30,
am, bw, hs, mc5i, mir, msgr, xon,
cols#80, lh#1, lines#24, lw#8, ma#1, nlab#8, wsl#45,
acsc=0wa_h[jukslrmqnxqzttuyv]wpxv, bel=^G, cbt=\EI,
civis=\E`0, clear=\E+$80, cnorm=\E`1, cr=^M, cub1=^H,
cud1=^J, cuf1=^L, cup=\E=%p1%' '%+%c%p2%' '%+%c, cuu1=^K,
dch1=\EW$10, dim=\E`7\E), dl1=\ER$1, dsl=\EF\r,
ed=\EY$80, el=\ET, flash=\E`8$100/\E`9, fsl=^M,
home=^^, ht=\011$1, hts=\E1, il1=\EE$2, ind=\n$2,
ip=$2, is2=\E'\E(\E\^3\E`9\016\024, kHOM=\E{, kbs=^H,
kcbt=\EI, kcub1=^H, kcud1=^J, kcuf1=^L, kcuu1=^K, kdch1=\EW,
kdl1=\ER, ked=\EY, kel=\ET, kent=\E7, kf1=^A@\r, kf2=^AA\r,
kf3=^AB\r, kf4=^AC\r, kf5=^AD\r, kf6=^AE\r, kf7=^AF\r,
kf8=^AG\r, khome=^^, kich1=\EQ, kil1=\EE, knp=\EK, kpp=\EJ,
krpl=\Er, ll=^^^K, mc0=\EP, mc4=^T, mc5=^X, nel=^M^J,
pfx=\Ez%p1%'?'%+%c%p2%s\177,
pln=\Ez%p1%'/'%+%c%p2%s\r, prot=\E`7\E), ri=\Ej$3,
rmacs=\EH^C, rmir=\Er, rmln=\EA11, rmso=\E(,
sgr=%?%p1%p5%p8%|%|%t\E`7\E)%e\E(%;%?%p9%t\EH\002%e\EH\003%;,
sgr0=\E(\EH\003, smacs=\EH^B, smir=\Eq, smln=\EA10,
smso=\E`7\E), tbc=\E0, tsl=\EF,
It's possible that one or more of the strings are corrupt - I corrected
several of the entries for Wyse terminals from having seen that some
typos were introduced by back/forth translation with infocmp (e.g.,
adding commas or other punctuation). I'd suggest debugging the terminal
entry using 'tack', which exercises a large portion of the terminfo
entry in individual tests. (tack is part of ncurses).
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: Wy30 terminal
On Sun, Dec 09, 2001 at 01:54:35PM -0500, David T-G wrote: One thing you might do is to tell your editor to wrap your lines at 72 characters or so... that's what editors are for (mutt-users seems to have a lot of vim-users, though of course I use vile - either way it's just a keystroke to reflow). ...and then Skylar Thompson said... % % I have a Wy30+ serial terminal that is currently sitting in my living room. .. Have you tried running mutt with TERM=vt100? That's pretty basic and simple, and should be a good start. vt100 is nothing like wyse30 (unless of course the wyse30 terminal has a vt100 emulation that he can use - then it might be something like ;-) -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Wy30 terminal
On Sun, Dec 09, 2001 at 02:17:02PM -0500, David T-G wrote: Thomas, et al -- ...and then Thomas Dickey said... % On Sun, Dec 09, 2001 at 01:54:35PM -0500, David T-G wrote: % One thing you might do is to tell your editor to wrap your lines at 72 % characters or so... % that's what editors are for (mutt-users seems to have a lot of vim-users, % though of course I use vile - either way it's just a keystroke to reflow). Ick. I don't like reflowing someone else's text. I don't like someone else reflowing mine, either. I do it often enough that I don't have to look at the key I've bound that to (F7). % % I have a Wy30+ serial terminal that is currently sitting in my living room. % Have you tried running mutt with TERM=vt100? That's pretty basic and % simple, and should be a good start. % vt100 is nothing like wyse30 (unless of course the wyse30 terminal % has a vt100 emulation that he can use - then it might be something like ;-) I figured the latter as fairly likely, but I also figured that vt100 was about as basic as one could get. Shows you what I know :-) it's possible (about 1/4 of the time I point out that terminal xxx isn't vt100-compatible, someone says it has a vt100 emulation - though it isn't clear before/after if the requestor was using that. Lovely Greek goo you posted a bit ago; I found it very interesting (well, no, not really, but perhaps Skylar will find it helpful ;-) enough that he can look/compare/inquire further... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt via rxvt/gnome-terminal -- push ignored sometimes
On Thu, Dec 06, 2001 at 06:47:38PM -0800, Ben Compton wrote: Hey all, I've encountered a weird problem -- I'm setting up xbuffy to launch new terminals, and those terminals to open up mutt pointing at a specific mailbox sometimes, though, when you pass the mutt command off to the terminal (in my case I tried using rxvt and gnome-terminal) sometimes the -e command is ignored in weird ways. I've seen a recent bug report for gnome-terminal indicating that it mistreats -e. (gnome-terminal probably should be deleted to save diskspace). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: binding and slow reaction
On Tue, Dec 04, 2001 at 09:48:35PM -0500, Brian Clark wrote: Can anyone tell me why this: bind pager \e exit Causes there to be a full 1 second delay, after hitting Esc, before it actually quits the pager? man ncurses ESCDELAY Specifies the total time, in milliseconds, for which ncurses will await a character sequence, e.g., a function key. The default value, 1000 milliseconds, is enough for most uses. However, it is made a vari- able to accommodate unusual applications. (it's hardcoded in slang, btw) -- -Brian Clark % egrep -i pager= ~/.muttrc set pager=builtin % mutt -v Mutt 1.3.23i (2001-10-09) Copyright (C) 1996-2001 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: Linux 2.2.19 [using ncurses 5.2] -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: color problems after upgrade
I tried you colors, and those object where default is specified as the background, the aterm background shows thru - everything else - the message body, and the main index background is still white on black. perhaps your $TERM is xterm-color (except for hardcoded applications that ignore $TERM, you won't see default colors working properly in that case). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: License of patches
On Sun, Dec 02, 2001 at 12:19:39PM +0100, Nicolas Rachinsky wrote: Hello, is it safe to assume, that all the mutt patches floating around are gpl'd, because they are derived from gpl'd software (mutt)? not necessarily - add-on macros and other code which does not include diff's from mutt's source would not be affected (it's really up to the author of those items). -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Trailing Lines
On Fri, Nov 30, 2001 at 09:20:06AM +0530, Prahlad Vaidyanathan wrote: In Vim, in vi :g/^$/d -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
