After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736985 - Signature separator
Signature separator
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: composer
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
review
Depends on:
Blocks:
 
 
Reported: 2014-09-19 16:56 UTC by Robert Schroll
Modified: 2021-07-05 13:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Don't strip trailing space from signature separator (1.01 KB, patch)
2014-09-19 17:12 UTC, Robert Schroll
committed Details | Review

Description Robert Schroll 2014-09-19 16:56:42 UTC
As was mentioned in bug #712895, the standard, for plain-text emails at least, is to precede the signature with a single line containing "-- ".  Not only do we not do that, we make it impossible for the user to do it by hand: Thanks to bug #731746, we strip off trailing spaces.

I see a number of possible solutions.

1) Allow the user to have their signature begin with "-- ".  Practically, this means detecting this line in our flowed-text formatter and treating it specially.  We'll have to do this for any of the other solutions, so I'll go ahead and do it.

2) Automatically insert "-- " before the signature when it's added to the composer.  This seems to be controversial in #712895.

3) Have an option to insert the separator or not.

4) Only insert the separator in the plain text component.  This would mean adding it at send-time, not insertion-time, so the user wouldn't get a chance to see it before it went out.

5) Only insert the separator when in the plain text compose mode.  This assumes that the people who care about the separator are the same people who insist on plain text emails, which doesn't seem unreasonable.  It might fool people into thinking the separator will be in the plain text version of their HTML emails, which isn't true.  I don't know what we would want to do when the user switched compose formats.
Comment 1 Robert Schroll 2014-09-19 17:12:46 UTC
Created attachment 286651 [details] [review]
Don't strip trailing space from signature separator

This does (1), which will also be needed by any of the other solutions.
Comment 2 Jim Nelson 2014-09-19 18:43:10 UTC
Review of attachment 286651 [details] [review]:

Looks good, Robert.  Please insert a comment before the code that explains why this particular line is exceptional, then commit!
Comment 3 Jim Nelson 2014-09-19 18:47:21 UTC
At this point, I think I'd rather leave it up to the user to manually add their signature separator (if any) in the edit box rather than offer options or automatically insert it.  Do you have a leaning on this?
Comment 4 Robert Schroll 2014-09-19 19:07:44 UTC
Comment on attachment 286651 [details] [review]
Don't strip trailing space from signature separator

I'll leave this bug open while we're considering other changes to how 
the signature separator should be handled.

I don't use signatures myself, so I have no strong opinions.  But people 
who do seem to care a lot, so letting them set things up however they 
like may be a good strategy.  We could populate the signature box with 
"-- \n" initially to indicate to people that they can include it if they 
want it.

Attachment 286651 [details] pushed as 17b481d - Don't strip trailing space from signature separator
Comment 5 Jim Nelson 2014-09-19 19:19:37 UTC
Sounds good.  I too don't have strong opinions, although I do use signatures (now) and don't use a top-dash separator.  Yet another tricky email issue.  Three users, four use-cases.
Comment 6 Federico Bruni 2018-01-12 12:38:19 UTC
I see that Robert's patch was pushed to master.

I don't have strong opinions on how to handle signatures. Options 4) and 5) might be the best ones.
Comment 7 GNOME Infrastructure Team 2021-07-05 13:28:10 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.