Summary: | allow multiple 'to' addresses on the same line in the 'to:' address box | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | James Th <james> |
Component: | composer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CLOSED NOT A BUG | ||
Severity: | normal | CC: | bs, montel |
Priority: | NOR | ||
Version: | 5.12.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
James Th
2019-10-08 10:49:57 UTC
KMail did a different choice, when you enter a comma (or a semicolon) after an email address, it automatically creates a new "To" line. The same thing happens if you paste email addresses (eg: foo@email.com,bar@email.com) Ok, many thanks! I understand that this is a feature request - where is the
best place to file feature requests please, as I completely understand than
bugs.kde.org is perhaps not the correct place?
thanks!
> https://bugs.kde.org/show_bug.cgi?id=412725
>
> Christophe Giboudeaux <christophe@krop.fr> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|REPORTED |RESOLVED
> Resolution|--- |NOT A BUG
>
> --- Comment #1 from Christophe Giboudeaux <christophe@krop.fr> ---
> KMail did a different choice, when you enter a comma (or a semicolon) after
> an email address, it automatically creates a new "To" line.
>
> The same thing happens if you paste email addresses (eg:
> foo@email.com,bar@email.com)
Well, there's nothing to report :) Laurent removed lots of useless options, I don't think he's willing to add new ones. Anyway, bugs.kde.org is the right place for feature requests. Great, thanks for letting me know that this is the right place to include feature requests! Just don't want to waste your time, if it wasn't! :) > https://bugs.kde.org/show_bug.cgi?id=412725 > > --- Comment #4 from Christophe Giboudeaux <christophe@krop.fr> --- > Anyway, bugs.kde.org is the right place for feature requests. Hi, The problem is not just adding/removing option. It's just that we implemented check signature type for email address and we display an icon on the line. It's for that that Dan modified it. So we can't switch back otherwise this feature will not work. Regards (In reply to Laurent Montel from comment #6) > Hi, > > The problem is not just adding/removing option. > It's just that we implemented check signature type for email address and we > display an icon on the line. It's for that that Dan modified it. > > So we can't switch back otherwise this feature will not work. > > Regards I've re-opened this ticket. Simply because Perhaps there's a way that could be a good compromise: if 'check signature type' is not enabled (which in my case will probably never happen, and will likely be the use-case for a number of other people), then the code could allow multiple addresses within the same 'to:' box (comma- separated) Once 'check signature type' is enabled, then perform the current code ie 1:1 relationship between email address & 'to:' box. This way I think that we can preserve the hard-work that Dan's done, whilst providing another option. Thanks! No need for new options for exotic features only useful for your workflow. If ever you wonder why people don't use kmail, it's exactly things like this that are the reason why. Poor design, lack of compromise, and etotistical attitudes. On 08/10/2019, 18:02, "Christophe Giboudeaux" <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=412725 Christophe Giboudeaux <christophe@krop.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |NOT A BUG --- Comment #8 from Christophe Giboudeaux <christophe@krop.fr> --- No need for new options for exotic features only useful for your workflow. -- You are receiving this mail because: You reported the bug. (In reply to James Th from comment #9) > If ever you wonder why people don't use kmail, it's exactly things like this > that are the reason why. > > Poor design, lack of compromise, and etotistical attitudes. A bad design because you can't write "foo@kde.org, bla@kde.org" ?:) Is it not work when we use several line ? if it's the case ok it's a bad design. But adding a option only because you prefer having "foo@kde.org, bla@kde.org" it's not a solution. and I don't think that it's a lack of compromise when you just want to complexify code only as you want to be able to write to email separated with a ',' ... I think you're missing the point. The point is quite simply, you shouldn't
have to agree with me, but you should at least listen to what I say. The
question is to do with respecting of my ideas, both as an end-user, and as a
member of the KDE community. I don't see your role as being Kmail's gate-
keeper. I see your role as being a listener to ideas and opinions, and having
the common-sense to be able to say "OK, i don't necessarily agree with what
this person is proposing, but there might be an idea worth implementing for
the good of the end-users." By me asking for the possibility to separate email
addresses is really not a silly idea. Outlook, Apple mail, etc do this by
default. If I wrote a feature request asking for kmail to default to a pink
colour scheme with purple unicorns, i would expect you to use the intelligence
that you have, and say 'no'.
My only "fault" in all this is to request a feature that so many other email
clients use. When you wrote and explained to me, that there was a reason why
we have multiple 'To:' boxes, I didn't rubbish your thoughts, or your
explanation. I took it onboard, listened to your reasons, and I came up with
what I believe to be a reasonable compromise so that we could both have a
solution. To be told by someone else that this is 'an exotic feature that is
only useful to your workflow" is rude, unnecessary, and unhelpful.
Do you know that just like you, I really, really like kmail. It's so much
better than Thunderbird, and just like you I want it to succeed. It's the
only mail client that I have on my openSUSE TW box, it's the only one that I
actually want to use. We have common-ground, I would just like us to build on
that, and to build a successful solution that works for all of us. To engage
with each other, and to challenge each other is great! To basically piss on my
ideas, because people don't believe in them is not democratic, fair, helpful,
or professional.
> https://bugs.kde.org/show_bug.cgi?id=412725
>
> --- Comment #10 from Laurent Montel <montel@kde.org> ---
> (In reply to James Th from comment #9)
>
> > If ever you wonder why people don't use kmail, it's exactly things like
> > this that are the reason why.
> >
> > Poor design, lack of compromise, and etotistical attitudes.
>
> A bad design because you can't write "foo@kde.org, bla@kde.org" ?:)
> Is it not work when we use several line ? if it's the case ok it's a bad
> design.
> But adding a option only because you prefer having "foo@kde.org,
> bla@kde.org" it's not a solution. and I don't think that it's a lack of
> compromise when you just want to complexify code only as you want to be
> able to write to email separated with a ',' ...
Maybe there is no point in adding a suggestion here and maybe it is handled elsewhere. But i would like to add an idea to the current handling. When i want to use a list of recipients i cannot copy and paste a text of the form: a...@... b...@... c...@... I have to add a comma to the end of each line. This should not be necessary. The Newline should have the same effect as the comma. Having the recipients in separate lines is great. Just the requirement to add a comma to each line looks weird. |