Re: About emacs, about quoting text, about writing message.
On 2001-07-17 18:14:01 +0200, Jens Paulus wrote: 3.) Suppose I'm in the index and my position indication arrow is marking an email from somebody I want to write an email to. I don't want to hit 'r' because I don't want to _reply_ to this email. One solution would be: Why not reply to that person? Don't you want the r mark on the index, or do you just want to start a new thread? In the latter case, you can set the edit_hdrs variable and remove the In-Reply-To header when editing. This will have the effect of removing References, too. -- Thomas Roesslerhttp://log.does-not-exist.org/
From: is blank
Mutt users, On my computer at work (mutt 1.2.5, solaris), whenever I send a message, mutt fills in the From header with my name and my email address. I don't think I ever did anything to configure this, but I like it. On my home computer (mutt 1.3.x, debian), whenever I send a message, the ``From'' header is empty. When I send the message the From field is eventually filled in by something, perhaps the local MTA. However, this missing From header can confuse mutt in a number of ways such as when I reply to my own messages. What can I do to coax mutt to fill out this information? It seems like it should be automatic. Is there likely a problem outside of mutt? Thanks for the help, James
Re: From: is blank
Mutt users, Problem fixed. I found the system muttrc (I looked for /etc/mutt* and couldn't find it at first.) and I see that Debian disables filling in the header. I wonder why they did that? Oh well, I've solved the problem now. Even though you all didn't get to help me, I can feel that you would have if I had given you the chance. Thanks. James Gale
Re: Newbie question
On Wed, 18 Jul 2001, Fox Mulder wrote: thanks for the file. i tried it, but still no help. I still dont get the N in the folder view, and dont get the Inc field in the status bar. also, i am still getting that problem with the arrows in threads. There are problems with mutt recognizing new mail on the mbox format. I suggest considering moving your mailboxes to the 'maildir' format. It's easy and mutt works well with it. Also procmail supports it. -- Micha. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
Re[2]: mail sorting #2
On Wed, Jul 18, 2001 at 07:43:16AM +0200, Christoph Maurer wrote: Am Die, 17 Jul 2001, schrieb Lukasz Zamel: Procmail is really cool. I've downloaded a faq and it's not fo hard to configure. But still I have a small problem. I'm getting 'Error writing to ...' even if I set a+rw to those mailboxes. Did you set your MAILDIR Variable korrekt (normally $HOME/Mail) in your procmailrc. Thanks, that was the problem! I simply didn't set MAILDIR correctly. -- Lukasz Zamel [EMAIL PROTECTED] Reg. Linux User: #202048 PGP: http://republika.pl/lzamel/pubkey.asc 640K ought to be enough for enybody - Bill Gates, 1981 PGP signature
Keywords? Filter-on-condition-when-sending?
Two questions: == 1. Is there anyway of configuring WHAT headerfields that are asked for before entering edit-mode? Default seems to be 'To:' and 'Subject:'. I'd like to set 'Keywords:' as well. 2. How do I hook in a program to filter with on send? OK. The easiest way may be to set sendmail to a wrapperscript that does everything and then piping, but is there any other way? E.g. when you mail to a certain mailadress? /magnus -- : Magnus Bodin . http://x42.com/ .. etaosinrl=dhwygm'f.pb?c:k-1/2qvj,
Re: Keywords? Filter-on-condition-when-sending?
Am Mit, 18 Jul 2001, schrieb Magnus Bodin: Is there anyway of configuring WHAT headerfields that are asked for before entering edit-mode? Default seems to be 'To:' and 'Subject:'. I'd like to set 'Keywords:' as well. You can configure mutt to also ask for Cc: and Bcc: by setting askcc or askbcc respectively. But I think any other Headers can only be set either with hooks or by setting the edit_headers variable and editing them in your editor. Christoph -- Christoph Maurer - Paul-Röntgen-Straße 7 - D - 52072 Aachen mailto:[EMAIL PROTECTED] - http://www.christophmaurer.de On my Homepage: SuSE 7.0 on an Acer Travelmate 508 T Notebook
Re: About emacs, about quoting text, about writing message.
Quoting Jens Paulus [EMAIL PROTECTED], who wrote: 3.) Suppose I'm in the index and my position indication arrow is marking an email from somebody I want to write an email to. I don't want to hit 'r' because I don't want to _reply_ to this email. One solution would be: What I do is have edit_headers set in my muttrc. Then I do a reply, but when I get popped into vim, I delete the references line (that makes it not a reply) and change the subject to whatever I want. Sam -- Sam Roberts [EMAIL PROTECTED]
Re: Problems with vvv port on FreeBSD
On 2001.07.17, in [EMAIL PROTECTED], Suresh Ramasubramanian [EMAIL PROTECTED] wrote: Louis LeBlanc [mutt-users] 17/07/01 23:51 -0400: Hey all. I am trying to get the vvv port for FreeBSD built, but it keeps dying on some wchar code. Any ideas what the hangup is there? I personally had no problems. However, there is a note which says vvv can't coexist with Roland's compressed folders patch in that port. Did you enable both? I'm not sure what that note's about, and I'm only assuming that vvv is the nntp patch (vs the other patches on his site), but I'm using VVV's nntp with the compressed folders patch. I don't think I understand the meaning of a *BSD port at all. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Problems with vvv port on FreeBSD
David Champion [18/07/01 09:04 -0500]: Suresh Ramasubramanian [EMAIL PROTECTED] wrote: I personally had no problems. However, there is a note which says vvv can't coexist with Roland's compressed folders patch in that port. Did you enable both? I'm not sure what that note's about, and I'm only assuming that vvv is the nntp patch (vs the other patches on his site), but I'm using VVV's nntp with the compressed folders patch. I don't think I understand the meaning of a *BSD port at all. Sorry. Ports are a freebsd feature ... packages which download the source and compile as per a readymade makefile, after applying certain other patches. quoting from /usr/ports/mail/mutt-devel/Makefile (for mutt 1.3.19) .if defined(WITH_VVV_PATCHES) defined(WITH_COMPRESSED_FOLDERS) .error WITH_VVV_PATCHES and WITH_COMPRESSED_FOLDERS cannot be used together .endif -suresh
mutt 1.2.5 and noatime filesystems
Hi, I'm using mutt 1.2.5 on FreeBSD 4.3-STABLE box. Today I've mounted /var partition with options noatime. I rebooted, but later mutt doesn't work. Each time that I exit from a Mailbox and press TAB+TAB to check for new messages, mutt notifies that there are new messages in mailboxes that I've check before. Then I enter in one of this mailboxes, but there aren't new mex. I've remounted /var without noatime and mutt works fine... Any idea?? Sorry if my English is very poor...
xterm colored Mutt
Hello, I have the problem of having a non-colored mutt, when starting it in xterm. $TERM is xterm. When I change $TERM to linux or xterm-color mutt will start with colors. So I guess it has something to do with terminfo. Unfortunately I don't know a lot about it. On my SuSE-System mutt starts colored within xterm even with $TERM=xterm, so I guess they changed properties of the xterm-terminfo-file or mutt is looking for something else to determine if it should use colors or not. So, can someone help me with this? How can I tell xterm to use xterm-color instead of xterm terminfo without having to set $TERM manually? André.
Re: mutt 1.2.5 and noatime filesystems
Matteo [EMAIL PROTECTED] wrote: I'm using mutt 1.2.5 on FreeBSD 4.3-STABLE box. Today I've mounted /var partition with options noatime. I rebooted, but later mutt doesn't work. Each time that I exit from a Mailbox and press TAB+TAB to check for new messages, mutt notifies that there are new messages in mailboxes that I've check before. Then I enter in one of this mailboxes, but there aren't new mex. I've remounted /var without noatime and mutt works fine... As I understand it, Mutt detects new mail by comparing the mailbox's last modification time to the last access time. If you mount the partition with noatime, you've eliminated the access time, so how can you expect Mutt to detect new mail properly? -- Linux: The Choice of the GNU Generation
popping mail into an imap mailbox
All, I connect to my mailboxes over an imap/ssl connection. I also have one mailbox that I connect to over pop. I have been using Mutt's pop functionality to grab the pop messages and then upload them into the imap mailbox. The problem is that when I hit 'G' to pop the messages, they are downloaded successfully, then I see them being uploaded to the imap folder, but I do not see them displayed in mutt's view of the folder. I have to leave the folder and then return to it for the messages to be displayed. When I do they have the 'O' unread message flag. I have tried hitting the '$' key, hoping it would be a bidirectional sync, not just a sync local to remote. It hasn't worked. Is there a key or configuration parameter that will allow me to see the messages I pop-then-upload without having to leave the folder? Here is the imap section of my .muttrc: set imap_user=[EMAIL PROTECTED] unset imap_passive unset imap_list_subscribed set imap_servernoise unset imap_force_ssl And here is the config fragment that I have a folder-hook execute when I go to the folder in question: set pop_host=pop.business.earthlink.net set pop_user=[EMAIL PROTECTED] set spoolfile==work.ssn TIA --N. -- Nate Johnston [EMAIL PROTECTED] GPG footprint: DEAF B505 0D84 1AEF A43F 91C5 71B3 D053 D0E1 3C05 Unix System Administrator SingleSignon.net
Re: xterm colored Mutt
On Wed, 18 Jul 2001, Andre Wyrwa wrote: Hello, I have the problem of having a non-colored mutt, when starting it in xterm. $TERM is xterm. When I change $TERM to linux or xterm-color mutt will start with colors. So I guess it has something to do with terminfo. Unfortunately I don't know a lot about it. On my SuSE-System mutt starts colored within a good place to start is www.google.com (search for xterm) as I point out 2-3 times a week, xterm-color is incorrect for XFree86 xterm, ditto linux. xterm even with $TERM=xterm, so I guess they changed properties of the xterm-terminfo-file or mutt is looking for something else to determine if it should use colors or not. So, can someone help me with this? How can I tell xterm to use xterm-color instead of xterm terminfo without having to set $TERM manually? see the man-page. -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: mutt 1.2.5 and noatime filesystems
On Wed, Jul 18, 2001 at 04:26:16PM +0200, Matteo wrote: Today I've mounted /var partition with options noatime. I rebooted, but later mutt doesn't work. Each time that I exit from a Mailbox and press TAB+TAB to check for new messages, mutt notifies that there are new messages in mailboxes that I've check before. Then I enter in one of this mailboxes, but there aren't new mex. I've remounted /var without noatime and mutt works fine... Any idea?? See the first Note: in section 3.11 of the mutt manual. I'd have thought that by removing support for atime you're experiencing a variation on the problem that's spoken about there (actually the reverse problem if you think about it). -- Dave Pearson: | mutt.octet.filter - autoview octet-streams http://www.davep.org/ | mutt.vcard.filter - autoview simple vcards Mutt: | muttrc2html - muttrc - HTML utility http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode
Re: Problems with vvv port on FreeBSD
I simply untarred his port directory into my /usr/ports/mail/ dir and tried a make. On Linux, all I had to do was drop the spec file into the SPEC dir and rpm -ba mutt.spec. I haven't checked the port setup because I am still new to FreeBSD and am not quite familiar with the details therin. Notice that the vvv distribution directory has several patches? He is also kind enough to provide a mutt.spec file for building rpms and a port.1.3.19.tgz file, which is typically unzipped into the mail port directory and built for install - FreeBSDs version of package management for those Linux only dudes out there. It basically creates a package on the fly and installs it. Pretty clean as far as I can tell so far. Anyway, I am getting some problems in the regex.c file. something about 'wt' being undeclared, and undeclared functions wctype - which is actually a typedef in an included file, etc. Anyway again, here is the real confusion: this file is not changed by the patches! I built mutt-devel (distributed version of 1.3.19) and compared the regex.c files - no difference. Hmm. I also noticed the makefile in the port directory was configuring --with-regex. Maybe that is my problem. I'll try bagging that config directive. At this point, any suggestions would be quite welcome. As long as they are intended to help me get this build done anyway :) Thanks all Lou On 07/18/01 09:37 AM, Suresh Ramasubramanian sat at the `puter and typed: Louis LeBlanc [mutt-users] 17/07/01 23:51 -0400: Hey all. I am trying to get the vvv port for FreeBSD built, but it keeps dying on some wchar code. Any ideas what the hangup is there? I personally had no problems. However, there is a note which says vvv can't coexist with Roland's compressed folders patch in that port. Did you enable both? -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://acadia.ne.mediaone.net ԿԬ If A = B and B = C, then A = C, except where void or prohibited by law. -- Roy Santoro
Re: Problems with vvv port on FreeBSD
WITH_VVV_PATCHES??? what rev do you have of the mutt-devel port? I just updated yesterday, I have 1.3.19 rev 4. I didn't find that tag anywhere in the Makefile. BTW, my recent response was on target. I removed --with-regexp from the vvv Makefile and it build out nicely. Thanks Lou On 07/18/01 07:55 PM, Suresh Ramasubramanian sat at the `puter and typed: David Champion [18/07/01 09:04 -0500]: Suresh Ramasubramanian [EMAIL PROTECTED] wrote: I personally had no problems. However, there is a note which says vvv can't coexist with Roland's compressed folders patch in that port. Did you enable both? I'm not sure what that note's about, and I'm only assuming that vvv is the nntp patch (vs the other patches on his site), but I'm using VVV's nntp with the compressed folders patch. I don't think I understand the meaning of a *BSD port at all. Sorry. Ports are a freebsd feature ... packages which download the source and compile as per a readymade makefile, after applying certain other patches. quoting from /usr/ports/mail/mutt-devel/Makefile (for mutt 1.3.19) .if defined(WITH_VVV_PATCHES) defined(WITH_COMPRESSED_FOLDERS) .error WITH_VVV_PATCHES and WITH_COMPRESSED_FOLDERS cannot be used together .endif -suresh -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://acadia.ne.mediaone.net ԿԬ QOTD: Just how much can I get away with and still go to heaven?
Re: more questions
hi.. fixed it right finally. there was a problem with the termcap file. replaced it and it works fine now. thanks for the help. ankit * Andre Wyrwa [EMAIL PROTECTED] [21:42 18/07/01]: On Tue, 17. Jul 2001 um 08:00:18PM +0530, Fox Mulder wrote: yea, that is what it looks like. i am on slackware 8.0, and have terminal type set to linux. i get the same even when the terminal type is xterm, only then i dont get colors. also, it is the same in text mode, and xwindows... Do you get it under X only or in console mode, too? André.
Re: xterm colored Mutt
* Thomas E. Dickey [EMAIL PROTECTED] [21:42 18/07/01]: a good place to start is www.google.com (search for xterm) as I point out 2-3 times a week, xterm-color is incorrect for XFree86 xterm, ditto linux. i am new to this list. what will be the right setting fot xf86 if it is not xterm-color? it seems to be working fine for me.. ankit
Re: xterm colored Mutt
On Wed, 18 Jul 2001, Fox Mulder wrote: * Thomas E. Dickey [EMAIL PROTECTED] [21:42 18/07/01]: a good place to start is www.google.com (search for xterm) as I point out 2-3 times a week, xterm-color is incorrect for XFree86 xterm, ditto linux. i am new to this list. what will be the right setting fot xf86 if it is not xterm-color? it seems to be working fine for me.. xterm-xfree86 -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Newbie question
On Wed, Jul 18, 2001 at 11:52:58AM +0530, Fox Mulder wrote: * Suresh Ramasubramanian [EMAIL PROTECTED] [11:42 18/07/01]: Fox Mulder [mutt-users] 18/07/01 11:30 +0530: Hey, i dont get any such indicator. guess i will have to look it up in the manual... I tried to put in the %N to the folder_format. but, i still dont get the an N indicator next to folders containing new mail. Also, I get a zero in front of the Inc in the status bar. apparently mutt is unable to determine whether a folder has new mail or not. I am attaching my .muttr file. there is no nuttrc in the /etc diretory.. Try mine - http://www.hserus.net/muttrc.html hi.. thanks for the file. i tried it, but still no help. I still dont get the N in the folder view, and dont get the Inc field in the status bar. also, i am still getting that problem with the arrows in threads. It's been a while since I discovered this problem with my installation, so I don't remember the details, but I couldn't get the N indicator to work reliably until I configured mutt with --enable-buffy-size. Now it works fine. (I'm using mutt-1.2i on HP-UX 10.20.) Your folder_format should already contain the %N field. do i try to compile mutt myself? currently i am using the one that came with slackware 8.0.. You could try that. Before doing so, however, you might execute 'mutt -v' to see the options that Slackware compiled it with. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: timestamp of mailbox file is not updated
Might be helpful with some naive new-mail checking programs, but of course breaks mechanisms which really look for mailbox updates. I vote for removing the code. (c: Anyone objects? Noone objected - does that mean that the code will be removed in the next release? If no, what do I have to do so that it will be removed? Thanks, Andy. -- Dr. Andy Spiegl, Radio Marañón, Jaén, Perú E-Mail: [EMAIL PROTECTED], [EMAIL PROTECTED] URL: http://spiegl.de, http://radiomaranon.org.pe PGP/GPG: see headers o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~
Re: Random Sigs? (the shortest of all!)
* On Thu, Jul 12, 2001 at 11:31:26AM -0700, Chris Fuchs wrote: On Thu, Jul 12, 2001 at 11:35:59AM -0400, darren chamberlain wrote: Chris Fuchs [EMAIL PROTECTED] said something to this effect on 07/11/2001: #!/usr/local/bin/perl #randsig.pl, by Don Blaheta. Released into public domain, blah, blah, blah. # Generates a signature randomly from a single file of witty quotes which # the user maintains; the quotes can be multi-line, and are separated by # blank lines. This is too much work. Try this: Way, way too much work still. Try this: set signature=perl -an0777F'\n\s*\n' -e 'print \$F[rand(@F)]' ~/quotes.txt| Of course you need a ~/quotes.txt file with empty lines as separators. -- HIPPOLYTE: Ou que d'un beau trépas la mémoire durable, Eternisant des jours si noblement finis, Prouve à tout l'univers que j'étais votre fils. (Phèdre, J-B Racine, acte 3, scène 5)
Re: vfolders
On Thu 12-Jul-2001 at 12:49:39PM +, Jonathan Miller wrote: I really love the concept of vfolders, which are basically SQL statements that create folders out of a bunch of mail in a database. This is a definite issue with the mail-as-file system for storing mail. Like most people, I have my mail archive categorised and stored by context (lists|customers|projects etc..), which is fine most of the time since 'limit' does great searches. The problem is mail that belongs in two or more categories. Currently I just put multiple copies wherever I think I might want to look for it later - obviously this is a really inefficient use of space and it would be nice to be able create links in/between Maildirs rather than copying the files (kind of like cross-postings in a news spool). When I had everything in mbox files, I occasionally used grepmail/grepm to do cross-mailbox searches. The cute thing with grepm is that it creates an mbox file with the search results and opens it in mutt. This is something like your 'vfolders', though painfully slow with the amount of mail I've got. I've thought about writing a script that does the grepm thing with Maildirs. Ideally it would create the vfolder as a Maildir containing only linked files, so I could have as many vfolders as I like without having to go and buy a bigger disc. Maybe someone has already written this. Bruno -- http://bruno.postle.net/
Re: xterm colored Mutt
Well, I'm afraid I don't have any such entry in my termcap file. I do, however, have this one: xterm-color|xterm-co|xterm with ANSI colors:\ :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=xterm: This implies to me that xterm-color _is_ a valid setting. When I try setting TERM=xterm-xfree86 or just xterm-xfree86, I get the following: Error opening terminal: xterm-xfree86. Which implies that xterm-xfree86 is an invalid setting for the TERM variable. To quote the man xterm: Termcap(5) entries that work with xterm include ``xterm,'' ``vt102,'' ``vt100'' and ``ansi,'' and xterm automatically searches the termcap file in this order for these entries and then sets the ``TERM'' and the ``TERM- CAP'' environment variables. and: -tn name This option specifies the name of the terminal type to be set in the TERM environment variable. This terminal type must exist in the termcap(5) database and should have li# and co# entries. So . . . What am I to do? If xterm-color works and xterm-xfree86 does not, why shouldn't I use xterm-color? I know why I shouldn't use xterm-xfree86 - it just won't work :) BTW, the info I have included here applies to my FreeBSD system. I still get color with TERM=xterm on Mandrake - which does have the xterm-xfree86 entry. I suspect this whole thing really just boils down to whats in the termcap. In search of enlightenment . . . On 07/18/01 12:32 PM, Thomas E. Dickey sat at the `puter and typed: On Wed, 18 Jul 2001, Fox Mulder wrote: i am new to this list. what will be the right setting fot xf86 if it is not xterm-color? it seems to be working fine for me.. xterm-xfree86 -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://acadia.ne.mediaone.net ԿԬ Matz's Law: A conclusion is the place where you got tired of thinking.
Re: xterm colored Mutt
On Wed, Jul 18, 2001 at 03:44:51PM -0400, Louis LeBlanc wrote:
Well, I'm afraid I don't have any such entry in my termcap file. I do,
however, have this one:
sigh - xterm's distribution includes a termcap which can be added (up front)
to the /etc/termcap file.
xterm-color|xterm-co|xterm with ANSI colors:\
:pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=xterm:
This implies to me that xterm-color _is_ a valid setting. When I try
setting TERM=xterm-xfree86 or just xterm-xfree86, I get the
following:
Error opening terminal: xterm-xfree86.
Which implies that xterm-xfree86 is an invalid setting for the TERM
variable.
To quote the man xterm:
yes (I note that ``xterm-color'' is not mentioned either)
The real answer is this:
infocmp xterm-xfree86 xterm-color
comparing xterm-xfree86 to xterm-color.
comparing booleans.
OTbs: F:T.
bce: T:F.
mc5i: T:F.
npc: T:F.
comparing numbers.
comparing strings.
blink: '\E[5m', NULL.
cbt: '\E[Z', NULL.
civis: '\E[?25l', NULL.
cnorm: '\E[?25h', NULL.
ech: '\E[%p1%dX', NULL.
el1: '\E[1K', NULL.
enacs: '\E(B\E)0', '\E)0'.
flash: '\E[?5h$100/\E[?5l', NULL.
hpa: '\E[%i%p1%dG', NULL.
ich: '\E[%p1%d@', NULL.
invis: '\E[8m', NULL.
is2: '\E[!p\E[?3;4l\E[4l\E', '\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E'.
kDC: '\E[3;2~', NULL.
kEND: '\EO2F', NULL.
kHOM: '\EO2H', NULL.
kIC: '\E[2;2~', NULL.
kLFT: '\EO2D', NULL.
kNXT: '\E[6;2~', NULL.
kPRV: '\E[5;2~', NULL.
kRIT: '\EO2C', NULL.
kb2: '\EOE', NULL.
kcbt: '\E[Z', NULL.
kend: '\EOF', NULL.
kent: '\EOM', NULL.
kf1: '\EOP', '\E[11~'.
kf13: '\EO2P', '\E[25~'.
kf14: '\EO2Q', '\E[26~'.
kf15: '\EO2R', '\E[28~'.
kf16: '\EO2S', '\E[29~'.
kf17: '\E[15;2~', '\E[31~'.
kf18: '\E[17;2~', '\E[32~'.
kf19: '\E[18;2~', '\E[33~'.
kf2: '\EOQ', '\E[12~'.
kf20: '\E[19;2~', '\E[34~'.
kf21: '\E[20;2~', NULL.
kf22: '\E[21;2~', NULL.
kf23: '\E[23;2~', NULL.
kf24: '\E[24;2~', NULL.
kf25: '\EO5P', NULL.
kf26: '\EO5Q', NULL.
kf27: '\EO5R', NULL.
kf28: '\EO5S', NULL.
kf29: '\E[15;5~', NULL.
kf3: '\EOR', '\E[13~'.
kf30: '\E[17;5~', NULL.
kf31: '\E[18;5~', NULL.
kf32: '\E[19;5~', NULL.
kf33: '\E[20;5~', NULL.
kf34: '\E[21;5~', NULL.
kf35: '\E[23;5~', NULL.
kf36: '\E[24;5~', NULL.
kf37: '\EO6P', NULL.
kf38: '\EO6Q', NULL.
kf39: '\EO6R', NULL.
kf4: '\EOS', '\E[14~'.
kf40: '\EO6S', NULL.
kf41: '\E[15;6~', NULL.
kf42: '\E[17;6~', NULL.
kf43: '\E[18;6~', NULL.
kf44: '\E[19;6~', NULL.
kf45: '\E[20;6~', NULL.
kf46: '\E[21;6~', NULL.
kf47: '\E[23;6~', NULL.
kf48: '\E[24;6~', NULL.
kfnd: NULL, '\E[1~'.
khome: '\EOH', NULL.
kslt: NULL, '\E[4~'.
mc0: '\E[i', NULL.
mc4: '\E[4i', NULL.
mc5: '\E[5i', NULL.
op: '\E[39;49m', '\E[m'.
rmam: '\E[?7l', NULL.
rmcup: '\E[?1049l', '\E[2J\E[?47l\E8'.
rmso: '\E[27m', '\E[m'.
rmul: '\E[24m', '\E[m'.
rs1: '\Ec', NULL.
rs2: '\E[!p\E[?3;4l\E[4l\E', '\E7\E[r\E8\E[m\E[?7h\E[?1;3;4;6l\E[4l\E'.
setb:
'\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m', NULL.
setf:
'\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m', NULL.
sgr:
'\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\016%e\017%;',
NULL.
sgr0: '\E[m\017', '\E[m'.
smam: '\E[?7h', NULL.
smcup: '\E[?1049h', '\E7\E[?47h'.
vpa: '\E[%i%p1%dd', NULL.
Termcap(5) entries that work with xterm include
``xterm,'' ``vt102,'' ``vt100'' and ``ansi,'' and xterm
automatically searches the termcap file in this order for
these entries and then sets the ``TERM'' and the ``TERM-
CAP'' environment variables.
and:
-tn name
This option specifies the name of the terminal
type to be set in the TERM environment variable.
This terminal type must exist in the termcap(5)
database and should have li# and co# entries.
So . . .
What am I to do? If xterm-color works and xterm-xfree86 does not, why
shouldn't I use xterm-color? I know why I shouldn't use xterm-xfree86
- it just won't work :)
BTW, the info I have included here applies to my FreeBSD system.
I still get color with TERM=xterm on Mandrake - which does have the
xterm-xfree86 entry. I suspect this whole thing really just boils
down to whats in the termcap.
In search of enlightenment . . .
On 07/18/01 12:32 PM, Thomas E.
Re: xterm colored Mutt
In order to turn on color in xterm enter the following line in ~/.Xdefaults *customization: -color This will turn on color in all apps that use color in an xterm window. Ed -- _ Linux, the choice | One difference between a man and a machine of a GNU generation -o) | is that a machine is quiet when well oiled. /\ | _\_v | | -
Re: xterm colored Mutt
Ed Robitaille wrote In order to turn on color in xterm enter the following line in ~/.Xdefaults *customization: -color This will turn on color in all apps that use color in an xterm window. Oops ! You'll have to re-start 'X' or or enter the command that re-init's 'X' to see this go into effect. Ed -- _ Linux, the choice | Wiker's Law: Government expands to absorb of a GNU generation -o) | revenue and then some. /\ | _\_v | | -
Re: xterm colored Mutt
On Wed, Jul 18, 2001 at 09:21:24PM -0400, Ed Robitaille wrote: Ed Robitaille wrote In order to turn on color in xterm enter the following line in ~/.Xdefaults *customization: -color This will turn on color in all apps that use color in an xterm window. However I'm pretty sure that color ls in freebsd only works with xterm-color (as far as the various xterm termcaps go). I am pretty sure the person who sent the original message was using freebsd. I use xterm as my termcap on Linux machines (even if I'm connecting from my workstations which are both freebsd) but i use xterm-color in freebsd. does anyone know for sure that you can get the xterm-xfree86 termcap working on *bsd and that color ls still works with it? w
Re: xterm colored Mutt
On 2001.07.18, in [EMAIL PROTECTED], Ed Robitaille [EMAIL PROTECTED] wrote: Ed Robitaille wrote In order to turn on color in xterm enter the following line in ~/.Xdefaults *customization: -color This will turn on color in all apps that use color in an xterm window. Oops ! You'll have to re-start 'X' or or enter the command that re-init's 'X' to see this go into effect. Or: % xrdb -merge ~/.Xdefaults -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Problems with vvv port on FreeBSD
Thus spake Suresh Ramasubramanian ([EMAIL PROTECTED]): Ditto - I cvsup'd yesterday, after posting the article you replied to. Where might one find this fabled CVS repository? I tried the one mentioned in the FAQ but it's refusing connections... -Justin -- [ ] -- Justin R. Miller - [EMAIL PROTECTED] -- [ ] [ ] -- see full headers for PGP key information -- [ ] [ ] -- http://solidlinux.com/~justin/pubkey.asc -- [ ] PGP signature
Re: Problems with vvv port on FreeBSD
Justin R. Miller [mutt-users] 18/07/01 23:22 -0400: Thus spake Suresh Ramasubramanian ([EMAIL PROTECTED]): Ditto - I cvsup'd yesterday, after posting the article you replied to. Where might one find this fabled CVS repository? I tried the one mentioned in the FAQ but it's refusing connections... There are literally dozens of freebsd cvsup repositories - as I'm in India I prefer cvsup.jp.freebsd.org and cvsup.kr.freebsd.org As for the mutt cvs repository take a look at http://www.mutt.org -suresh -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Problems with vvv port on FreeBSD
Thus spake Suresh Ramasubramanian ([EMAIL PROTECTED]): There are literally dozens of freebsd cvsup repositories - as I'm in India I prefer cvsup.jp.freebsd.org and cvsup.kr.freebsd.org As for the mutt cvs repository take a look at http://www.mutt.org That's what I'm talking about, the mutt one. The one in the FAQ is refusing pserver connections. -Justin -- [ ] -- Justin R. Miller - [EMAIL PROTECTED] -- [ ] [ ] -- see full headers for PGP key information -- [ ] [ ] -- http://solidlinux.com/~justin/pubkey.asc -- [ ] PGP signature
Re: Newbie question
* Gary Johnson [EMAIL PROTECTED] [22:18 18/07/01]: It's been a while since I discovered this problem with my installation, so I don't remember the details, but I couldn't get the N indicator to work reliably until I configured mutt with --enable-buffy-size. Now it works fine. (I'm using mutt-1.2i on HP-UX 10.20.) Your folder_format should already contain the %N field. do i try to compile mutt myself? currently i am using the one that came with slackware 8.0.. You could try that. Before doing so, however, you might execute 'mutt -v' to see the options that Slackware compiled it with. i am pasting the output of mutt -v. it does list a -BUFFY-SIZE. I am not too sure what the '-' sign means. does this mean that this this was an option, or does it mean that it wasnt an option? thanks for the help. ankit mohan $mutt -v -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/spool/mail SHAREDIR=/usr/share/mutt SYSCONFDIR=/etc/mutt ISPELL=/usr/bin/ispell To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. ---
Re: Newbie question
Fox Mulder [mutt-users] 19/07/01 10:17 +0530: i am pasting the output of mutt -v. it does list a -BUFFY-SIZE. I am not too sure what the '-' sign means. does this mean that this this was an option, or does it mean that it wasnt an option? + = used. - = not used. +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
