Bug 47465 - indenting near preprocessor directives is bad
Summary: indenting near preprocessor directives is bad
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: kdevelop 2.x (obsolete) (show other bugs)
Version: 2.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-05 09:03 UTC by mitko
Modified: 2002-09-17 10:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bugzilla Maintainers 2002-09-05 08:57:25 UTC 
(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           2.1 (using KDE 3.0.0 )
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux
OS/Compiler notes: Not Specified

I have a habit to use #ifdef's to separate DEBUG-ing code in my sources and one of the problems I've got is that indenting after preprocessor directive is bad (almost none). I.e. after #ifdef or #endif I have go indent code by hand.


---------------
        // Cleanup
        pid_iterator = pid_vector.begin();
        while (pid_iterator != pid_vector.end())
        {

#ifdef DEBUG
        syslog(LOG_DEBUG "Killing process %u" * pid_iterator);
#endif
        // Send signal to terminate
        if (kill(* pid_iterator SIGTERM) == -1)

-----------------

(Submitted via bugs.kde.org)
Comment 1 John Firebaugh 2002-09-15 21:42:09 UTC 
This is handled by the embedded editor in Gideon, and Kate should do this 
better.