extragear/sdk/kdevelop/app

David Nolden zwabel at googlemail.com
Tue Dec 8 12:04:56 UTC 2009


Am Dienstag 08 Dezember 2009 09:14:24 schrieb Andreas Pakulat:
> On 08.12.09 01:39:09, David Nolden wrote:
> > SVN commit 1060081 by zwabel:
> >
> > Allow specifying the session to load through the command-line.
> >
> >  M  +5 -0      main.cpp
> >
> >
> > --- trunk/extragear/sdk/kdevelop/app/main.cpp #1060080:1060081
> > @@ -118,6 +118,7 @@
> >      KCmdLineArgs::init( argc, argv, &aboutData );
> >      KCmdLineOptions options;
> >      options.add("profile <profile>", ki18n( "Profile to load" ));
> > +    options.add("s <session>", ki18n("Session to load" ));
> >      options.add("project <project>", ki18n( "Url to project to load" ));
> >      options.add("+files", ki18n( "Files to load" ));
> 
> Looking at this is there a definition of how -s, -project and additional
> files being listed interact? Also, can we please stay consistent and use
> "session" instead of just "s".
The problem is that when using "session", a strange assertion happens within 
KCmdLine Args, and I had neither time nor nerves to debug this.

> Can't we make this a proper setter on the Core class? - please :)

In future, I hope that the _primary_ way of setting the session will be the 
environment-variable, so that the duchain can use that information during 
initialization. Which means that, once I've found a way to spawn another 
_detached_ instance of kdevelop with a specific environment-variable set, we 
can remove the cmdline-option again completely.

Greetings, David




More information about the KDevelop-devel mailing list