I'm having trouble figuring out the date format for my
attribution line. I want it to show as or
something a lot shorter than the default. Can someone provide
this for me?
thanks,
jc
--
Jim Breton <[EMAIL PROTECTED]> wrote on Fri, 25 Feb 2000:
> Is there a way (other than modifying the source) to change the format of
> the Date string put into messages I send?
You can't change the *format*, because that's more or less specifically
defined in the RFCs. However I wouldn't call ch
Jim Breton writes:
> Is there a way (other than modifying the source) to change the format of
> the Date string put into messages I send? I really just want to change
> the time zone and it looks like Mutt is writing this header (although I
> can't modify it when $edit_headers is set).
>
> Rathe
Lars Hecking <[EMAIL PROTECTED]>:
> > Rather than EST I would like to use GMT. My local machine is set to
> > EST and I know I could change that, but I'm wondering if there's a way
> > to change *just* mutt for this.
>
> Bourne shell:
>
> $ TZ=GMT mutt
>
> C shell:
>
> $ env TZ=GMT mutt
> And if you want the timezone to depend on which folder you're in, or
> who you're writing to, then you simply write a hook that ... calls
> mutt's putenv/setenv command, which doesn't exist, but could be
> created ...
Just like that builtin perl interpreter I envisioned, which could
rid mutt
At 07/11/01 10:16, Jeff Coppock wrote:
>I'm having trouble figuring out the date format for my
>attribution line. I want it to show as or
>something a lot shorter than the default. Can someone provide
>this for me?
I typed this command before sendin
Byrial Jensen [mutt-users] <16/07/01 09:56 +0200>:
> At 07/11/01 10:16, Jeff Coppock wrote:
> >I'm having trouble figuring out the date format for my
> >attribution line. I want it to show as or
> >something a lot shorter than the default. Can so
On 2001-07-16 at 09:56:48Z, Byrial Jensen wrote:
> 1) The time format is ambiguous because it doesn't include timezone
>information. As it is, it will use the origininal sender's timezone
>(the question was sent at 10:16 your local time). It would have
>been mine local time if I had us
I am trying to use Champion and Blackman's nice bash script,
which I have appended below, to assign different date formats
according to the age of the date.
I have tested each of the conditionals of this script and
it seems to work from the shell. However when I try to use it
from
* On 21 Nov 2011, von der Burg wrote:
>
> I am trying to use Champion and Blackman's nice bash script,
> which I have appended below, to assign different date formats
> according to the age of the date.
>
> I have tested each of the conditionals of this script and
> it seems to work
d this
year, or older messages:
set index_format='%4C %?X?%2X& ? %Z %?[1y?%\?[1d\?%[%H:%M] \&%[%d
%b]\?&%[%d/%m/%Y]? %-30.30L %s'
(should all be on one line).
The difference between the two date_conditional patches is, for example,
that my version applies the "to
On Mon, Nov 21, 2011 at 04:36:00PM -0600, David Champion wrote:
Caveats: I remember this coming up but I don't remember exactly when or
in what context. (If you have a URL where you got this I could double
check.)
The start of the thread is here:
http://marc.info/?l=mutt-users&m=1294265041212
Hi list,
I have
set date_format="%a %d %b %y"
set index_format"%4C %c %D %s"
which is ok for the index. Now when I reply to a message, I would like
to have the attribution specially set, something like (in French) this:
Le mardi 18 août 2009, John Dow (j...@example.com) a écrit :
So full day n
Hi!
I'm using mutt 1.3.19i. When I reply to a mail, the mail is attributed
like this:
| So sprach Some1 am Sat, May 26, 2001 at 05:37:09PM -0500:
This is because I've got in my .muttrc:
set attribution = "So sprach %n am %d:"
When I also have
set locale=de_DE
in my .muttr
this:
LANG: de
LANGUAGE: de_DE:de
LC_COLLATE:de_DE
LC_CTYPE: de_DE
LC_MESSAGES: de_DE
LC_MONETARY: de_DE
LC_NUMERIC:de_DE
LC_TIME: de_DE
This also happens with %x. With 'set locale=de_DE' in my .muttrc, it
prints "17.07.2001" which is the c
Hi!
I would like to change my index to look instead of:
L 66 Feb 22 To mutt-users@mutt. ( 0.2K) The Subject goes here...
to:
L 66 Feb 22 2002 To mutt-users@mutt. ( 0.2K) The Subject goes here...
I read the %d uses the $date_format, but the actual date_format does not
matches the existing in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, August 19 at 01:06 PM, quoth steve:
>set date_format="%a %d %b %y"
>set index_format"%4C %c %D %s"
>
>which is ok for the index. Now when I reply to a message, I would like
>to have the attribution specially set, something like (in Fren
On Thu, 19. Jul 2001 um 05:45:41PM +0200, Alexander Skwar wrote:
> This also happens with %x. With 'set locale=de_DE' in my .muttrc, it
> prints "17.07.2001" which is the correct date format for my locale.
> However, if I remove %x, it prints "07/17/01"
Quoting David Collantes <[EMAIL PROTECTED]> [25 Feb-02 15:20]:
> I would like to change my index to look instead of:
>
> L 66 Feb 22 To mutt-users@mutt. ( 0.2K) The Subject goes here...
>
> to:
>
> L 66 Feb 22 2002 To mutt-users@mutt. ( 0.2K) The Subject goes here...
>
> I read the %d uses t
On [25/02/02] 14:57, David Collantes wrote:
>
> L 66 Feb 22 To mutt-users@mutt. ( 0.2K) The Subject goes here...
>
> to:
>
> L 66 Feb 22 2002 To mutt-users@mutt. ( 0.2K) The Subject goes here...
in 'index_format' use %d (or %D if you prefer local time zone) for
the date (instead of default '
On Mon, Feb 25, 2002 at 03:36:33PM -0500, darren chamberlain wrote:
[... SNIP ...]
> > change from:
> >
> > L 66 Feb 22 To mutt-users@mutt. ( 0.2K) The Subject goes here...
> >
> > to:
> >
> > L 66 Feb 22 2002 To mutt-users@mutt. ( 0.2K) The Subject goes here...
> >
> > I read the %d uses th
Le mercredi 19 août 2009, Kyle Wheeler (kyle-m...@memoryhole.net) a écrit :
> On Wednesday, August 19 at 01:06 PM, quoth steve:
> >set date_format="%a %d %b %y"
> >set index_format"%4C %c %D %s"
> >
> >which is ok for the index. Now when I reply to a message, I would like
> >to have the attributio
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 for
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
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 ...
%
% -
27 matches
Mail list logo
