On Mon, Sep 28, 2009 at 11:20:00PM -0700, Brendan Cully wrote:
> 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 muc
On Thu, Oct 23, 2008 at 10:07:02AM -0400, Aron Griffis wrote:
> What OS is this? There are some patches recently in mutt that
> affect cmdline processing, but your example works for me.
Confirmed to be a problem here under Linux. 2.4.26, Debian, AMD64, built
from 5554:5ea9f336dd60.
--
Paul
s
On Wed, Jul 16, 2008 at 02:34:06PM +0900, TAKAHASHI Tamotsu wrote:
> +while (mutt_iconv (cd, &ib, &ibl, &ob, &obl, inrepls, outrepl) ==
> (size_t)-1)
[...]
> + safe_realloc (&buf, len + obl + 1);
> +}
Is it possible to add some kind of limit condition on this? Call me
paranoid, but
On Wed, May 21, 2008 at 10:04:44PM -, Mutt wrote:
> I've never attached something to a bug via email before, let's see how
> this goes... }}}
Well, it managed to attach the patch. I don't think making people go to a
bug report to download a patch is likely to get it applied, though, so here
On Wed, May 21, 2008 at 12:48:22PM +0200, Rocco Rutte wrote:
> the object files. Using the attached patch I also get no warnings, but
> I'm not sure the approach using casts is really right...
I can't think of a better one, offhand. That doesn't mean much though.
I got no warnings when buildin
On Tue, May 20, 2008 at 12:35:36PM +0100, Paul Walker wrote:
> I'm not sure whether these are caused by %lld/off_t actually being
> different on AMD64 to x86, or whether they come out for everyone. Being
> able to use -Werror would be nice, though, so I might look into them
> som
On Tue, May 20, 2008 at 12:05:32PM +0200, Rocco Rutte wrote:
> Thanks. Do you get more warnings on amd64? If so I'd like to fix them with
> one patch instead of a rate of one file per day. :)
But I get more entries in the ChangeLog that way! :-)
No more pointer warnings. I get the usual ones abo
On Mon, May 19, 2008 at 06:50:17PM +0200, Rocco Rutte wrote:
>> The attached patch changes the print to use "%p" instead.
> Thanks, I've pushed it.
Hm. Something weird going on here; it's in the main mutt copy I keep synced
with hg, but any copies I make with "hg clone" don't have it in place.
Th
On Sun, May 18, 2008 at 06:58:48PM -0400, Jean-Pierre Radley wrote:
> My word, the very first line of my message said 1.5.18, so why are you
> asking me what version?
Because I missed that bit. :) It was where most people put "hi" or similar,
so my brain just skipped it.
> The platform is SCO OS
On Sun, May 18, 2008 at 05:10:22PM -0400, Jean-Pierre Radley wrote:
> Why would the directory size, 38416, be represented by mutt as dK ?
Bit difficul to say, based just on that. Out of interest, which mutt
version, and which platform (and version) is this on? Linux, or *BSD...? Is
this when you'
On Sun, May 18, 2008 at 01:45:14AM -, Mutt wrote:
> mutt 1.4 is not going to get anything but security fixes at this point...
If that's the case, we should probably aim to get mutt 1.6 out sooner rather
than later.
--
Paul
I get a warning building init.c on my AMD64 box, because one of the debug
prints casts pointers to "unsigned int". This isn't large enough to hold a
64-bit pointer.
The attached patch changes the print to use "%p" instead. I believe this is
standard C, but if people are aware of platforms where mu
On Sat, Mar 08, 2008 at 03:30:18PM +0100, Thomas Roessler wrote:
> Pointers and integers are not interchangeable. Zero is the
> sole exception: the constant zero may be assigned to a
> pointer, and a pointer may be compared with the constant zero.
Ah. Missed that bit. :) My mis
On Sat, Mar 08, 2008 at 02:53:51AM +0100, Vincent Lefevre wrote:
> where X is an array. Moreover, gcc gives a warning for
> if (X == 0)
> but not for
> if (X == (void *) 0)
> This is completely unintuitive!
Why is this unintuitive?
X is a pointer.
0 is *not* a pointer. It's an integer.
(void
On Sat, Mar 08, 2008 at 03:39:40AM +0100, Vincent Lefevre wrote:
> You missed the point: gcc emits the warning even in the cases where such a
> test is necessary.
Agreed. However, in this case the test is *not necessary*. It serves no
purpose. If someone later coming along changes the code so tha
On Mon, Mar 03, 2008 at 04:38:00PM +0100, Thomas Roessler wrote:
> I don't think these particular cases are taken too far.
In which case we'll just have to disagree on that. ;-)
--
Paul
On Mon, Mar 03, 2008 at 02:48:35PM +0100, Thomas Roessler wrote:
> Indeed, it is -- in particular if (like in this case, I believe) the
> code which makes foo constant might change in the future in a way
> that would make foo non-constant.
But you can say that about any item of code. Any part of
On Mon, Mar 03, 2008 at 12:20:02PM +0100, Vincent Lefevre wrote:
> where the condition is always true, and which doesn't trigger any
> warning.
Not really, because I'd argue that "if (1)" shouldn't exist in checked in
code. In that case, the variable will not be NULL, so why are we checking to
se
On Mon, Mar 03, 2008 at 10:45:39AM +0100, Thomas Roessler wrote:
> From a quick look, the warnings are actually mistaken, and the patch
> shouldn't be applied.
I've checked, and I have to agree with gcc - the warnings are genuine. Both
variables are allocated on the stack, and can't be NULL.
Not
On Fri, Nov 23, 2007 at 03:34:54AM -0500, Derek Martin wrote:
> While I don't really oppose this, it seems to me that the far saner
> way to deal with this is for the mailing list software to allow the
> subscribing users to upload their public key, and to make the mailing
It would make it easier
On Thu, Sep 06, 2007 at 10:40:05AM -0500, David Champion wrote:
> Seems like a degenerate case of labelling to me.
> red, ~yred.
I can't find "edit-label", so I'm going to assume it's something you're
proposing.
Yeah, basically the flags are like labels, and it would be nice to use
labels instea
On Mon, Sep 03, 2007 at 11:10:54AM -0400, Derek Martin wrote:
> Granted, it's still way, way better than trying to do it with Outlook,
> which some of my coworkers do. I don't have any idea how they manage
> it. ;)
Actually, what you've described is one of the cases where Outlook is really
usefu
On Fri, Aug 31, 2007 at 05:40:05PM +0200, Rocco Rutte wrote:
> 1) mutt_multi_choice() is currently used to let the user choose from quite
> a number of possible options. To fit in 80x25 they're abbreviated which
That looks nice. ;-)
> 2) When interactively entering 'attachments ?' it'll end cu
On Mon, Aug 27, 2007 at 11:13:39AM +0200, Oswald Buddenhagen wrote:
> can't this be exterminated completely?
Feel free to have a go; all you have to do is register for an account on the
trac instance.
--
Paul
signature.asc
Description: Digital signature
On Thu, Jul 19, 2007 at 05:42:38PM -0400, Derek Martin wrote:
> It seems obvious to me that if you've bothered to set a reply-to
> header on your messages, you want all replies to go to that address,
> including replies from yourself... But one or two people complained
Really? I'd have said it w
Hi all,
I've just noticed that the Debian 1.5.16 mutt, and the tip of the tree, no
longer seem to give me percentages when loading a mailbox. I found those
quite useful to know how much longer it had to go. :-)
Were they removed deliberately? Or did I just not notice a configuration
change?
--
On Sat, Jun 16, 2007 at 06:30:03PM -0400, Derek Martin wrote:
> NO INHERENT MEANING TO ANY EXIT CODE, IN THE GENERAL CASE. THERE IS ONLY
> A CONVENTION ON HOW TO INTERPRET THEM. Many programs conform to this
Which suggests that programs which violate the convention should be fixed.
There's a co
On Sat, Jun 16, 2007 at 04:10:43PM -0400, Mike Hunter wrote:
> My one concern is that I can't seem to find any documentation that ANY
> common editor actually endorses a return value that signifies a fatal
> error...but maybe we should encourage them :)
SCO are dying anyway, so I don't think that
On Tue, Jun 05, 2007 at 03:38:45PM -, Mutt wrote:
> + for (i = 4; buf[i] && i < sizeof buf; i++)
> + buf[i] = tolower(buf[i]);
If I've understood it right, if sizeof(buf) < 4 that loop will dereference
off the end of the array before checking the boundary condition. Maybe
switch
On Sat, Apr 07, 2007 at 02:10:42PM -0700, Brendan Cully wrote:
> Spam. I've made trac send a random password to the registered email
So it is. I hadn't actually paid the URLs any attention.
--
Paul
signature.asc
Description: Digital signature
On Sat, Apr 07, 2007 at 02:35:13PM -, Mutt wrote:
> The default behaviour when moving between edit fields in most user
> interfaces is to select all the text in the target edit field. Urwid
> currently just moves the cursor and doesn't
If it's not a silly question, why have you entered the
On Wed, Apr 04, 2007 at 02:30:05PM -0700, Brendan Cully wrote:
> That should just be $folder. As far as I can tell,
> $imap_home_namespace is about equivalent to
> $folder+=$imap_home_namespace
General opinion seems to agree with you, so fair enough. Like I said, I
don't actually use IMAP these d
On Tue, Apr 03, 2007 at 06:06:47PM -0700, Brendan Cully wrote:
> I'd like to yank the $imap_home_namespace option. I don't think it does
> anything sensible. It's mostly just confusing. Would anyone mind if I
> pulled it?
Well, if I don't set it then ISTR I end up viewing my home directory rather
On Sat, Mar 31, 2007 at 03:59:41AM -, Mutt wrote:
> #2871: Undelivered Mail Returned to Sender
>
> {{{
> This is the mail system at host peyresourde.cs.ubc.ca.
Um. Don't suppose there's any way to make bounces disappear...?
(Not vital, but would be nice.)
--
Paul
signature.asc
Descrip
On Thu, Mar 29, 2007 at 12:20:52PM +, Rocco Rutte wrote:
> Once we find a solution for aborted writes, I think the user is
> responsible for maintaince of the cache as he's it now for header cache
> too.
And this is one of the reasons I don't like the header cache much. It makes
things faster
On Wed, Mar 28, 2007 at 05:32:47PM -0600, Kyle Wheeler wrote:
> hurry, so I kill mutt (ctrl-\, because ctrl-c won't stop a download).
> The cache will be corrupted, because mutt didn't get a chance to
> unlink it out of the cache.
That's a good example. It also means mutt won't get a chance to
On Fri, Mar 23, 2007 at 09:06:04PM +, Dave wrote:
> If it only takes a millisecond to figure out why I'm wrong, why don't you
> spend the millisecond and post the results? I spent a few milliseconds on
If you could only get work done under Unix-type systems, then anyone using
Windows couldn'
On Fri, Mar 23, 2007 at 02:52:24AM +, Dave wrote:
> That's why they want clear, simple programs, that do clear, simple
> actions, without a long config file that by default makes decisions for
> them in a half-assed way. Gee, that's the UNIX philosophy, isn't it?
If that's the case, those pe
On Wed, Mar 21, 2007 at 11:06:32PM +0100, Oswald Buddenhagen wrote:
> at this point, it would be quite a stretch to claim that this still has
> something to do with mutt, so preferably skip over it if you are not
> interested in discussing world security policy.
Or you could take it off-list...?
This thread seems to be getting a bit personal in places. Can people please
keep the discussion related to mutt (or at least security)...?
--
Paul
signature.asc
Description: Digital signature
On Tue, Mar 20, 2007 at 07:50:40PM +, Rocco Rutte wrote:
> Well, some mutt docs say that when adding new features, the old should be
> default. Adding spaces back by force is a one liner. I can do that if it's
I'm confused here. The $indent_string variable should control what the
quoting stri
On Mon, Mar 19, 2007 at 09:18:42PM +, Rocco Rutte wrote:
> than before: When replying to f=f messages, empty lines are left empty
> whereby an empty line is a line without further content after the quoting
> characters.
I'm not entirely certain I understand this. Do you mean that if there's a
On Fri, Mar 16, 2007 at 06:00:06PM -0700, William Yardley wrote:
> I think it's reasonable to set a sane-ish default in the example, and
> assume that if the user prefers to install in a different place later
> on, they can make the appropriate change in their .muttrc.
Agreed.
--
Paul
signatu
On Sat, Mar 17, 2007 at 01:11:18AM +0100, Matthias Andree wrote:
> Yup, these are just too many keypresses if you're not using that
> folder=... stuff.
I still can't quite figure out if you're reporting this as a bug or not. :)
If you are, then how would you propose changing it?
--
Paul
signa
On Thu, Mar 15, 2007 at 05:15:26PM -0700, Brendan Cully wrote:
> On my OS X system, gpg lives in /sw/bin. Many others probably have it in
> /opt or /usr/local. I don't think /usr/bin is a particularly foolproof
Personally, I would still argue that /usr/bin is far and away the most
common. Most pe
On Thu, Mar 15, 2007 at 05:40:52PM +0100, Christoph Berg wrote:
> # Parent 5c2f2072a4dbfa69f2db7a93ae52b984f65e165c
> Remove absolute paths.
For what it's worth, I don't think this is a good change. The absolute path
will be correct for most systems, and does guard against rogue gpg's in the
pat
On Sun, Mar 04, 2007 at 02:04:39PM +0100, Matthias Andree wrote:
> Yay, but unless I'm mistaken, that's hidden on the command line
> interface when switching folders, and not easily accessible without
> re-entering password or even as a pop-up sidebar or something like that
> -- which is what I ha
On Wed, Feb 28, 2007 at 02:13:53PM -0800, Brendan Cully wrote:
> We just need to make sure that eg asciidoc does what mutt needs. No
> more than that, I think.
The problem is that what mutt needs will expand over time. Isn't that why
the doc generation was moved to docbook in the first place...?
On Thu, Mar 01, 2007 at 01:23:28PM -0800, Ryan Phillips wrote:
> This problem didn't happen with 1.5.13. If it makes a difference I'm
> using putty to ssh into the box.
I seem to remember having that problem when putty and the terminal had
different ideas about what encoding to use. I solved it
On Thu, Feb 22, 2007 at 10:57:22AM -0800, Brendan Cully wrote:
> I'd be very interested in these new bzr vs hg benchmarks. Every test
> I've seen up until now, hg has trounced bzr performance-wise. (And hg
> does renames.)
I don't have benchmarks; I'm going purely subjectively here. No pretence
On Thu, Feb 22, 2007 at 09:20:06AM -0800, Brendan Cully wrote:
> I am probably biased, since I do a fair amount of hg hacking, but it
> is certainly an improvement over CVS.
Out of interest, have you looked at bzr? I was using Mercurial at one point,
but left it for bzr quite some time ago, and h
Hi Thomas,
> Thanks to Brendan for taking over, and thanks to all of you for
> making mutt the mailer that I still prefer to use! ;-)
Just wanted to join you in thanking Brendan, and also to say thanks to you
for your work over the years. It's been much appreciated; hope you enjoy
whatever else n
On Thu, Feb 15, 2007 at 10:06:19AM +, Lars Hecking wrote:
> Normally, attaching a pdf file creates an attachemnt of type
> application/pdf, encoding base64. But I have one particular
> file that gets attached as text/plain qp. WTH?
Out of interest, is it just mutt that gets confused, or do
53 matches
Mail list logo
