Version: 3.2.1 (using KDE KDE 3.4.2) Installed from: Unspecified Linux When I run "reformat source code" in a text file, it generates all indentation with space characters instead of tab characters, although KDevelop's options state that all indentations are done by tabs.
you have to make sure it's configured properly. The "Reformat source code" option doesn't use the settings from the editor.
but isn't that an inconsistency? If the program uses at least two separate sets of settings to act on the same options and behaviour, not only it will bring confusion to the user's but it also will make the usage and configuration a lot harder and absolutely not intuitive. Isn't there a plan to fix this bug?
KDevelop can use 3 diferent editors currently. These present three diferent configuration dialogs. But it can use even more as long as there is a ktexteditor interface to them. I've heard that there is a emacs-ktexteditor interface, that would be our fourth editor. What you want is for us to parse all the settings of these editors and discover which one affects the indentation, and then trconfigure astyle (source formatter) according to it ? It seams to bee too much work, for such a simple thing. And it will stop working as soon as a new editor comes out.
Yes, it seems to be too much work and not an easy task. Still, it isn't all that nice if there are options scattered through kdevelop which aren't usable.
Forgive me for reopening the bug but I've realized something. Couldn't this problem be solved just by running the "Tools"->"Clean indentation" routine after running the "Edit"->"Formato Sourcecode" routine?
*** Bug 133182 has been marked as a duplicate of this bug. ***
Re comment #5: yes, in theory. The problem is that "clean indentation" is a dynamically added action that KDevelop knows nothing about. To access non-exposed features of a dynamically loaded plugin is nasty business.. really only justified in very special cases.
Btw, I think this is a wish. Changing subject accordingly.
I don't see this happening at all, we don't control astyle and we don't control the editors indentation setting. If somebody has a bright idea how to fix this, please re-open.