#3478: Naming the gnupg signature filename instead of "noname" filename
--+--
Reporter: schplaf | Owner: mutt-dev
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: mutt |Version: 1
On Sun, Oct 06, 2013 at 01:30:09PM -0500, Derek Martin wrote:
> On Sun, Oct 06, 2013 at 11:01:20AM -0700, Alexander Gattin wrote:
> > If my system is not using DNS for local name resolution, then I
> > can still use /etc/network/interfaces (or whatever) scripts to
> > edit /etc/resolv.conf just for
On Sun, Oct 06, 2013 at 12:01:05PM -0700, Alexander Gattin wrote:
> You have several hostnames or A records or domain names or whatever.
> Then you have `hostname`, which is configured in kernel, at least in
> Linux (cat /proc/sys/kernel/hostname), which may match some A
> record, or not. Or match
On Sun, Oct 06, 2013 at 12:02:24PM -0700, Alexander Gattin wrote:
> On Sun, Oct 06, 2013 at 11:20:15AM -0700,
> Alexander Gattin wrote:
> > On Sun, Oct 06, 2013 at 01:15:26PM -0500, Derek
> > Martin wrote:
> > > parsing /etc/resolv.conf directly can be wrong,
>
> No solution is ideal here.
I don'
On Sun, Oct 06, 2013 at 11:20:15AM -0700,
Alexander Gattin wrote:
> On Sun, Oct 06, 2013 at 01:15:26PM -0500, Derek
> Martin wrote:
> > parsing /etc/resolv.conf directly can be wrong,
No solution is ideal here.
You've added a lot of comments to trac ticket
3298. There's one problem, though:
> Not
On Sun, Oct 06, 2013 at 01:30:09PM -0500, Derek
Martin wrote:
> > My system has several IP addresses and several
> > hostnames (depending on interface/network).
>
> Wrong, it has exactly one hostname, as does
> every TCP/IP-networked host. It may have
> several domain names corresponding to the
On Sun, Oct 06, 2013 at 11:20:15AM -0700, Alexander Gattin wrote:
> On Sun, Oct 06, 2013 at 01:15:26PM -0500, Derek
> Martin wrote:
> Yes, it doesn't break, it just returns wrong
> domain.
Let me be very clear here: This patch CAN NOT produce a domain which
is wrong, in the sense that any domain
#3649: Sorting by 'To: ' does not work right
---+--
Reporter: grarpamp | Owner: mutt-dev
Type: defect| Status: new
Priority: major | Milestone: 1.6
Component: mutt |Version: 1.5.21
Resolution:| Keyw
On Sun, Oct 06, 2013 at 11:20:15AM -0700, Alexander Gattin wrote:
> > It doesn't break anything, because if you don't
> > get the domain you expect,
>
> Yes, it doesn't break, it just returns wrong
> domain.
If you set it in your muttrc, it will ALWAYS be right. If you fix
your /etc/hosts misco
On Sun, Oct 06, 2013 at 11:01:20AM -0700, Alexander Gattin wrote:
> On Fri, Oct 04, 2013 at 01:06:35PM -0500, Derek
> Martin wrote:
> If my system is not using DNS for local name
> resolution, then I can still use
> /etc/network/interfaces (or whatever) scripts to
> edit /etc/resolv.conf just for m
On Sun, Oct 06, 2013 at 01:15:26PM -0500, Derek
Martin wrote:
> On Sun, Oct 06, 2013 at 11:01:20AM -0700,
> Alexander Gattin wrote:
> > On Fri, Oct 04, 2013 at 01:06:35PM -0500, Derek
> > Martin wrote:
> > On the other hand, your patch breaks some of
> > setups that do use DNS.
>
> It doesn't brea
On Sun, Oct 06, 2013 at 11:01:20AM -0700, Alexander Gattin wrote:
> On Fri, Oct 04, 2013 at 01:06:35PM -0500, Derek
> Martin wrote:
> > Even if the patch was complete garbage, the
> > point is there was never any discussion from the
> > devs as to WHY. It was completely ignored for
> > three and a
On Sun, Oct 06, 2013 at 11:01:20AM -0700, Alexander Gattin wrote:
> On Fri, Oct 04, 2013 at 01:06:35PM -0500, Derek
> Martin wrote:
> On the other hand, your patch breaks some of
> setups that do use DNS.
It doesn't break anything, because if you don't get the domain you
expect, you simply set it
On Fri, Oct 04, 2013 at 01:06:35PM -0500, Derek
Martin wrote:
> Even if the patch was complete garbage, the
> point is there was never any discussion from the
> devs as to WHY. It was completely ignored for
> three and a half years.
Yes, ignoring your patch because of
technical/stylistic problems
#3298: Mutt's way to get the FQDN is broken
-+--
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: reopened
Priority: major | Milestone:
Component: mutt|Version: 1.5.20
Resolution: | Keywords:
---
#3298: Mutt's way to get the FQDN is broken
-+--
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: reopened
Priority: major | Milestone:
Component: mutt|Version: 1.5.20
Resolution: | Keywords:
---
#3298: Mutt's way to get the FQDN is broken
-+--
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: reopened
Priority: major | Milestone:
Component: mutt|Version: 1.5.20
Resolution: | Keywords:
---
changeset: 6311:24bb691dcde7
user: nihilh...@gmail.com
date: Sun Oct 06 09:31:17 2013 -0700
link: http://dev.mutt.org/hg/mutt/rev/24bb691dcde7
include for definition 'true'
closes #3642
diffs (11 lines):
diff -r 035306822940 -r 24bb691dcde7 crypt-gpgme.c
--- a/crypt-gpgme.c
#3642: Missing header when building against S-Lang
--+--
Reporter: baskerville | Owner: mutt-dev
Type: defect | Status: closed
Priority: major| Milestone:
Component: build|Version:
Resolution: fixed
#3487: Display problems for mbox-files > 2GiB
+--
Reporter: antonio@… | Owner: me
Type: defect | Status: assigned
Priority: trivial| Milestone:
Component: mutt |Version: 1.5.21
Resolution: | Key
#3648: TLS-received emails are missorted when sorting by date-received
+--
Reporter: hobarrera | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: browser|Version: 1.5.21
Resol
#3649: Sorting by 'To: ' does not work right
---+--
Reporter: grarpamp | Owner: mutt-dev
Type: defect| Status: new
Priority: major | Milestone: 1.6
Component: mutt |Version: 1.5.21
Resolution:| Keyw
On Tue, Jul 16, 2013 at 03:17:36PM -0700, Kevin J. McCarthy wrote:
This patch "fixes" the segfault by reverting to the old behavior of
using mutt_save_attachment() for the compose/send case when viewing text
attachments in the pager.
Whether this is the correct thing to do is another discussion.
#3478: Naming the gnupg signature filename instead of "noname" filename
--+--
Reporter: schplaf | Owner: mutt-dev
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: mutt |Version: 1
changeset: 6310:035306822940
user: Kevin McCarthy
date: Sat Oct 05 15:57:49 2013 +0800
link: http://dev.mutt.org/hg/mutt/rev/035306822940
Fix segfault when viewing text attachments in compose menu. (closes #3644)
The segfault was introduced in changeset b9f9e3147eb4. Since decod
#3644: segmentation fault when viewing an application/x-sh attachment
---+
Reporter: vinc17| Owner: me
Type: defect| Status: closed
Priority: critical | Milestone:
Component: mutt |Version:
Resolution: fixed |
On Sat, Oct 05, 2013 at 08:35:56PM -0400, Aaron Schrab wrote:
Here's a new version of that first patch adjusted to apply after the
other one.
Applied. http://dev.mutt.org/trac/changeset/6309
changeset: 6309:6bcde5f1c7a7
user: Aaron Schrab
date: Sun Oct 06 14:32:45 2013 +
link: http://dev.mutt.org/hg/mutt/rev/6bcde5f1c7a7
Ensure that BUFFER variables are initialized to prevent later attempts
to traverse an uninitialized pointer.
diffs (64 lines):
diff -r 132861c8b
At 19:28 + 05 Oct 2013, Michael Elkins wrote:
On Thu, Aug 22, 2013 at 03:10:36PM -0400, Aaron Schrab wrote:
Indeed, I'd already completed the following patch before seeing this
message. It replaces use of memset with mutt_buffer_init. Even if
there's a later move to do more in another in
Michael Elkins wrote:
> Applied. http://dev.mutt.org/trac/changeset/6308
Just to make sure it doesn't slip through the cracks, this
was actually a two-part patch. Aaron's first patch in email
20130822190611.ga14...@pug.qqx.org added calls to mutt_buffer_init() for
some err variables in addition
30 matches
Mail list logo
