On Fri, Dec 11, 2015 at 05:27:09PM -0800, Kevin J. McCarthy wrote:
> On Fri, Dec 11, 2015 at 04:31:02PM -0800, Will Yardley wrote:
> > Hrm, the replying (and pager) behavior seems the same to me; do I need
> > to set anything else?
> >
> > Patch applied cleanly except a reject on mutt.h, which was
On Fri, Dec 11, 2015 at 04:31:02PM -0800, Will Yardley wrote:
> On Fri, Dec 11, 2015 at 04:17:00PM -0800, Kevin J. McCarthy wrote:
> > On Fri, Dec 11, 2015 at 02:22:47PM -0800, Kevin J. McCarthy wrote:
> > > After thinking about it, I'm leaning towards something like
> > > $reflow_space_quotes. If
On Fri, Dec 11, 2015 at 04:17:00PM -0800, Kevin J. McCarthy wrote:
> On Fri, Dec 11, 2015 at 02:22:47PM -0800, Kevin J. McCarthy wrote:
> > After thinking about it, I'm leaning towards something like
> > $reflow_space_quotes. If set, and your $indent_string = "| ", ">>>Foo"
> > would become "| > >
On Fri, Dec 11, 2015 at 02:22:47PM -0800, Kevin J. McCarthy wrote:
> After thinking about it, I'm leaning towards something like
> $reflow_space_quotes. If set, and your $indent_string = "| ", ">>>Foo"
> would become "| > > > Foo". If unset, it would become "| >>>Foo".
> (Keeping the weird spacin
On Fri, Dec 11, 2015 at 01:48:57PM -0800, Will Yardley wrote:
> On Fri, Dec 11, 2015 at 12:34:29PM -0800, Kevin J. McCarthy wrote:
> > On Thu, Dec 10, 2015 at 10:12:37PM -0800, Will Yardley wrote:
> So based on that, I understood this to mean that $reflow_text and
> $reflow_wrap are specifically ap
On Fri, Dec 11, 2015 at 12:34:29PM -0800, Kevin J. McCarthy wrote:
> On Thu, Dec 10, 2015 at 10:12:37PM -0800, Will Yardley wrote:
> > On Thu, Dec 10, 2015 at 05:49:40PM -0800, Kevin J. McCarthy wrote:
> > > What happens with unpatched mutt-1.5.23 if you unset reflow_text?
> >
> > However, if I'm
On Fri, Dec 11, 2015 at 09:46:32AM +0100, Fabian Groffen wrote:
> On 10-12-2015 15:37:29 -0800, Kevin J. McCarthy wrote:
> > >>>foo foo >>foo
>
> This is a bug (the same happens below, snipped for brevity).
> I think what the Gentoo patch tries to achieve is to keep con
On Thu, Dec 10, 2015 at 10:12:37PM -0800, Will Yardley wrote:
> On Thu, Dec 10, 2015 at 05:49:40PM -0800, Kevin J. McCarthy wrote:
> > What happens with unpatched mutt-1.5.23 if you unset reflow_text?
>
> However, if I'm understanding the description right, it seems like this
> should be ignored li
Hello,
On Thu, Dec 10, 2015 at 03:37:29PM -0800, Kevin J. McCarthy wrote:
KJM> Below, the first column indicates the "original" content of an email.
KJM> The second column is the output when replying using the FreeBSD patch,
KJM> and the third column is output when replying using the Gentoo patch.
On 10-12-2015 15:37:29 -0800, Kevin J. McCarthy wrote:
> I have been trying to read up on format=flowed and the patches you
> referenced, but frankly both the above patch and the revised gentoo
> version at:
> http://sourceforge.net/p/gentoomuttpatches/code/ci/default/tree/07-quote.patch
> make no
ps - Given text known to be f=f, I'd also prefer to see the quoted
section like:
> > > Yay!
> >
> > Noes!
vs.
> >> Yay!
> >
> > Noes!
which is more consistent (and, I think, what the $stuff_all_quoted may
have done). Since with format=flowed text, lines starting with a '>' are
quoted, and the d
On Thu, Dec 10, 2015 at 05:49:40PM -0800, Kevin J. McCarthy wrote:
> On Thu, Dec 10, 2015 at 04:12:52PM -0800, Will Yardley wrote:
> > FWIW, I do not have $quote_quoted set, but I'm pretty sure the behavior
> > is as I expect with the FreeBSD patch for some reason. I've used the
> > FreeBSD ports v
On Thu, Dec 10, 2015 at 04:12:52PM -0800, Will Yardley wrote:
> FWIW, I do not have $quote_quoted set, but I'm pretty sure the behavior
> is as I expect with the FreeBSD patch for some reason. I've used the
> FreeBSD ports version, but have also used that patch directly when
> building on a Mac.
W
On Thu, Dec 10, 2015 at 03:37:29PM -0800, Kevin J. McCarthy wrote:
> On Mon, Nov 23, 2015 at 09:51:39PM -0800, Will Yardley wrote:
> > I would also love to see a better fix for quoting flowed text
> > when replying using *non* flowed text. Bugs #3309, #3001 have
> > a better description. FreeBSD'
On Mon, Nov 23, 2015 at 09:51:39PM -0800, Will Yardley wrote:
> I would also love to see a better fix for quoting flowed text
> when replying using *non* flowed text. Bugs #3309, #3001 have
> a better description. FreeBSD's patch (patch-1.5.XX.vvv.quote)
> http://download.openpkg.org/components/ca
On Tue, Nov 24, 2015 at 10:28:24AM -0800, Kevin J. McCarthy wrote:
> On Mon, Nov 23, 2015 at 09:51:39PM -0800, Will Yardley wrote:
> > I would also love to see a better fix for quoting flowed text when
> > replying using *non* flowed text.
> > Bugs #3309, #3001 have a better description. FreeBSD's
On Mon, Nov 23, 2015 at 09:51:39PM -0800, Will Yardley wrote:
> As a user of mutt, I would really love to see one of the trash folder
> patches make it into a release; this is a feature that most people
> expect now, and I think the various arguments for why the patch is
> better than just using ho
On Tue, Nov 24, 2015 at 02:05:54PM +0100, Moritz Barsnick wrote:
> On Sun, Nov 22, 2015 at 20:01:03 -0800, Kevin J. McCarthy wrote:
>
> > I was originally thinking about one more 1.5.x release just to give
> > more time, but I'm definitely open to just pushing straight for a
> > 1.6.0 as the next
Hi,
I pretty much "+1" the NNTP support. Disregarding the intrusive nature
of the patch, the "similarity" (I know, not "equality") of features in
and the nature of SMTP and e-mail vs. NNTP make mutt an *extremely*
wise choice for me as a newsreader. NNTP not being widespread anymore
would indeed be
On Sun, Nov 22, 2015 at 20:01:03 -0800, Kevin J. McCarthy wrote:
> I was originally thinking about one more 1.5.x release just to give
> more time, but I'm definitely open to just pushing straight for a
> 1.6.0 as the next release.
I'm all for this. Do it like Linux Torvalds: Just bump the versio
Hello!
Kevin J. McCarthy has written on Monday, 23 November, at 12:26:
>Now, that's not the patch's fault: mutt doesn't have any "plugin" hooks.
>It would be nice if we did, but it won't happen for 1.6.0. When I have
>some more time, I'll try to look more closely at the patch and see if
>ther
Hello!
Will Yardley has written on Monday, 23 November, at 21:51:
>My vote is for not including NNTP; like it or not, barely anyone
>supports it anymore (even when I worked at a fairly old school
>university, we phased our our NNTP servers several years ago, and all of
>my ISPs have shut down
On Sun, Nov 22, 2015 at 08:01:03PM -0800, Kevin J. McCarthy wrote:
>
> I know you have an extensive list of patches you maintain. Are
> there any you'd like to get committed before 1.6.0? What about the
> command-on-new-mail series? (No pressure, just asking...)
Very happy that there's some mo
On Mon, Nov 23, 2015 at 12:27:13PM +0200, Andrej N. Gritsenko wrote:
> Talking about patches I would like to see NNTP support included into next
> release at last, that way it not only can be translated but also bugs can
> be addressed and fixed, now it's too hard to do something with them since
>
Hello!
Kevin J. McCarthy has written on Sunday, 22 November, at 20:01:
>I believe we're on the same page here. I was originally thinking about
>one more 1.5.x release just to give more time, but I'm definitely open
>to just pushing straight for a 1.6.0 as the next release. Recently,
>I've m
On Sun, Nov 22, 2015 at 10:16:42PM -0600, David Champion wrote:
> Agreed - but in particular, I think that the 1.6 blockers in Trac are
> too big. They've been blocking 1.6 for years, and I think we're to the
> point now where 1.6 is more important than those particular issues. I
> think that we
* On 22 Nov 2015, Kevin J. McCarthy wrote:
> > I think we could relegate the even/odd versioning to history, apply a
> > 1.6 tag as soon as we clear all in-flight bugfix patches, and continue
> > with only one tagged series from there. (Development would simply be
> > untagged.)
>
> I believe we
[moving this to its own thread]
On Sun, Nov 22, 2015 at 03:09:39PM -0600, David Champion wrote:
> * On 22 Nov 2015, Kevin J. McCarthy wrote:
> > Personally, and I haven't discussed this with the other committers yet,
> > I would like to release a 1.5.25 around February and try for a 1.6.0
> > Aug
28 matches
Mail list logo
