On Sat, May 13, 2000 at 11:37:12PM -0400, David T-G typed:
> As you've seen, the fix is to get a new mutt ...
yep ...
> ... but my vague recollection is that 0.95.4i already had the mutt_dotlock
> program so that mutt itself could run without special perms -- and so
I tried compiling a later v
Suresh --
...and then Suresh Ramasubramanian said...
% On Sat, May 13, 2000 at 11:37:12PM -0400, David T-G typed:
%
% > ... but my vague recollection is that 0.95.4i already had the mutt_dotlock
% > program so that mutt itself could run without special perms -- and so
%
% I tried compiling a la
Mrinal --
...and then Mrinal Kalakrishnan said...
% Hi,
%
% My friend has a problem with an old Mutt version (0.95.4i), our
% timezone is +0530, but it displays it as +051800.
%
% Other than updating mutt, is there any fix for this?
As you've seen, the fix is to get a new mutt ...
%
% -
Mrinal Kalakrishnan saw fit to inform me that:
> My friend has a problem with an old Mutt version (0.95.4i), our
> timezone is +0530, but it displays it as +051800.
> Other than updating mutt, is there any fix for this?
It is a mutt bug afaict. The mutt changelog has a note from Roessler to
tha
Hi,
My friend has a problem with an old Mutt version (0.95.4i), our
timezone is +0530, but it displays it as +051800.
Other than updating mutt, is there any fix for this?
- Forwarded message -
From: Suresh Ramasubramanian <[EMAIL PROTECTED]>
Subject: [LIH] HELP: Weird date format in mu
