Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: use Interleaved style response style instead of Top posting #120

Closed
nonfreegithub opened this issue Oct 23, 2023 · 1 comment · Fixed by #124
Closed

Suggestion: use Interleaved style response style instead of Top posting #120

nonfreegithub opened this issue Oct 23, 2023 · 1 comment · Fixed by #124
Labels
Enhancement New feature or request
Milestone

Comments

@nonfreegithub
Copy link
Contributor

I suggest that when you respond to an email, the mod could use the Interleaved style response style instead the ugly Top posting.

Interleaved style is more aesthetic, allows you to respond to specific parts of the email and is mostly used in regular email (also in GitHub)

The Top posting style became fashionable because of Outlook/Gmail and it looks very ugly in a long message conversation

I don't know if it would be possible to give a nice format to the quotes with > when the message is displayed

I recommend this wikipedia article

@BuckarooBanzay BuckarooBanzay added the Enhancement New feature or request label Oct 27, 2023
@Athozus
Copy link
Member

Athozus commented Dec 2, 2023

I'll try to do that for new release, thanks. However, putting bars like :

Hello, I'm Athozus

could be very complicated in Minetest formspec.

At least, the minimal is to use > chars, indeed. It should just detects line-breaks and add those chars.

@Athozus Athozus added this to the 1.4.0 milestone Dec 2, 2023
Athozus added a commit that referenced this issue Dec 8, 2023
* Generate interleaved style when replying/forwarding a message (#120)

* Simplify interleaving function

Co-authored-by: SX <[email protected]>

---------

Co-authored-by: SX <[email protected]>
@Athozus Athozus linked a pull request Dec 8, 2023 that will close this issue
@Athozus Athozus closed this as completed Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants