On Tue, Jan 15, 2002 at 04:23:34PM -0500, Jeremy Blosser wrote:
> On Jan 15, Maciej Kalisiak [[EMAIL PROTECTED]] wrote:
> > Is it possible in mutt to change the parent of a message in a thread?
> > And then have it be written to the mailbox so that the message keeps the
> > new parent in subsequen
On Jan 15, Maciej Kalisiak [[EMAIL PROTECTED]] wrote:
> On Tue, Jan 15, 2002 at 04:23:34PM -0500, Jeremy Blosser wrote:
> > On Jan 15, Maciej Kalisiak [[EMAIL PROTECTED]] wrote:
> > > Is it possible in mutt to change the parent of a message in a thread?
> > > And then have it be written to the mai
Jeremy Blosser wrote:
>
> Er, no, it is not included in vanilla mutt. Your mutt must not be
> quite as vanilla as you think. ;)
perhaps it's the debian mutt? that patch appears to be in the latest
unstable version (with a number of others).
w
On Tue, Jan 15, 2002 at 06:16:47PM -0500, Jeremy Blosser wrote:
> > Oh! I find that "&" seems to be part of the vanilla distribution of
> > mutt (i.e., its in my help menu, and it works), at least in 1.3.25.
> > Excellent. Or is that patch you mention somehow different?
>
> Er, no, it is not incl
Maciej Kalisiak wrote:
>
> I have no idea which one provides the "&" and "#" though. If it turns
> out to be the patch you mentioned then let me know, and I'll file a
> bug with the patch author.
not all the patches show up in mutt -V output.
do: apt-get source mutt
and look in mutt-1.3.25/debi
On Jan 15, Will Yardley [[EMAIL PROTECTED]] wrote:
> Maciej Kalisiak wrote:
> > I have no idea which one provides the "&" and "#" though. If it turns
> > out to be the patch you mentioned then let me know, and I'll file a
> > bug with the patch author.
>
> not all the patches show up in mutt -V o
Hi Maciej,
> Oh! I find that "&" seems to be part of the vanilla distribution of
> mutt (i.e., its in my help menu, and it works), at least in 1.3.25.
> Excellent. Or is that patch you mention somehow different?
I guess you're using Debian.
> Anyhow, there seems to be a glaring but minor bug wi
Jeremy Blosser wrote:
> > ...
> > the behavior you describe is from 000_patch-1.3.25.cd.edit_threads.9
> ...and the current version of that same patch is 9.1.
> I have no idea if that version fixes your bug; Cedric will probably reply
> to this thread when he sees it.
Yes, this was fixed in 9.
