Bug 400982 - Do not add spurious newline to task DESCRIPTION, but differentiate SUMMARY in unified text box
Summary: Do not add spurious newline to task DESCRIPTION, but differentiate SUMMARY in...
Status: REPORTED
Alias: None
Product: zanshin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.08.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: already done
Assignee: Kevin Ottens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-12 20:49 UTC by Erik Quaeghebeur
Modified: 2022-12-03 15:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Quaeghebeur 2018-11-12 20:49:39 UTC
In vtodos Zanshin's task description is decomposed into a SUMMARY and a DESCRIPTION. Because zanshin itself does not explicitly differentiate between these concepts, when adding a task to Zanshin, I separate with a white line the SUMMARY and DESCRIPTION (that looks better visually). However, then a '\n' is inserted in the vtodo item at the start of the DESCRIPTION field. It should not be there. It can be easily stripped, I guess.

I am talking here about vtodos, because that is my use case, but this report is equally valid for interoperability with Kontact's task manager, which is heavily inspired by vtodo functionality. There, in the DESCRIPTION field also a spurious blank line is added. 

In Zanshin itself the first line of the unified SUMMAR+DESCRIPTION box is used as a SUMMARY/Title for purposes of listing the task in the task list. So perhaps  this first line should also be differentiated in the unified text box, e.g., by italicizing it, or adding some whitespace or a line below it, or yet something else.
Comment 1 Justin Zobel 2022-12-03 09:01:29 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Erik Quaeghebeur 2022-12-03 15:06:15 UTC
(In reply to Justin Zobel from comment #1)
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?

Still present.