CVS Background Tasks

The recent changes to make the update/commit process run in the
background unfortunately haven't made an iota of difference to my
workflow - when these tasks are running were the times I'd go make a cup
of tea anyway, and so updating/committing in the background makes no
difference to me.

Granted if the ui were responsive enough would allow you to carry on
navigating around code if you need to, so in those terms it's no bad
thing, but in terms of impact to improving my personal productivity it
ranks pretty low.

What would really help me out however would be if the cvs operations
that seriously do impact my workflow could be backgrounded - that
would be the add/remove operations. So many times I find my train of
thought broken mid-flow, sitting there waiting for CVS to do it's
business because I've just created or moved a class, and with a remote
CVS connection such as I have it can become quite tiresome.

Maybe it's already done, and I'm missing the way to turn it on, but if
it's not already there, is it already planned for addition in a point
release? Should I file a JIRA?

Cheers,
N.

4 comments

Hello Nathan,

NB> The recent changes to make the update/commit process run in the
NB> background unfortunately haven't made an iota of difference to my
NB> workflow - when these tasks are running were the times I'd go make a
NB> cup of tea anyway, and so updating/committing in the background
NB> makes no difference to me.
NB>
NB> Granted if the ui were responsive enough would allow you to carry on
NB> navigating around code if you need to, so in those terms it's no bad
NB> thing, but in terms of impact to improving my personal productivity
NB> it ranks pretty low.
NB>
NB> What would really help me out however would be if the cvs operations
NB> that seriously do impact my workflow could be backgrounded - that
NB> would be the add/remove operations. So many times I find my train
NB> of thought broken mid-flow, sitting there waiting for CVS to do it's
NB> business because I've just created or moved a class, and with a
NB> remote CVS connection such as I have it can become quite tiresome.
NB>
NB> Maybe it's already done, and I'm missing the way to turn it on, but
NB> if it's not already there, is it already planned for addition in a
NB> point release? Should I file a JIRA?

No, it's not done, and if by "point release" you mean 6.0.x, it won't be
done in such a release either. But it's something that we'll definitely consider
for the 6.5 release.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Great... is there an existing JIRA for it, or should I file another?

Thanks,
Nathan.

Dmitry Jemerov wrote:

Hello Nathan,

NB> The recent changes to make the update/commit process run in the
NB> background unfortunately haven't made an iota of difference to my
NB> workflow - when these tasks are running were the times I'd go make a
NB> cup of tea anyway, and so updating/committing in the background
NB> makes no difference to me.
NB> NB> Granted if the ui were responsive enough would allow you to
carry on
NB> navigating around code if you need to, so in those terms it's no bad
NB> thing, but in terms of impact to improving my personal productivity
NB> it ranks pretty low.
NB> NB> What would really help me out however would be if the cvs
operations
NB> that seriously do impact my workflow could be backgrounded - that
NB> would be the add/remove operations. So many times I find my train
NB> of thought broken mid-flow, sitting there waiting for CVS to do it's
NB> business because I've just created or moved a class, and with a
NB> remote CVS connection such as I have it can become quite tiresome.
NB> NB> Maybe it's already done, and I'm missing the way to turn it on, but
NB> if it's not already there, is it already planned for addition in a
NB> point release? Should I file a JIRA?

No, it's not done, and if by "point release" you mean 6.0.x, it won't be
done in such a release either. But it's something that we'll definitely
consider for the 6.5 release.

0

Hello Nathan,

Please file a new one.

NB> Great... is there an existing JIRA for it, or should I file another?
NB>
NB> Thanks,
NB> Nathan.
NB> Dmitry Jemerov wrote:
NB>
>> Hello Nathan,
>>
>> NB> The recent changes to make the update/commit process run in the
>> NB> background unfortunately haven't made an iota of difference to my
>> NB> workflow - when these tasks are running were the times I'd go
>> make a
>> NB> cup of tea anyway, and so updating/committing in the background
>> NB> makes no difference to me.
>> NB> NB> Granted if the ui were responsive enough would allow you to
>> carry on
>> NB> navigating around code if you need to, so in those terms it's no
>> bad
>> NB> thing, but in terms of impact to improving my personal
>> productivity
>> NB> it ranks pretty low.
>> NB> NB> What would really help me out however would be if the cvs
>> operations
>> NB> that seriously do impact my workflow could be backgrounded -
>> that
>> NB> would be the add/remove operations. So many times I find my
>> train
>> NB> of thought broken mid-flow, sitting there waiting for CVS to do
>> it's
>> NB> business because I've just created or moved a class, and with a
>> NB> remote CVS connection such as I have it can become quite
>> tiresome.
>> NB> NB> Maybe it's already done, and I'm missing the way to turn it
>> on, but
>> NB> if it's not already there, is it already planned for addition in
>> a
>> NB> point release? Should I file a JIRA?
>> No, it's not done, and if by "point release" you mean 6.0.x, it won't
>> be done in such a release either. But it's something that we'll
>> definitely consider for the 6.5 release.
>>
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Done : http://www.jetbrains.net/jira/browse/IDEA-9597

Cheers,
N.

Dmitry Jemerov wrote:

Hello Nathan,

Please file a new one.

NB> Great... is there an existing JIRA for it, or should I file another?
NB> NB> Thanks,
NB> Nathan.
NB> Dmitry Jemerov wrote:
NB>

>>> Hello Nathan,
>>>
>>> NB> The recent changes to make the update/commit process run in the
>>> NB> background unfortunately haven't made an iota of difference to my
>>> NB> workflow - when these tasks are running were the times I'd go
>>> make a
>>> NB> cup of tea anyway, and so updating/committing in the background
>>> NB> makes no difference to me.
>>> NB> NB> Granted if the ui were responsive enough would allow you to
>>> carry on
>>> NB> navigating around code if you need to, so in those terms it's no
>>> bad
>>> NB> thing, but in terms of impact to improving my personal
>>> productivity
>>> NB> it ranks pretty low.
>>> NB> NB> What would really help me out however would be if the cvs
>>> operations
>>> NB> that seriously do impact my workflow could be backgrounded -
>>> that
>>> NB> would be the add/remove operations. So many times I find my
>>> train
>>> NB> of thought broken mid-flow, sitting there waiting for CVS to do
>>> it's
>>> NB> business because I've just created or moved a class, and with a
>>> NB> remote CVS connection such as I have it can become quite
>>> tiresome.
>>> NB> NB> Maybe it's already done, and I'm missing the way to turn it
>>> on, but
>>> NB> if it's not already there, is it already planned for addition in
>>> a
>>> NB> point release? Should I file a JIRA?
>>> No, it's not done, and if by "point release" you mean 6.0.x, it won't
>>> be done in such a release either. But it's something that we'll
>>> definitely consider for the 6.5 release.
>>>

0

Please sign in to leave a comment.