Bug 341961

Summary: Feature request: Real increase/ decrease indend
Product: [Applications] kmail2 Reporter: mark <nurasima>
Component: composereditor-ngAssignee: Laurent Montel <montel>
Status: REPORTED ---    
Severity: wishlist CC: matthias.nagel
Priority: NOR    
Version First Reported In: 5.9.1   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description mark 2014-12-17 04:27:39 UTC 
When choosing to increase indend in a marked paragraph in the message body, one receive a bullet point list.
This might be the intention of the developers but it is misleading and a feature of real increase/ decrease indend, (preferably with <tab>/<shift><tab>,  is dearly missing.
..unless I am missing it.
In the wake of such change, I suggest to rename the current behaviour as well to what it really does.
Alternatively, the current behaviour can be kept but is configurable via a prefix for indendation (similar to quoting replied text). Empty prefix equals real indendation.

Reproducible: Always

Steps to Reproduce:
1. Mark a paragraph
2. Execute Increase Indent
3. Decrease Indend

Actual Results:  
>2 added bullet points
>3 removal of bullet points

Expected Results:  
>2 increased indendation of paragraph
>3 decreased indendation of paragraph
Comment 1 Matthias Nagel 2018-10-02 16:27:27 UTC 
Using the command "increase indent" from the menu bar intentionally creates a bullet list. The name is misleading. It should be something like "Increase/decrease nested list level". See this bug #215663.

Nonetheless, I support this feature request. Real indention is actually a missing feature. For example, I often discuss 3rd party literature via mail and having a feature like this would help to distinguish between my own text and citations.

However, I would not use the HTML tag <tab> but prefer something like <p style="margin-left:??px;> or alternatively a <blockquote>-environment. With respect to the support of <blockquote> there is already another feature request, see bug #362493.