Bug 109208

Summary:	KWrite indentation moves C preprocessor '#' to the start of the line
Product:	[Applications] kate	Reporter:	Clarence Dang <dang>
Component:	indentation	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	christoph, esigra
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Clarence Dang 2005-07-17 12:14:02 UTC

Version:            (using KDE KDE 3.4.0)
Installed from:    Fedora RPMs
OS:                Linux

Ever since KDE 3.4, typing '#' in a .cpp file sends the cursor straight to the left.

This is a matter of coding style but now I have to fight KWrite to let me indent '#'s :(

I'd ask that this be made configurable.

Comment 1 Christoph Cullmann 2005-09-29 17:00:59 UTC

indentation wish

Comment 2 Clarence Dang 2005-11-08 12:38:32 UTC

In general the indenter in the KWrite of KDE 3.4 is too aggressive.  Another issue is that it is now difficult to do a particular kernel coding style that looks like this:

static
int  // but KWrite indents when pressing enter after "static"
function()
{
}

A workaround for both of these problems is to use the "Normal" indentation mode instead of the "C Style".

Comment 3 Christoph Cullmann 2012-10-28 16:27:59 UTC

Hi,

the indenter is a javascript which you can fix and provide a patch.

For docs see http://kate-editor.org/2009/10/29/extending-kate-with-scripts/

We have not the time nor expertise to maintain the indenters on our own and fix all corner cases, the same hold for the highlighters. Please help out ;)
Reopen if a patch is around.

Comment 4 Andrew Crouthamel 2018-09-23 02:35:24 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-27 03:42:29 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!