From: "Shaun Oliver" <shaun_oliver@optusnet.com.au>
To: <speakup@braille.uwo.ca>
Subject: RE: more mutt stuff
Date: Fri, 3 Jan 2003 11:19:32 +1100 [thread overview]
Message-ID: <002901c2b2bd$cd203bc0$1700a8c0@shaun2> (raw)
In-Reply-To: <20030102191741.GA6986@zqc.com>
Hi,
Look at the my_hdr option
If you look in /usr/doc/mutt-version/sample.muttrc
It gies some good examples of what you can do with my_hdr.
Hth
-----Original Message-----
From: speakup-admin@braille.uwo.ca [mailto:speakup-admin@braille.uwo.ca]
On Behalf Of Deedra Waters
Sent: Friday, 3 January 2003 6:18 AM
To: speakup@braille.uwo.ca
Subject: Re: more mutt stuff
Whee! It's working. It's normal again....for me at least:) One last
question and I think I can figure out the rest of what I need.
I have several different email addresses that I use for different
things. From what it looks like in the config file, I can set up sort of
message rules so that for example any mail that goes to
staff@freenode.net or dmwaters@freenode.net I can reply with
dmwaters@freenode.net. What I don't see unless I'm missing it, is the
ability to send messages from dmwaters@freenode.net using a new message
Am I missing something there?
Janina Sajka wrote
| Here's a brief excerpt from my current Mutt index screen. Sorry, the
| editor is wrapping the lines though they're not wrapped on the index
| screen itself:
|
| r 154 Telephony Voice User Interface Conference ( 49) Jim
Tobias
| fmt
| 155
| *> ( 104) Jim Tobias fmt
| 156 Mastering 88 Keys Con (Digital) Brio ( 193) Paula
| Tucker fmt
|
| Notice that this isn't the default index screen. I wanted status,
| message number, then subject, in that order. So, I have the following
| in my .muttrc:
|
|
| set index_format = "%Z %4C %s %?M?(#%03M)&(%4l)? %F %{fmt}"
|
| The blank subject part of #155 indicates that it's in the thread with
| 154. This is behavior you can change, though I don't recall how just
| now.
|
| Certainly, you can set mutt to not thread, which would probably do it
| right there.
|
| PS: My %[fmt] is clearly wrong. Guess I should fix it! <grin>
|
| Deedra Waters writes:
| >
| > The only thing that bugs me about not seeing more of the subject
| > lines is that a lot of messages look blank. For example the "logging
| > in on multiple consoles thread" It makes it a lot harder to just
| > skim threw messages that way. I liked the fact that pine showed me
| > at least part of the subject line so I could just ignore the stuff I
| > didn't want to read.
|
| _______________________________________________
| Speakup mailing list
| Speakup@braille.uwo.ca
| http://speech.braille.uwo.ca/mailman/listinfo/speakup
---end quoted text---
--
Help support Freenode and pdpc: http://www.freenode.net/contrib.shtml
My webpage: http://www.dmwaters.us
Check out WOPN Freenode radio! http://www.wopn.org
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters
` Kerry Hoath
` Deedra Waters
` Janina Sajka
` Kerry Hoath
` Janina Sajka
` Deedra Waters
` Janina Sajka
` Deedra Waters
` Janina Sajka
` Shaun Oliver [this message]
` Deedra Waters
` Shaun Oliver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901c2b2bd$cd203bc0$1700a8c0@shaun2' \
--to=shaun_oliver@optusnet.com.au \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).