On Wednesday, April 24 at 03:37 AM, quoth Vincent Lefevre:
On 2013-04-23 20:06:10 -0500, Derek Martin wrote:
Cute, but DoS is not the only vector as you well know. Using the
message store or any part of the message store is not a workable
solution. It's (in general) data from an untrusted
On Tuesday, April 16 at 12:25 PM, quoth Tim Gray:
I run mutt on OS X. As I'm sure many of you know, OS X has a system
wide content indexing and search system called Spotlight. Spotlight
already indexes and searches emails stored individually as files
(similar to maildir) and OS X also has a
On Monday, April 8 at 03:31 PM, quoth Derek Martin:
It's much easier to complain when something bugs you than it is to
remember to express appreciation when everything is fine...
You know, that's an excellent point, and a good reminder. So:
I would like to profess that my copy of mutt has
On Wednesday, March 27 at 05:04 PM, quoth isdtor:
I've been wondering for a while whether it is possible to completely
save a mailbox (i.e. mbox) in exactly its current state, deleted
messages and all, without actually purging deleted messages? In other
words, I would like to preserve the
On Tuesday, July 31 at 02:41 PM, quoth Vincent Lefevre:
I would rather see a standalone SMTP-client (possibly designed for
Mutt users) than a built-in SMTP-client:
There *is* one! It's called msmtp. :) On their wiki, they say It was
designed with Mutt in mind, which is where the M came from.
On Saturday, July 28 at 11:19 AM, quoth Rado Q:
I like things to be simple easy to use, too.
But within its own area of operation.
I prefer modular solutions to use them as _I_ like them, gives me
more power, less dependence on fixed or not easily changed features.
So we're agreed, then:
+1 +0
On Wednesday, July 18 at 10:35 AM, quoth David Champion:
I'm writing in reaction to a request on mutt-users, but this is not
really a response to that post -- it's more a response to a recent
upswing in requests of this type.
It would be straightforward to add a search pattern
On Monday, September 28 at 11:20 PM, quoth Brendan Cully:
I am deeply saddened to report that Rocco Rutte died of cancer last
week. He'd been sick for some time, but it still seems terribly
sudden. I wish we'd had a chance to meet in person, and I am glad
that he chose to spend so much of his
On Tuesday, September 22 at 03:10 PM, quoth Manish Katiyar:
Yes,... I can open it in thunderbird.though looks like
thunderbird takes very long time to fetch headers and it appears it
does it in batches.
This has been discussed recently on one of the mutt lists. Since
Thunderbird
On Friday, August 28 at 03:54 PM, quoth Mun Johl:
I didn't anticipate that Outlook would alter the format of the
encapsulated message when it forwarded it as an attachment. That
may be standard procedure, but it throws a wrinkle into the works.
For example, a signature delimiter -- is
On Wednesday, August 19 at 09:04 AM, quoth Aviv Greenberg:
It's google's IMAP servers sample conversation with the bug is
below. The skips are consistent (ie when i repeat fetching headers i
miss the same messege ids). I'm missing ~35 headers out of 280K:
Ahhh, Google. Yeah. They're
On Wednesday, August 19 at 12:32 AM, quoth Aviv Greenberg:
It appears that the imap server skips some headers in the FETCH
command. Is this normal? Is this whats casuing the error? What can i
do?
It's definitely NOT normal. What IMAP server are you using? If you can
produce an example IMAP
On Saturday, August 1 at 08:04 PM, quoth Stephen Hunt:
If I leave my mutt(set up with gmail for IMAP) open for more than
4-5 minutes untouched all my messages disappear from the screen
and on the bottom of the screen I get this error tls_socket_read
(A TLS packet with unexpected length was
On Monday, July 20 at 09:27 PM, quoth Stefan Petrea:
I think this is a bug.
Why?
I can see why it's a *problem*, but why do you think it's a mutt bug?
~Kyle
--
Liberty is the only thing you cannot have unless you are willing to
give it to others.
On Friday, July 10 at 08:21 AM, quoth b a:
I understand that you enclose as much calls as you can inside
mutt_allow_interrupts(1); ... mutt_allow_interrupts(0);
How does that translate later on , how does it help ncurses or any
other code that's supposed to run run ? Your code doesn't have
On Friday, July 10 at 04:28 PM, quoth Thomas Dickey:
yes. I've some test-screens in vttest (in the xterm-related part),
which can be used for a quick check. The tack program also has a
screen for this, though it doesn't exercise as many cases.
Drat.
HEH - that's a fun little program.
I just discovered the bce fix to the whole blanks at the end of all
lines in my email problem, and I have some questions about things
that bce breaks in the rest of mutt.
For those who don't know, ncurses normally uses space characters to
erase the terminal (i.e. set it to blank), which can
On Thursday, July 9 at 07:31 PM, quoth Thomas Dickey:
On Thu, 9 Jul 2009, Kyle Wheeler wrote:
(If it helps, I'm using Apple's Terminal.app... it may not have the
greatest BCE support, but surely there's a way to clear things
without going the route of *spaces*)
as far as I know, it has
On Friday, July 10 at 05:24 AM, quoth b a:
When pressing enter to view an email with a big attachement mutt
becomes unresponsive until the message is fetched.
I've had the same complaint.
I don't like this and I will fix it in the next few days by binding
the escape key to break the loop on
On Saturday, July 4 at 11:10 AM, quoth Derek Martin:
The Mac is the only platform I've heard of still having
Unicode-related issues (and shame on Apple for that), and AFAIK they
can all be patched or worked around by now.
Er? What issues are these? I've been using a Mac for ages, and I have
On Thursday, July 2 at 10:51 AM, quoth Aron Griffis:
The idea of this changeset makes sense, but I think the
implementation might be broken. I have this in my mailcap
(heavily simplified):
text/html; firefox %s
text/html; w3m %s; needsterminal
text/html; w3m -dump %s; copiousoutput
As of
On Thursday, July 2 at 06:53 PM, quoth Rocco Rutte:
http://dev.mutt.org/doc/manual.html#mailcap-search-order
I just noticed that in the third paragraph, the second wocka around
view-mailcap is backwards. It looks like view-mailcap instead of
view-mailcap.
~Kyle
--
University politics
On Friday, June 26 at 12:00 AM, quoth Brendan Cully:
5 new changesets in mutt:
http://dev.mutt.org/hg/mutt/rev/c5d0252e8f72
changeset: 5946:c5d0252e8f72
branch: HEAD
tag: tip
user:Rocco Rutte pd...@gmx.net
date:Thu Jun 25 21:46:28 2009 +0200
summary: Fix f=f
On Friday, June 26 at 04:54 PM, quoth Rocco Rutte:
A generating agent SHOULD:
1. Ensure all lines (fixed and flowed) are 79 characters or
fewer in length, counting the trailing space but not
counting the CRLF, unless a word by itself exceeds 79
On Tuesday, June 23 at 12:00 AM, quoth Brendan Cully:
http://dev.mutt.org/hg/mutt/rev/54bc1ef602e7
changeset: 5934:54bc1ef602e7
branch: HEAD
tag: tip
user:Rocco Rutte pd...@gmx.net
date:Mon Jun 22 17:36:21 2009 +0200
summary: Make mutt_curses_(error|message)
On Tuesday, June 23 at 12:30 AM, quoth Brendan Cully:
I've just pushed Vincent's simple fix.
Many thanks!
~Kyle
--
This is my simple religion. There is no need for temples; no need for
complicated philosophy. Our own brain, our own heart is our temple;
the philosophy is kindness.
On Tuesday, June 23 at 08:21 PM, quoth Rocco Rutte:
So the only real issue is when the FS isn't accurate about the times
for the directory.
Yeah... Of course filesystem problems are always an issue, but I guess
my thought is: for just about all filesystems, keeping track of a
last modified
On Monday, June 22 at 10:43 AM, quoth Derek Martin:
On Mon, Jun 22, 2009 at 04:43:27PM +0200, Moritz Barsnick wrote:
I think this behavior is not desired.
I meant to add that if you want to mark something that needs your
attention, but *don't* want to treat it as new (unseen) mail, then you
On Wednesday, June 17 at 05:28 PM, quoth Rocco Rutte:
This would appear to break situations like mine, where I use '=' to
refer to $folder:
mailboxes = =friends =mutt
No, because mutt_expand_path() is called in advance that would expand a
leading '=' using $folder. However, ==foo is
On Saturday, June 13 at 06:37 AM, quoth Thomas Dickey:
On Sat, 13 Jun 2009, Mutt wrote:
#3252: mutt: Should use transliterations for charset conversions
--+-
Reporter: anto...@dyne.org | Owner: mutt-dev
Type:
On Thursday, June 11 at 01:38 PM, quoth Patrick Welche:
I don't use the header cache - I would have to enable it to use it
right?
(off by default?)
Ahhh, I assumed that you did use it. Yeah, you'd have to enable it.
Hmm. I don't know how mutt handles new/old tracking on IMAP without
the
|
# Different return addresses for different mailing lists
subscribe '^mutt-us...@mutt\.org$'
send-hook mutt-us...@mutt.org \
my_hdr From: Kyle Wheeler kyle-m...@memoryhole.net
alternates '^kyle-m...@memoryhole\.net$'
subscribe '^mutt-...@mutt\.org$'
send-hook mutt-dev@mutt.org
On Thursday, June 11 at 11:44 PM, quoth Heinrich Langos:
mailers) will create a References: header that labels your
message as being a response to that other thread. Many mail
programs, including mutt and most mailing list archive software,
will then treat your message as being part of the
On Monday, June 8 at 12:21 PM, quoth Patrick Welche:
Now I'm even more confused: mutt says after several days of not
reading mail, mutt says:
Msgs:220272 New:6 Old:710
and those refer to the 6 new messages I received while it is open.
YIKES - that is a *huge* mailbox!
It's interesting
On Monday, June 1 at 10:27 PM, quoth Patrick Welche:
So the first question is, am I missing a new setting in mutt?
No - mutt's current behavior uses both \Unseen and \Recent along with
its own header cache in order to be reliable across multiple brands of
IMAP servers.
And then how do I
On Sunday, March 22 at 12:25 PM, quoth Albert Oliver:
Most email clients support them, and I'd like that mutt could also
be there.
Not that I don't think this would be a good idea, I do. BUT... do most
clients *really* support arbitrary IMAP tags? I've used Apple Mail,
and MS Outlook and
Does anyone here have any ideas?
- Forwarded message from Joshua Tinnin krinkly...@speakeasy.net -
On Wed, Mar 11, 2009 at 11:18:30AM -0500, Kyle Wheeler wrote:
On Wednesday, March 11 at 10:36 AM, quoth Joshua Tinnin:
Here it is:
Program received signal SIGSEGV, Segmentation fault
On Tuesday, February 17 at 05:35 PM, quoth Kyle Wheeler:
#3 0x000ca55c in mutt_socket_poll (conn=0x18c9000) at
mutt_socket.c:168
Something else I noticed... mutt_socket_poll relies on conn-bufpos,
conn-available, and conn-conn_poll, none of which are reset when a
connection gets
It would appear that the UPDATING document is slightly incorrect,
which may be confusing for folks in the future. It claims that there's
a new config variable ssl_verify_hostname, while the muttrc man page
describes it as ssl_verify_host. I've confirmed that mutt doesn't
recognize
On Tuesday, January 13 at 06:57 AM, quoth Brendan Cully:
Should be fixed in 10e224e86f0b. Thanks again for spotting.
Cool! That was fast! :)
~Kyle
--
If women didn't exist, all the money in the world would have no
meaning.
-- Aristotle
With recent changes to the mutt source, an infinite recursive loop has
been created in some configuration scenarios. Specifically, if you
have account-hooks to set your $folder and then attempt to set your
$folder. For example:
account-hook 'm...@server' \
'set
On Tuesday, December 16 at 01:48 PM, quoth Erik Hovland:
Some headers provide no useful symbols to the file that includes it.
This means that the header is optional. And since it is optional, then
removing it saves time (less for cpp to process) and space.
As a guy whose done a little bit of
I recently updated to the latest mutt source, and the behavior has
changed in an annoying way. When I compose messages now, mutt *always*
thinks that my editor has returned a non-zero exit code (specifically:
1). I use vim, and as far as I can tell, it always exits with a 0 exit
code.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, November 17 at 09:32 PM, quoth Brendan Cully:
Seems fine. Does anyone object?
I like it. :)
~Kyle
- --
Never think that war, no matter how necessary, no matter how
justified, is not a crime.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, November 17 at 07:01 AM, quoth Michael Elkins:
On Mon, Nov 17, 2008 at 03:37:00PM +0100, steve wrote:
Sometimes people send their message with the following headers:
From: email-address email-address
which isn't very nice in the index
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, November 17 at 09:37 AM, quoth Kyle Wheeler:
reply-hook '^~t email-address' 'push edit-tokill-linea
chosen name email-addressenter'
Okay, my quoting is a little off on the push line. Its easier if you
can just use an alias
On Thursday, November 13 at 12:17 PM, quoth Jeremie Le Hen:
Attached you will find a patch introducing a new match pattern: =().
Thanks to this pattern you can match the parent message of messages
matching the inner pattern.
I don't disagree with the idea, but I do disagree with the syntax.
On Tuesday, November 11 at 12:18 AM, quoth Gary Johnson:
Is this a known problem or should I investigate further?
Are you using mutt's internal regex engine? Try recompiling mutt with
the --with-regex option and see if that doesn't fix it. If it does,
then the problem is just that your Linux
On Monday, November 10 at 12:15 AM, quoth Gary Johnson:
$ echo test | mutt -s test garyjohn
Hmmm, okay, so, you're not *specifying* a return address. I suppose
the question is: what should mutt be doing in this case?
Have you set the environment variable 'EMAIL'? I'm guessing not. I'm
On Monday, November 10 at 11:42 PM, quoth TAKAHASHI Tamotsu:
This has already been fixed:
1970-01-01 00:00 + Brendan Cully [EMAIL PROTECTED] (a2e8f6fab8d3)
* smtp.c: Test that envelope from or from is set before attempting
SMTP delivery. Closes #3079.
Oh wait, since over
On Wednesday, November 5 at 03:11 PM, quoth Thomas Parmelan:
Mutt doesn't store the envelope from in the saved copy of the
message.
Yes it does. I use mbox folders. The From separator usually uses the
envelope sender. In fact, it really does for incoming messages...
Ahh, sorry, I was
On Tuesday, November 4 at 03:58 PM, quoth Thomas Parmelan:
The problem I have is that in this case the saved copy of my sent
mails have not the real enveloppe from, but the one derived from the
From:.
Mutt doesn't store the envelope from in the saved copy of the message.
The envelope is not
On Friday, October 31 at 11:21 PM, quoth TAKAHASHI Tamotsu:
So here is another patch.
%e is a pretty version of %f in $folder_format.
Hmm... there's a minor problem... in browsing around an IMAP server,
going to the parent folder is normally labelled .., but after going
through
On Friday, October 31 at 11:21 PM, quoth TAKAHASHI Tamotsu:
So here is another patch.
%e is a pretty version of %f in $folder_format.
Fantastic! It's even fewer lines than the first one!
+1 to include in mutt.
~Kyle
--
If man was meant to be nude, he would have been born that way.
On Friday, October 31 at 12:48 AM, quoth TAKAHASHI Tamotsu:
* Thu Oct 30 2008 Kyle Wheeler [EMAIL PROTECTED]
Is there some reason that the mutt buffy list is all in canonicalized
full-url form? As a bit of a screen real estate hawk, it seems a bit
wasteful that when I press 'y', I get a screen
On Thursday, October 30 at 04:50 PM, quoth Aron Griffis:
TAKAHASHI Tamotsu wrote: [Thu Oct 30 2008, 11:48:44AM EDT]
I think it takes just a few lines if you set
folder=imaps://[EMAIL PROTECTED]/INBOX/
Would it be worth making this configurable? I ask because
I access three separate accounts
On Tuesday, October 28 at 03:42 PM, quoth Aron Griffis:
An alternative would be to add an attach-glob option to mutt, which
mutt would then expand internally, for example:
mutt -g \*.jpg [EMAIL PROTECTED]
More ideas? Dissenting opinions?
What about using the same sort of parsing that's
On Monday, October 20 at 07:13 PM, quoth Patrick Welche:
I just updated to today's head (grabbing the #3000 patch, thanks!) and find
that my list of mailboxes is now just INBOX (on cyrus imap server, / ) I
set mask=
just in case, but no change. I note that imap_fix_path changed since the
last
After changeset 2050b44407bf, I’m unable to compile with qdbm. I see
that configure.in is testing for $use_qdbm, but never sets it.
Equivalent logic is used in the tokyocabinet stuff, but I don’t see
how that could possibly work *either*, since $use_tokyocabinet is
never set.
A small patch
On Tuesday, September 30 at 07:30 AM, quoth Christian Ebert:
* Kyle Wheeler on Monday, September 29, 2008 at 17:47:51 -0500
After changeset 2050b44407bf, I’m unable to compile with qdbm. I
see that configure.in is testing for $use_qdbm, but never sets it.
Sorry; typo. I meant configure.ac
Hey,
It just came to my attention that, at least when auto-viewing html
attachments, mutt uses a predictable filename rather than its usual
secure temporary file creation (e.g. it always uses $TMPDIR/mutt.html
to view html files).
This seems like a security bug, among other things. Where is
On Wednesday, September 10 at 05:54 PM, quoth Rocco Rutte:
[4f67fc336986] removes the imap_keepalive() call from the pager's
main loop and calls it everytime in km_dokey(). The change in
[12a6de725483] however only calls imap_keepalive() if
$imap_keepalive $timeout. Maybe we need something
On Wednesday, September 10 at 06:30 PM, quoth Rocco Rutte:
Sure... what is this supposed to prove? Should I back-out my change
to pager.c (I re-inserted the imap_keepalive() call)?
Yes. This shouldn't prove anything but it should fix the problem in the
right place instead of fixing the pager.
On Wednesday, September 10 at 05:54 PM, quoth Rocco Rutte:
[4f67fc336986] removes the imap_keepalive() call from the pager's
main loop and calls it everytime in km_dokey(). The change in
[12a6de725483] however only calls imap_keepalive() if
$imap_keepalive $timeout. Maybe we need something
On Monday, September 8 at 01:21 PM, quoth Rado S:
=- Kyle Wheeler wrote on Thu 4.Sep'08 at 12:00:00 -0500 -=
E.g. when you want to look up some option's docs you would normally start
searching from the beginning and hit it in the toc right away, click the
link and get where you want
On Thursday, September 4 at 03:33 PM, quoth Rocco Rutte:
Well, I don't see a semantic construct that fits here (but I'm by
far not a docbook expert). Sure, a list would do but that would look
horrible for the hundreds of options. Everything that renders to
something with indentation is bad I
Has anyone else noticed a change in pager-based timeouts?
I generally track mutt's mercurial tree, and I noticed that recently
mutt started timing out (being Disconnected for Inactivity) if I let
it sit while viewing a message (i.e. in the internal pager). However,
I can let it sit on a
On Wednesday, September 3 at 09:31 PM, quoth Rocco Rutte:
I'd like to commit a change which makes the manual contain only
chapters and sections in the manual to trim the table of contents,
mainly to remove hundreds of sections for config options.
Due to Brendan recalling objections I'd like
On Wednesday, September 3 at 11:12 AM, quoth Brendan Cully:
On Wednesday, 03 September 2008 at 12:47, Kyle Wheeler wrote:
Has anyone else noticed a change in pager-based timeouts?
I generally track mutt's mercurial tree, and I noticed that
recently mutt started timing out (being Disconnected
On Wednesday, August 13 at 12:27 AM, quoth Brendan Cully:
This patch makes me uneasy (especially during a freeze), but I'm
willing to apply it if no one else objects. I don't see what kind of
damage a hook might do in batch mode, but I can't convince myself that
it's harmless either.
Well, I
On Tuesday, August 5 at 09:51 PM, quoth Mun Johl:
I've been using w3m to render HTML messages within my mutt window
for quite a while. My HTML mailcap entries are as follows:
text/html;$HOME/bin/mutt_opera %s
text/html; w3m -dump %s; nametemplate=%s.html; copiousoutput
Looks good.
I just noticed this, but why is $time_inc mentioned twice in the
UPDATING file?
~Kyle
--
The whole problem with the world is that fools and fanatics are always
so certain of themselves, but wiser people so full of doubts.
-- Bertrand Russell
On Wednesday, May 21 at 10:49 PM, quoth Mutt:
#681: rc of mutt_display_message differs between builtin and external pager
Comment (by paul):
I've just tried to peek at this, and I have to admit I'm not sure what's
being asked for here. I set my pager to 'less' (rather than builtin), but
I
On Wednesday, May 14 at 02:34 PM, quoth Mutt:
#3048: ZWSP at start of line causes display problems in pager
Comment (by pdmef):
As it works for me on OS X (ncursesw 5.6) but not on Linux (Debian,
Gentoo; both ncursesw 5.5). So maybe it's more of a system than pure mutt
issue (e.g. curses, libc
On Thursday, March 20 at 03:47 PM, quoth Vincent Lefevre:
Do not set $charset. There are very few good reasons for it.
A good reason is to use transliteration!
I didn't say there were *NO* good reasons. Transliteration is the only
one I'm aware of, and even that has problems, as Alain
On Tuesday, March 18 at 08:42 PM, quoth Mutt:
set assumed_charset=UTF-8
set charset=UTF-8//TRANSLIT
Do not set $charset. There are very few good reasons for it.
There is *never* a good reason to use UTF-8 and //TRANSLIT at the same
time.
Suppose my name (Miek Gieben) would contain some
On Tuesday, March 18 at 09:21 PM, quoth Mutt:
It's possible that your name is being mis-encoded in email, and so
it is taking various paths through mutt on the way to being
displayed based on whether mutt notices the problem or not.
The content type of the email showing this problem is set to
On Monday, February 18 at 07:19 PM, quoth Mutt:
When I reply to a gpg encryptd mail I don't get the decrypted mail
in the reply but instead
On Mon, Feb 18, 2008 at 08:01:17PM +0100, Olaf Foellinger wrote:
gpg: fatal: unable to reopen standard input, output, or error
The gpg.rc is the
On Monday, February 18 at 09:09 PM, quoth Mutt:
This has had me riddled for quite some time now as well. Even if I
set LC_CTYPE=de_DE.iso885915 (or similar, like @euro), I need to
tell mutt about it with set charset=iso-8859-15. Or am I
overseeing something?
Mutt gets its charset from the
I just noticed, in the man page for muttrc, the description of
query_command says:
See query for more information.
But the word query doesn't appear anywhere else in the muttrc man
page. Any idea what it's referring to?
~Kyle
--
It is only possible to live happily ever after on a
On Wednesday, February 6 at 09:42 AM, quoth Patrick Shanahan:
* Kyle Wheeler [EMAIL PROTECTED] [02-06-08 09:36]:
I just noticed, in the man page for muttrc, the description of
query_command says:
See query for more information.
But the word query doesn't appear anywhere else
Heya,
So, in an attempt to get mutt to color mails the way I think, I added
these patterns to my muttrc:
# Mark deleted messages that aren't part of collapsed threads
color index color8 default '~D !~(~v)'
# Mark collapsed threads as deleted if ALL messages in the thread are
# marked deleted
On Friday, December 21 at 11:04 AM, quoth Mutt:
Not much to go on, I believe. What to do? :)
If you have debug support compiled in, you could run it with the -d2
flag and provide the ~/.muttdebug0 file. Or you could try compiling
your own version (that doesn't have the debug symbols stripped
On Wednesday, November 28 at 09:21 AM, quoth Mutt:
Please look up what WSP is in RfC2334 (it's the same as LSWP in the
older RfC822):
Just because a WSP can be either a tab or a space does not mean that
they are interchangeable and that they have no semantic meaning. The
RFC says that you
On Wednesday, November 28 at 11:04 AM, quoth Mutt:
In other words, by merely removing the CRLF, we should have the
original, pre-folding version of the header. Thus, when folding, we
may only ADD CRLFs (in specific places), rather than give ourselves
the freedom to delete and replace some of
On Wednesday, November 28 at 06:21 PM, quoth Mutt:
I'm no day-time programmer, but if someone can point me to the right
source file I'm sure I can hack a fix. I'm sending hundreds of
automated messages per day from cron to my techs and this tab is
super-annoying.
I think the right file is
On Sunday, November 4 at 04:06 PM, quoth Michael Tatge:
* On Wed, Oct 31, 2007 Mutt wrote:
Comment (by pdmef):
Just for the record: $rfc2047_parameters should do the trick.
Is there any reason to have $rfc2047_parameters?
The muttrc man page has the answer to your question. To wit:
On Sunday, November 4 at 05:48 PM, quoth Michael Elkins:
Has anyone tried to use collapse-all in a macro?
Not quite; but I use it in folder-hooks all the time.
macro index C T.\n;Wn\ct.\n mark all messages as read
Well, first of all, using characters instead of directly calling the
On Tuesday, October 9 at 03:21 PM, quoth Ben Walton:
+ /* FIXME: Make this based on an option later */
+ if (option (OPTPAGERHONOURSREVERSE) Sort SORT_REVERSE)
+ rc = OP_MAIN_PREV_UNDELETED;
+ else
+ rc =
On Friday, September 28 at 12:59 PM, quoth Ian Collier:
Apologies if this is a mutt-users issue, but it looks like mutt is being
inconsistent in how it determines whether a message came from a mailing
list.
Mmmm, not exactly. It is somewhat inconsistent, but it is documented.
A particular
On Tuesday, September 18 at 09:03 AM, quoth Mutt:
On the other hand, the question is what to do when all charsets in
$send_charset fail and $charset does not match an officially
assigned charset name, like in your case.
The options are 1) go ahead with a charset possibly not supported on the
On Thursday, September 13 at 01:02 PM, quoth Vincent Lefevre:
What it all really boils down to as far as what we mean when we say
the backspace key is that key that we press that we think will
delete the character to the left of the cursor and no more.
No, the backspace key is just the key
On Thursday, September 13 at 05:16 PM, quoth Vincent Lefevre:
On 2007-09-13 08:53:59 -0500, Kyle Wheeler wrote:
And what of keyboards without a key named backspace?
The key can't be used, so that its configuration doesn't matter.
But in general, one finds a key on the keyboard and use
On Thursday, September 13 at 04:04 PM, quoth Mutt:
On 2007-09-13 08:53:59 -0500, Kyle Wheeler wrote:
And what of keyboards without a key named backspace?
The key can't be used, so that its configuration doesn't matter.
The configuration of the BackSpace key *does* matter because
On Tuesday, September 11 at 07:37 AM, quoth Mutt:
Conversely, you can't be sure that what the user (or something else)
has configured for erase is really the backspace key.
Fair enough, but I don't expect mutt to handle pathological users.
I'm suggesting we go with least surprise. The erase
On Tuesday, September 11 at 07:48 AM, quoth Mutt:
But remember that in Mutt, the backspace key is not used in the
editor only, but also in the index, the pager and so on.
So what? Should mutt not be consistent? If I have:
bind index BackSpace delete-message
bind editor BackSpace
On Tuesday, September 11 at 04:42 PM, quoth Mutt:
essentially treating 'r' as my backspace key. Thus when I tell
mutt to bind backspace to something, I expect mutt to bind 'r' to
that something. It's simply consistent.
However readline (as you cited it in one of your messages) doesn't
work
On Tuesday, September 11 at 04:56 PM, quoth Mutt:
BackSpace must be defined by behavior, not by the ink printed on
the key, because of course no program can know what's printed on the
key.
No, that's not how the terminfo works. BackSpace means the backspace
key. No more. Just like Left means
On Wednesday, September 5 at 04:29 PM, quoth Rocco Rutte:
Hi,
the attached patch pretty-prints values for string based options. I'm not
really sure if we really need this for all cases (esp. pretty-printing for
paths), but to me it simply looks better if \r, \n and \t are pretty-printed
and
On Friday, August 31 at 05:40 PM, quoth Rocco Rutte:
currently I have two ideas (well, one from #mutt) for UI
enhancements and like to ask for input.
Looks nifty!
~Kyle
--
Power always thinks it has a great soul and vast views beyond the
comprehension of the weak; and that it is doing God's
1 - 100 of 147 matches
Mail list logo
