Your message dated Tue, 18 Mar 2008 10:28:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#468367: Add line lock
has caused the Debian Bug report #468367,
regarding Add line lock
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
468367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468367
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gobby
Version: 0.4.6-3
Severity: wishlist
--- Please enter the report below this line. ---
It could be appreciable to lock a line such as only a writer can use it.
It this way you could enable the undo for the current line. Moreover, it
help the writers to coordinate themself. Some time two of them can
delete some chars from a line using backspace, if more than one use
backspace are deleted a lot of chars. Thanks
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-686
Debian Release: lenny/sid
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing ftp.it.debian.org
--- Package information. ---
Depends (Version) | Installed
=========================================-+-================
libatk1.0-0 (>= 1.20.0) | 1.20.0-1
libavahi-client3 (>= 0.6.13) | 0.6.22-2
libavahi-common3 (>= 0.6.10) | 0.6.22-2
libavahi-glib1 (>= 0.6.12) | 0.6.22-2
libc6 (>= 2.7-1) | 2.7-6
libcairo2 (>= 1.4.0) | 1.4.14-1
libcairomm-1.0-1 (>= 1.4.0) | 1.4.6-1
libgcc1 (>= 1:4.1.1-21) | 1:4.3-20080202-1
libgconf2-4 (>= 2.13.5) | 2.20.1-3
libglib2.0-0 (>= 2.12.0) | 2.14.6-1
libglibmm-2.4-1c2a (>= 2.14.0) | 2.14.2-4
libgnomevfs2-0 (>= 1:2.17.90) | 1:2.20.1-1
libgnutls26 (>= 2.2.0-0) | 2.2.1-3
libgtk2.0-0 (>= 2.12.0) | 2.12.5-2
libgtkmm-2.4-1c2a (>= 2.12.0) | 1:2.12.3-2
libgtksourceview2.0-0 (>= 2.0.2) | 2.0.2-1
libnet6-1.3-0 (>= 1:1.3.4-0) | 1:1.3.6-1
libobby-0.4-1 | 0.4.5-1
liborbit2 (>= 1:2.14.10) | 1:2.14.10-0.1
libpango1.0-0 (>= 1.18.4) | 1.18.4-1
libsigc++-2.0-0c2a (>= 2.0.2) | 2.0.17-2
libstdc++6 (>= 4.2.1-4) | 4.3-20080202-1
libxml++2.6-2 (>= 2.20.0) | 2.20.0-1
libxml2 | 2.6.31.dfsg-1
--- End Message ---
--- Begin Message ---
tag 468367 + wontfix
On Thu, Feb 28, 2008 at 04:31:03PM +0100, Marco Righi wrote:
> It could be appreciable to lock a line such as only a writer can use it.
> It this way you could enable the undo for the current line. Moreover, it
> help the writers to coordinate themself. Some time two of them can
> delete some chars from a line using backspace, if more than one use
> backspace are deleted a lot of chars. Thanks
No, sorry. The clue of Gobby is that it is lock-free. Gobby's
successor will have undo, but we won't add locks just to provide it.
Our aims were at all times to provide a sensible algorithmic undo.
Sadly we didn't get it implemented in obby, but in its successor
infinote only, which still needs Gobby ported to it.
Kind regards,
Philipp Kern
--
.''`. Philipp Kern Debian Developer
: :' : http://philkern.de Debian Release Assistant
`. `' xmpp:[EMAIL PROTECTED]
`- finger pkern/[EMAIL PROTECTED]
signature.asc
Description: Digital signature
--- End Message ---
