Re: [Evolution] Annoyance with next message order

2015-03-19 Thread David Woodhouse
On Thu, 2015-03-19 at 18:05 +, Pete Biggs wrote:
  
  Next daft newbie-user question... how do I make that the default 
  for 
  *all* folders instead of having to change them one by one?
 
 I don't know about that, but you can save a custom view (including 
 sort order) by setting the folder how you want and then doing View -
 Current View - Save view.   Then it's reasonably trivial to set the 
 correct view of a folder when you first visit it (and that will 
 remain until it's changed).

Program received signal SIGSEGV, Segmentation fault.
0x0035f13bbc63 in gal_view_clone (view=0x1c00) at gal-view.c:241
241 g_return_val_if_fail (GAL_IS_VIEW (view), NULL);

Hm, suppose I'd best file a bug for that. In the morning :)

  In both of those cases, surely we're better off sorting by 
  Received  date not Sent? Should we make it the default?
  
 
 Certainly I think the Received date is the better one to sort by, 
 although YMMV. But I thought the default was no sorting - i.e. the 
 messages are displayed in the order they are stored.  In general 
 that's the received order, but not when you start moving messages 
 around.  But I may be wrong about that - it's a long time since I 
 used a vanilla install.

Yeah, likewise :)

-- 
dwmw2


smime.p7s
Description: S/MIME cryptographic signature
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Craig
On Thu, 2015-03-19 at 18:05 +, Pete Biggs wrote:
 I don't know about that, but you can save a custom view (including sort
 order) by setting the folder how you want and then doing View - Current
 View - Save view.   Then it's reasonably trivial to set the correct
 view of a folder when you first visit it (and that will remain until
 it's changed).

Thanks Pete, this answers a question I hadn't asked yet.

However, when I did this my computer exploded. OK, not quite, but I had
the same reaction as if it had. This is what happened:

1) I sorted my in box by date (having long ago done things like chosen
columns, etc.) by clicking on the Date column header.
2) I clicked View | Current View | Save Custom View.
3) Named it In Default (without the quotes).
4) Clicked the Save button.
5) Then went to click the Label column header so that it went back to
how I prefer to have my *in* box sorted. (The point of creating and
saving this custom view is to apply it to other mail boxes where I don't
label messages.)
6) There was no response. So I clicked on the Date column header to
sort by that. The Date column DISAPPEARED COMPLETELY! WTF?!
7) Right-clicked on any column header and selected Add a Column 
8) Up popped a box with a number of column names listed, including
Date.
9) I dragged the Date button to the position I wanted it between two
other columns and dropped it.
10) Nothing appeared.
11) Clicked the Close button on the list of possible column names to
add.
12) So I then did what I've done before: right-click on any column
header, click on Customise Current View.
13) Click the Fields Shown ... button.
14) Now the Date field/column is no longer even listed as a possible
field/column to add any more.

With rising panic and great trepidation I closed and opened Evolution.
Date column still not there, but I essentially repeated steps 12 and 13
and everything seems to be back to normal, and the Date column (which
had also somehow been removed from other, but not all, mail boxes) is
back. However, now I'm afraid to save a custom view, even though it's
exactly what I have been looking for.

Evolution 3.10.4 under Xfce 4.10 on Xubuntu 14.04.2, in case anyone
wants to follow up or tell me what I did wrong to cause such weirdness.
Thanks.


Craig




___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Patrick O'Callaghan
On Wed, 2015-03-18 at 15:00 -0400, Paul Smith wrote:
 Hi all.  This has bugged me for years but never enough to complain about
 it (until now, I guess :)).  I wonder if it's just me, or just my setup,
 or what.  I'm currently using Evolution 3.12.10 but I've seen this for a
 number of releases (maybe always?)
 
 I order my folders by Received (Ascending) so my newest messages are at
 the bottom, and I enable threading.  So suppose I get 15 new messages
 and 10 of them are in the same thread.  I select the first one in the
 thread, read it, press ^D to delete it... and at least 50% of the time
 instead of automatically selecting the next message in the thread
 according to the ordering shown in my folder, Evo jumps over the next
 message (or two, or whatever) and selects another one inside the thread.
 When this happens, it never goes back to the previous messages in the
 thread; if I keep deleting it will get to the last message in the
 thread, delete it, then go to the next message after the thread.
 
 This is really surprising, especially because often the skipped messages
 have context needed to understand the selected message.  Also, if I back
 up to the first message that was skipped and delete that one, Evo will
 jump back down to that same message again, skipping the intermediate
 ones.
 
 It seems like the go to next message on delete algorithm is not using
 the same ordering as the display threaded messages in a folder
 algorithm.
 
 Does this happen to anyone else?  Is it a known issue?  Should I file an
 enhancement request about it?
 
 Also, what is the ordering that go to next message on delete actually
 uses?  I might even be willing to choose the same order for my display,
 if I knew what it was.

It's never been completely clear to me what these ordering really mean
when combined with threading. I have folders ordered by Received
(Descending, i.e. the oldest thread first) and this problem doesn't
happen to me. I suspect the problem has to do with wanting the most
recent thread (i.e. the thread with the most recent message) at the top
but the messages within each thread go from oldest to newest. I'm not
saying the behaviour you see isn't a bug, but it may only manifest with
this particular configuration. If you feel it is a bug then you should
consider reporting it to BZ.

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread David Woodhouse
On Thu, 2015-03-19 at 16:44 +, Patrick O'Callaghan wrote:
 On Thu, 2015-03-19 at 08:21 -0400, Paul Smith wrote:
   I have folders ordered by Received (Descending, i.e. the oldest
  thread
   first) and this problem doesn't happen to me. I suspect the 
   problem has to do with wanting the most recent thread (i.e. the 
   thread with the most recent message) at the top but the messages 
   within each thread go from oldest to newest.
  
  That's why I order my mail Ascending instead of Descending, with 
  the newest mail at the BOTTOM of the folder.  Although it's a bit 
  weird at first, this seems the most natural to me; it aligns the 
  inter-thread order with the intra-thread order: both go from 
  oldest at the top to newest at the bottom.
  
 
 I misunderstood you. As I said, I also have oldest first (both 
 threads and messages) yet I don't see the behaviour you describe. 
 However I seem to have a custom sort order which I must have 
 configured a long time ago and forgotten about. I can't find an 
 obvious way to see what it's set to.

I don't have a custom sort order, and I also see the saner behaviour 
you describe, Patrick. If I delete a message, focus moves to the next 
message below it in the display. Not the next newer message in the 
mailbix which may be elsewhere in the threaded display.

My main issue with the sorting, FWIW, is the fact that we sort on the 
Date: header and not the time the message was actually *delivered*. So 
when we get a misdated mail from the future, it sits as the newest 
message in the mailbox until the world finally catches up with it. Or 
we get annoyed and delete it.

-- 
dwmw2


smime.p7s
Description: S/MIME cryptographic signature
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Pete Biggs

 
 My main issue with the sorting, FWIW, is the fact that we sort on the 
 Date: header and not the time the message was actually *delivered*. So 
 when we get a misdated mail from the future, it sits as the newest 
 message in the mailbox until the world finally catches up with it. Or 
 we get annoyed and delete it.

Add a column called Recieved (which is the date received) and sort on
that.

P.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread David Woodhouse
On Thu, 2015-03-19 at 17:08 +, Pete Biggs wrote:
 On Thu, 2015-03-19 at 17:05 +, Pete Biggs wrote:
   
   My main issue with the sorting, FWIW, is the fact that we sort 
   on the  Date: header and not the time the message was actually 
   *delivered*. So  when we get a misdated mail from the future, it 
   sits as the newest  message in the mailbox until the world 
   finally catches up with it. Or  we get annoyed and delete it.
  
  Add a column called Recieved (which is the date received) and 
  sort on that.
 
 Actually, you don't need to add the column - just right click on the 
 header bar (i.e. the Subject or From header) and got to Sort By 
 and select Received.

Next daft newbie-user question... how do I make that the default for 
*all* folders instead of having to change them one by one?

Other than committing a change to Evolution... or come to think of it, 
shouldn't we do that?

There are two cases when 'Sent' is different from 'Received' by more 
than an irrelevant few seconds:

There's the case I mentioned, of spam or otherwise misdated mail.

And there's the case where a mail is delayed in transit by greylisting 
or some other mishap, and then if you are viewing in 'Sent' sort order 
and looking below the other mails you've already read, you might not 
see it. That actually happens to me more often than the spam with bad 
dates in the future, in fact. And probably *actually* happens more 
often than I know! :)


In both of those cases, surely we're better off sorting by Received 
date not Sent? Should we make it the default?

-- 
dwmw2


smime.p7s
Description: S/MIME cryptographic signature
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread David Woodhouse
On Thu, 2015-03-19 at 17:08 +, Pete Biggs wrote:
 On Thu, 2015-03-19 at 17:05 +, Pete Biggs wrote:
   
   My main issue with the sorting, FWIW, is the fact that we sort 
   on the  Date: header and not the time the message was actually 
   *delivered*. So  when we get a misdated mail from the future, it 
   sits as the newest  message in the mailbox until the world 
   finally catches up with it. Or  we get annoyed and delete it.
  
  Add a column called Recieved (which is the date received) and 
  sort on that.
 
 Actually, you don't need to add the column - just right click on the 
 header bar (i.e. the Subject or From header) and got to Sort By 
 and select Received.

Ooh, thank you. I don't remember that being available last time I 
looked.

-- 
dwmw2


smime.p7s
Description: S/MIME cryptographic signature
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Paul Smith
On Thu, 2015-03-19 at 16:56 +, David Woodhouse wrote:
 I don't have a custom sort order, and I also see the saner behaviour 
 you describe, Patrick. If I delete a message, focus moves to the next 
 message below it in the display. Not the next newer message in the 
 mailbix which may be elsewhere in the threaded display.

To be clear this doesn't happen to me all the time, but it does happen
probably 30-40% of the time when I have a longer thread of unread mail.
My suspicion is that when it happens, there's something about the
message that causes the thread display order and the next-message
order to be out of alignment.  It would be interesting to know what the
next-message code uses for ordering.

I could try pre-emptively saving email threads to an mbox file in case
it happens.  Or maybe I can undelete the message and reproduce the
behavior.  I'll see if I can get a better handle on it.

I guess for completeness I should say I'm using IMAP mailboxes, although
I doubt it makes a difference.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Pete Biggs
On Thu, 2015-03-19 at 17:05 +, Pete Biggs wrote:
  
  My main issue with the sorting, FWIW, is the fact that we sort on the 
  Date: header and not the time the message was actually *delivered*. So 
  when we get a misdated mail from the future, it sits as the newest 
  message in the mailbox until the world finally catches up with it. Or 
  we get annoyed and delete it.
 
 Add a column called Recieved (which is the date received) and sort on
 that.

Actually, you don't need to add the column - just right click on the
header bar (i.e. the Subject or From header) and got to Sort By and
select Received.

P. 

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Pete Biggs

 
 Next daft newbie-user question... how do I make that the default for 
 *all* folders instead of having to change them one by one?

I don't know about that, but you can save a custom view (including sort
order) by setting the folder how you want and then doing View - Current
View - Save view.   Then it's reasonably trivial to set the correct
view of a folder when you first visit it (and that will remain until
it's changed).

 
 In both of those cases, surely we're better off sorting by Received 
 date not Sent? Should we make it the default?
 

Certainly I think the Received date is the better one to sort by,
although YMMV. But I thought the default was no sorting - i.e. the
messages are displayed in the order they are stored.  In general that's
the received order, but not when you start moving messages around.  But
I may be wrong about that - it's a long time since I used a vanilla
install!

P.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Paul Smith
On Thu, 2015-03-19 at 11:31 +, Patrick O'Callaghan wrote:
 It's never been completely clear to me what these ordering really mean
 when combined with threading.

I'm not so worried about the order in which different threads are
displayed.  But within a single thread it seems to me that whatever
order is shown in the folder, should be the same order used by Evolution
to choose the next message to display when it automatically moves to the
next message (when the current message is deleted for example).

 I have folders ordered by Received (Descending, i.e. the oldest thread
 first) and this problem doesn't happen to me. I suspect the problem
 has to do with wanting the most recent thread (i.e. the thread with
 the most recent message) at the top but the messages within each
 thread go from oldest to newest.

That's why I order my mail Ascending instead of Descending, with the
newest mail at the BOTTOM of the folder.  Although it's a bit weird at
first, this seems the most natural to me; it aligns the inter-thread
order with the intra-thread order: both go from oldest at the top to
newest at the bottom.

Also, I like to read my email starting with the oldest new message and
going to the newest new message: if you sort Descending this doesn't
work because you read the oldest new message, which is at the end of the
new messages, then delete it, and Evo automatically chooses the next
message BELOW that in the list, which is the first message you already
read.  I want it to choose the next NEW message, which means it would
need to go UP in the folder.  Note this is a separate issue from the
threading order.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Patrick O'Callaghan
On Thu, 2015-03-19 at 17:11 +, David Woodhouse wrote:
 On Thu, 2015-03-19 at 17:08 +, Pete Biggs wrote:
  On Thu, 2015-03-19 at 17:05 +, Pete Biggs wrote:

My main issue with the sorting, FWIW, is the fact that we sort 
on the  Date: header and not the time the message was actually 
*delivered*. So  when we get a misdated mail from the future, it 
sits as the newest  message in the mailbox until the world 
finally catches up with it. Or  we get annoyed and delete it.
   
   Add a column called Recieved (which is the date received) and 
   sort on that.
  
  Actually, you don't need to add the column - just right click on the 
  header bar (i.e. the Subject or From header) and got to Sort By 
  and select Received.
 
 Ooh, thank you. I don't remember that being available last time I 
 looked.

IIRC it's been available for as long as I've used Evo, which is quite a
few years now.

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Patrick O'Callaghan
On Thu, 2015-03-19 at 13:20 -0400, Paul Smith wrote:
  I don't have a custom sort order, and I also see the saner
 behaviour 
  you describe, Patrick. If I delete a message, focus moves to the
 next 
  message below it in the display. Not the next newer message in the 
  mailbix which may be elsewhere in the threaded display.
 
 To be clear this doesn't happen to me all the time, but it does happen
 probably 30-40% of the time when I have a longer thread of unread
 mail.
 My suspicion is that when it happens, there's something about the
 message that causes the thread display order and the next-message
 order to be out of alignment.  It would be interesting to know what
 the
 next-message code uses for ordering.

It may also be affected by the In-Reply-To and References headers.

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Patrick O'Callaghan
On Thu, 2015-03-19 at 18:05 +, Pete Biggs wrote:
  Next daft newbie-user question... how do I make that the default
 for 
  *all* folders instead of having to change them one by one?
 
 I don't know about that, but you can save a custom view (including
 sort
 order) by setting the folder how you want and then doing View -
 Current
 View - Save view.   Then it's reasonably trivial to set the correct
 view of a folder when you first visit it (and that will remain until
 it's changed).

I can be certain but I do have a dim recollection of doing this in the
distant past, which is probably where my Custom sort order comes from.

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Left-click in text field grabs window to move

2015-03-19 Thread Emilio Recio
It seems to happen on many applications that rely on GTK. Thunderbird
does it from the tab bar, firefox doesn't do it anymore. It's especially
annoying in Eclipse (I have an expanded window, go and click on a
toolbar button, if I miss and click the blank part of the menu bar, it
picks the window up and un-maximizes it.) I am not sure why firefox
doesn't do it, but I imagine the point/click/drag is being subclassed
for other purposes.

-e

On 03/13/15 04:29, Florian Baumann wrote:
 Hello,

 so I have a rather strange and slightly annoying problem with the
 composer window of Evolution. Whenever I left-click in the text field,
 for example to select some text or just to set the cursor at some
 specific position, it grabs the window and moving the mouse moves the
 window, and I'm unable to select anything.
 If I left-click again, the window is dropped, and moving the mouse
 selects text.
 The exact behavior, especially if it selects text or not afterwards, is
 dependent upon the length of the left-click.

 What I also noticed, is that I can grab and move the window if I click
 the menu bar, or the menu icon bar. But there, the window is dropped
 again, if I let go of the left mouse button. So this seems like the
 intended behavior. The left-clicking and moving in the text field don't
 seem right to me.

 I'm using Xfce 4.12 on Arch Linux on two machines, both show this
 behavior.

 Thank you for your attention
 Florian

 ___
 evolution-list mailing list
 evolution-list@gnome.org
 To change your list options or unsubscribe, visit ...
 https://mail.gnome.org/mailman/listinfo/evolution-list


--

Thanks,
E. Recio

+-+
| E. Recio   | AIM: emrecio   |
| 833 Chestnut East; Ste 600 | Wrk: 215.503.2131  |
| Philadelphia, PA 19107 | Pgr: 877.656.1864  |
+-+

Never trust an operating system you don't have sources for. ;-)
-- Unknown source
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Annoyance with next message order

2015-03-19 Thread Patrick O'Callaghan
On Thu, 2015-03-19 at 08:21 -0400, Paul Smith wrote:
  I have folders ordered by Received (Descending, i.e. the oldest
 thread
  first) and this problem doesn't happen to me. I suspect the problem
  has to do with wanting the most recent thread (i.e. the thread with
  the most recent message) at the top but the messages within each
  thread go from oldest to newest.
 
 That's why I order my mail Ascending instead of Descending, with the
 newest mail at the BOTTOM of the folder.  Although it's a bit weird at
 first, this seems the most natural to me; it aligns the inter-thread
 order with the intra-thread order: both go from oldest at the top to
 newest at the bottom.
 

I misunderstood you. As I said, I also have oldest first (both threads
and messages) yet I don't see the behaviour you describe. However I seem
to have a custom sort order which I must have configured a long time ago
and forgotten about. I can't find an obvious way to see what it's set
to.

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list