[PATCH] Re: how to access the editor configuration from the cppsupportpart.cpp
jbb at kdevelop.org
Sat Dec 21 19:56:02 UTC 2002
I don't think this is a good idea, BUT currently this is probably a reasonable
I believe that formatting text is an editor function. Locating astyle at the
editor end would be a good idea.
We need to solve the "sliding breakpoint" problem where someone adds or
removes lines from a file before a breakpoint. This leaves the display
showing the breapoint in a different position to the breakpoint set in gdb.
Having the text manipulated in several different places in kdevelop doesn't
help us with this problem.
Note this problem isn't a reason in itself to move astyle to the editor but
does illustrate problems with having the text manipulated in several places.
On Sat, 21 Dec 2002 12:39, Roberto Raggi wrote:
> Hi all,
> On Saturday 21 December 2002 00:09, Roberto Raggi wrote:
> > On Friday 20 December 2002 19:26, Andreas Wuest wrote:
> > > The solution in the patch is however only suboptimal. the best solution
> > > would be in imho :
> > >
> > > 1. create the code that will be inserted into the editor.
> > > 2. Pass that code along to a Formatter (ASFormatter, ASBeautifier ??)
> > > to format the code according to the code style configuration.
> > > 3. inserted the formatted code into the editor.
> > nice ;) i've just applied it
> ops!!! i'm thinking about the last patch, and now i'm not so sure that is a
> good idea to add a dependence from astyle to cppsupport..
> i would like to know other opinions and if is the case to revert the commit
> ciao robe
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
More information about the KDevelop-devel