Problems with new session support

[Andreas Pakulat]

On 27.01.10 23:17:33, Milian Wolff wrote:
> On Wednesday 27 January 2010 22:38:39 Andreas Pakulat wrote:
> > On 27.01.10 22:12:39, David Nolden wrote:
> > > Well, on my work machine I have 3 sessions that don't have a name, and it
> > > is totally fine like that. What would I need a session name for, if the
> > > contained projects completely identify the session? We can leave the
> > > user alone with such unneeded overhead. "kdevplatform, kdevelop"
> > > identifies my kdevelop session perfectly.
> > 
> > The problem is that you can't start the session that way from the
> > commandline with the -s switch.
> 
> You can, simply pass it's hash. Not nice, but works.

Ah, sorry, I forgot to enable uuid-storage in my brain ;) Sorry, but
there's no way to associate a 32-char number with a list of projects in
a normal human brain.

So, besides the list of projects the name is the most important way of
choosing a session. And I'm a lazy person, so when I start kdevelop I
want it to be in the right session when the gui shows up, without having
to type more than 4 characters on the cli.

And I _always_ start kdev from the cli.

Andreas

-- 
Give your very best today.  Heaven knows it's little enough.