headers
Mike Miller | 3 May 2010 17:28
Picon

Re: Request for changes to method of operation

On Mon, 3 May 2010, Bret Busby wrote:

> Also, similarly, when the messages are listed in their respective 
> folders, if the timestamp displayed for each message, could be converted 
> ito either UTC time, or, the user's timezone time (but, and, 
> importantly, without affecting the timestamp as displayed in the message 
> header, which shows the timezone of the computer from which the message 
> was sent, when viewing each message), in the listing of messages, it 
> would make viewing the lists of messages, more user-friendly.
>
> An example of the apparent chaotic (from the displayed message times) 
> listing of messages, is shown in the attached screenshot image (I have 
> attached it - whether this mailing list will strip or retain the 
> attachment, I do not as yet know).
>
> Thus, that requested change would also make the software, more 
> user-friendly.
>
> Thank you in anticipation.

I see that you are from Australia, so you have more problems than most of 
us.  I get messages from Australia that say they were sent "Tomorrow".

I think what we need is an option to display "local date" in the index. 
Before recommending this I decided to look in the setup configuration and 
found this:

   [ Message Index Preferences ]
       [ ]  Auto Open Next Unread
       [ ]  Continue NextNew Without Confirming
(Continue reading)

Permalink | Reply |
headers
Mike Miller | 3 May 2010 17:34
Picon

bug in PREFDATETIME

In the help section for "Index Format" under Setup Configuration, I see 
this option:

   PREFDATETIME
       This token represents the date and time at which the message was
       sent, according to the "Date" header field. It is the preferred
       date and time representation for the current locale. Internally it
       uses the %c version of the time from the strftime routine.

On my system (Ubuntu 9.10), I see this:

$ date +%c
Mon 03 May 2010 10:14:15 AM CDT

When I use PREFDATETIME in the Index Format, it does have that format, but 
every date begins with "Sun" (Sunday) instead of the correct day of the 
week.

If there is a bug list, I can submit there, but I don't know where that 
list is.

Mike
Permalink | Reply |
headers
Eduardo Chappa | 4 May 2010 04:30

Re: bug in PREFDATETIME

On Mon, 3 May 2010, Mike Miller wrote:

MM> When I use PREFDATETIME in the Index Format, it does have that format, 
MM> but every date begins with "Sun" (Sunday) instead of the correct day 
MM> of the week.

That's because in your life every day is a sunday :).

Yes, you are right. There is a missing line in the date_str function. I 
just posted a patch in my page that adds this missing line.

Patch at http://staff.washington.edu/chappa/alpine/info/preftimebug.html

--

-- 
Eduardo
http://staff.washington.edu/chappa/alpine/
Permalink | Reply |
headers
Mike Miller | 4 May 2010 05:01
Picon

Re: bug in PREFDATETIME

On Mon, 3 May 2010, Eduardo Chappa wrote:

> On Mon, 3 May 2010, Mike Miller wrote:
>
> MM> When I use PREFDATETIME in the Index Format, it does have that format,
> MM> but every date begins with "Sun" (Sunday) instead of the correct day
> MM> of the week.
>
> That's because in your life every day is a sunday :).
>
> Yes, you are right. There is a missing line in the date_str function. I
> just posted a patch in my page that adds this missing line.
>
> Patch at http://staff.washington.edu/chappa/alpine/info/preftimebug.html

Muchas gracias, Eduardo.  (We speak mostly Spanish around the house 
because my wife is from Ecuador and we want our daughter to be bilingual.)

Do we have to tell them here on LaunchPad?:

https://bugs.launchpad.net/ubuntu/+source/alpine/+bug/574671

Mike
Permalink | Reply |
headers
Eduardo Chappa | 7 May 2010 23:44

Re: bug in PREFDATETIME

On Mon, 3 May 2010, Mike Miller wrote:

MM> Do we have to tell them here on LaunchPad?:

That's up to you. Asheesh is already a list member, so he is probably 
aware of the solution. In any case, there is another problem with the 
PREDTIME family of tokens, which is that no space is allocated for it in 
the screen. My patch now allocates enough space for each token to be 
displayed on the screen. The patch is available at

http://staff.washington.edu/chappa/alpine/info/preftimebug.html

--

-- 
Eduardo
http://staff.washington.edu/chappa/alpine/
Permalink | Reply |
headers
Mike Miller | 3 May 2010 18:05
Picon

Re: Request for changes to method of operation

On Mon, 3 May 2010, Mike Miller wrote:

> I discovered that I prefer this to the SMARTDATETIME24 that I had been 
> using in "Index Format":
>
> DAYOFWEEKABBREV(3) DATEISO(10) TIME24(5)
>
> Now my message index shows your message date like this...
>
> Mon 2010-05-03 00:11

FYI, this is what I'm using in the message index now:

ATT STATUS MSGNO TEXT:" " DAYOFWEEKABBREV(3) DATEISO(10) TIME24(6) FROMORTO(28%) SIZENARROW SUBJKEY(72%)

I added "TEXT" and changed TIME24(5) to TIME24(6) to put an extra space on 
either side of the data fields.  I almost always use an xterm that is 206 
characters across, so this works for me, but it is not compact.

Mike
Permalink | Reply |
headers
Mike Miller | 3 May 2010 23:42
Picon

Re: Request for changes to method of operation

On Mon, 3 May 2010, Mike Miller wrote:

> On Mon, 3 May 2010, Mike Miller wrote:
>
>> I discovered that I prefer this to the SMARTDATETIME24 that I had been 
>> using in "Index Format":
>> 
>> DAYOFWEEKABBREV(3) DATEISO(10) TIME24(5)
>> 
>> Now my message index shows your message date like this...
>> 
>> Mon 2010-05-03 00:11
>
> FYI, this is what I'm using in the message index now:
>
> ATT STATUS MSGNO TEXT:" " DAYOFWEEKABBREV(3) DATEISO(10) TIME24(6) FROMORTO(28%) SIZENARROW SUBJKEY(72%)
>
> I added "TEXT" and changed TIME24(5) to TIME24(6) to put an extra space 
> on either side of the data fields.  I almost always use an xterm that is 
> 206 characters across, so this works for me, but it is not compact.

Well, I changed my mind about that one too because I really like seeing 
the month instead of a number (e.g., Apr instead of 04), so I thought I 
would like "DAYDATE" because it does a format like "Sat, 23 Oct 1998", but 
I didn't like it because the date is shorter for the first 9 days of every 
month which looks a little messy, so I thought I'd build my own and I did 
it this way:

ATT STATUS MSGNO TEXT:" " DAYOFWEEKABBREV(3) DAY2DIGIT MONTHABBREV YEAR TIME24(6) FROMORTO(28%)
SIZENARROW SUBJKEY(72%)
(Continue reading)

Permalink | Reply |
headers
Benjamin R. Haskell | 4 May 2010 00:58
Favicon

Re: Request for changes to method of operation

On Mon, 3 May 2010, Mike Miller wrote:

> On Mon, 3 May 2010, Mike Miller wrote:
> 
> > On Mon, 3 May 2010, Mike Miller wrote:
> > 
> > > I discovered that I prefer this to the SMARTDATETIME24 that I had 
> > > been using in "Index Format":
> > > 
> > > DAYOFWEEKABBREV(3) DATEISO(10) TIME24(5)
> > > 
> > > Now my message index shows your message date like this...
> > > 
> > > Mon 2010-05-03 00:11
> > 
> > FYI, this is what I'm using in the message index now:
> > 
> > ATT STATUS MSGNO TEXT:" " DAYOFWEEKABBREV(3) DATEISO(10) TIME24(6) 
> > FROMORTO(28%) SIZENARROW SUBJKEY(72%)
> > 
> > I added "TEXT" and changed TIME24(5) to TIME24(6) to put an extra 
> > space on either side of the data fields.  I almost always use an 
> > xterm that is 206 characters across, so this works for me, but it is 
> > not compact.
> 
> 
> Well, I changed my mind about that one too because I really like 
> seeing the month instead of a number (e.g., Apr instead of 04), so I 
> thought I would like "DAYDATE" because it does a format like "Sat, 23 
> Oct 1998", but I didn't like it because the date is shorter for the
(Continue reading)

Permalink | Reply |
headers
Benjamin R. Haskell | 4 May 2010 01:02
Favicon

Re: Request for changes to method of operation

On Mon, 3 May 2010, Benjamin R. Haskell wrote:

> [...]
> It'd also be nice to see strftime-style dates, and maybe the index 
> format itself could specify whether to convert to localtime:
> 
> %{DATE:%Y-%m-%d %H:%M}       -> 2010-05-03 18:50
> %{LOCALDATE:%Y-%m-%d %H:%M}  -> 2010-05-03 22:50 (I'm in -0400 right now)

%{DATE:%Y-%m-%d %H:%M}       -> 2010-05-03 22:50
%{LOCALDATE:%Y-%m-%d %H:%M}  -> 2010-05-03 18:50 (I'm in -0400 right now)

Oops, reversed those.

And maybe DATE and HEADERDATE could be synonyms, along with 
LOCALDATE+SENDERDATE, or others.

--

-- 
Best,
Ben
Permalink | Reply |

Gmane