[Users] RE [Bug 4415] New: [Patch] Do not select another message after after delete or move

[Luc Pardon]

  I am not sure if it's even worthwhile of having this discussion, but
  here goes.

On Fri, 20 Nov 2020 11:05:42 -0600
Brian A via Users <users at lists.claws-mail.org> wrote:

> [...] the code acts exactly
> as designed and expected by the developer and most users.  

  No argument here. I don't doubt that it is working as designed, and
  I do not doubt that it works as expected by "most users" either. In
  fact, in my enhancement request I explicitly stated that "Current
  Claws Mail users probably don't mind".

  The only thing is that I am not among the "most users". It certainly
  does not behave as I expect a mail program to behave.

  If that means I should not use CM, that's fine with me.

  After all, this is open
  source, developed by volunteers in their own time and given away for
  nothing. So the developers absolutely have the right to decide
  how it should work.

> [...] little illogical to me that anyone would want to continue to sit
> on the message they just deleted, as the act of deleting means I'm
> done with that email and ready to move to the next email or close the
> program all together. 

   Of course I *am* ready to move to the next mail after I am done
   with the current one.

   What is a little illogical to me <g> is that anyone would need a
   piece of software to tell them what that next mail should be.

   I for one am perfectly capable of deciding that myself.

   But that also means that, yes, CM must stay put (i.e. "sit on the
   message that I just deleted") and wait for my command.

   Now, if I am told that I must not expect CM to do that, then that is
   fine with me. See above.

 
> Also Claws-mail is not trying to emulate Thunderbird [...]

 It may not be trying to do that, but it's doing a good job anyway <g>,
 in that it behaves exactly the same as TB does out of the box. 

Without the "deselect on
 delete" add-on, TB also auto-selects the message that it
 thinks I should read next (*).

 They recently broke that add-on for the umpteenth time, and that is
 what finally sent me (and probably others) looking for an alternative
 (**).

 Please note: "alternative for TB" is not the same as "clone of
 TB", but I can understand that you doubt me on that.

 But: 

  * if this TB "feature" is annoying enough for me to dump habits of
 20+ years of TB use, 

  * and if Claws Mail insists on doing the same thing
 as TB, 

  * and if I am told that "it has always worked like this
 and no way we"re going to change that", 

  * then it follows that Claws Mail
 "out of the box" is not the alternative I am looking for.

 Too bad, because it has some nice features that TB has not.

 Or maybe not "too bad", as far as I am concerned, because I can
 always create a private fork of it, and then I would not
 even have to think about compatibility with "most users". Much easier
 for me.

 And much easier for you guys too, because I wouldn't waste your
 time with my musings either. Indeed, you wrote:

> This is
> a feature request which I'm not interested in seeing.

 I take note. And as I said, you are perfectly within your rights
 here.

 No hard feelings at this end, I hope the same for you.

 Luc

(*) In fairness, and as I mentioned in my feature request, I can tell CM
to not open that message. I can't do that in stock TB. But we're
dealing with the auto-selection here.

(**) Yes, I know, that add-on has recently been resurrected, but for
how long? In any case it was the proverbial straw, with me in the role
of the camel.