#4370 closed enhancement (wontfix)
Please implement a check-in and re-checkout in one step menu item
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | |
Component: | version control | Version: | 1.5.2 |
Severity: | minor | Keywords: | |
Cc: | ps@… |
Description (last modified by )
Hi,
this is a forward from the Debian BTS:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=362052
Original report:
"""
It would be nice if LyX had an menu command similar to "ci -l" which
would record changes to the document in the RCS file then immediately
re-checkout the document so the user could continue editing without
interruption.
It would also be nice if performing version control operations wouldn't
scroll the editing window back to the top, and instead leave the scroll
and cursor position as-is to again reduce editing interruptions.
"""
Change History (5)
comment:1 by , 15 years ago
Cc: | added |
---|
comment:2 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment 1:
this would cause confusions for other-than rcs control systems. two possible
workarounds - either use version control toolbar - check in-out is only one click
more... the second one would be possible later when we have new lfun for
external commands (eg ci -l) for which you can make your own toolbar icon. i
have permission from Juergen to put it to only to 1.6.2 though.
comment 2:
thats unrelated to RCS, but anyway scrolling to old position works here after
document reload. maybe the reported forget to switch automatic scrolling in
preferences.
comment:3 by , 15 years ago
Hi,
the scrolling problem seems to be fixed at least in 1.6.0. I'm pretty sure that
I could reproduce it when I forwarded the bug.
The version controll toolbar makes it a bit easier but if I would use version
control within LyX I would be anonyed too. It's really somehow counter intuitive
that you've to check the document in and out again to continue writing.
Getting this fixed with 1.6.2 seems fine but that's not resolved/wontfix now I
think.
comment:4 by , 15 years ago
It's really somehow counter intuitive that you've to check the document in and
out again to continue writing.
not in the context of rcs where checking-in/out is joined with locking by
default. moreover the proposed solution brings another confusion for other
backends like svn where commit and update for the same file has no meaning and
complicates
another log checks for errors etc.
as far as status of the bug i'm not going to reimplement this and since nobody
else have touched this stuff for years i feel confident to mark it wontfix...
comment:5 by , 13 years ago
Description: | modified (diff) |
---|---|
Priority: | high → low |
the requested thing work in 1.6.7 in with svn.
i got idea how to add it into rcs.
Pavel, what do you think?