Double Commander

I often rename files and use strings from the clipboard for insert.
So when I do the renaming I write some strings, press ctrl-v and continue writing other strings. But when I look at the written name there is always the dot at the wrong position.

so for example:
1) the filename is "filename.txt"
2) I press F2
3) "filename" is marked because I always exclude the extension
4) I begin to write "new "
5) I press ctrl-v and in the clipboard is the word "name"
6) the result is : "new name.|txt"
=> as You can see the cursor is behind the dot and when I continue to write the dot is left behind.
=> I now always press the <- Cursor Back - but that's just a workaround.

This behavior is not on the Windows Version of DC (tried it with windows xp sp3).

Double Commander 0.5.4beta rev4505
openSuSE 11.4 with all latest updates

Thanks

_________________
OpenSource the Planet

Test rev.4730M from snapshots. I tested on it and didn't find this problem.

_________________
ОС: Win 7 Home Basic / Pro, 0.5.5 (on of latest build).

I tested now DC 0.5.5alpha rev4730M GTK

Result : The problem still exists. So the bug was not fixed in that release.
And : there is another new anoying thing in this alpha release - I have now 2 /boot buttons (I didn't need the one in the previous versions - who honestly wants to go in to /boot. /home should be the first button)
And : I also have now 2 /home buttons - one would be enough.

Has anyone else 2 /boot buttons?
I also would like to see this button gone and the sort order should be local mp's first and nfs/smb last. In my release there comes /boot first, then all my NFS drives and then the other local mountpoints. And it is not the same order which I get from df. Would be cool, If the sort order would be configurable.

Maybe the whole thing is a GTK problem (installed version is 2.22.1 and 3.0.0)

In the meantime I will step back to rev4505.

_________________
OpenSource the Planet

I think the problem is with the OS. In Windows 7, everything is OK.

_________________
ОС: Win 7 Home Basic / Pro, 0.5.5 (on of latest build).

Please post output of:

as I wrote in my initial post, DC on Windows XP does NOT have the problem. But my prefered OS is not Windows.
I tried it now on another Linux Installation (openSuSE 11.3, completely different setup) and I can reproduce the problem there (with dc 0.5.5.alpha 4730m)

Thanks

_________________
OpenSource the Planet

/dev/rootvg/lvroot / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-INTEL_SSDSC2MH250A2_LNEL113600JK250DGN-part3 /boot ext4 acl,user_xattr 1 2
/dev/rootvg/lvswap swap swap defaults 0 0
/dev/rootvg/lvhome /home ext4 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
datasafe:/crypt/crypt_daten /nfs/crypt_daten nfs rw,suid,dev,exec,noauto,nouser,async 0 0
datasafe:/crypt/crypt_temp /nfs/crypt_temp nfs rw,suid,dev,exec,noauto,nouser,async 0 0
datasafe:/crypt/crypt_vdr /nfs/crypt_vdr nfs rw,suid,dev,exec,noauto,nouser,async 0 0
datamachine:/volume1/data /nfs/datamachine nfs rw,suid,dev,exec,noauto,nouser,async 0 0


rootfs / rootfs rw 0 0
devtmpfs /dev devtmpfs rw,relatime,size=6154116k,nr_inodes=1538529,mode=755 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/mapper/rootvg-lvroot / ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/sda3 /boot ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/mapper/rootvg-lvhome /home ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
vmware-vmblock /var/run/vmblock-fuse fuse.vmware-vmblock rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0
gvfs-fuse-daemon /home/ruxi002/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
truecrypt /tmp/.truecrypt_aux_mnt1 fuse.truecrypt rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/mapper/truecrypt8 /crypt/tcraid ext4 rw,relatime,barrier=1,stripe=1,data=ordered 0 0
truecrypt /tmp/.truecrypt_aux_mnt2 fuse.truecrypt rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/mapper/truecrypt9 /crypt/tc ext4 rw,relatime,barrier=1,data=ordered 0 0
truecrypt /tmp/.truecrypt_aux_mnt3 fuse.truecrypt rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/mapper/truecrypt7 /crypt/vm ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0
datasafe:/crypt/crypt_daten /nfs/crypt_daten nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.33,mountvers=3,mountport=51977,mountproto=udp,local_lock=none,addr=10.0.0.33 0 0
datasafe:/crypt/crypt_temp /nfs/crypt_temp nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.33,mountvers=3,mountport=51977,mountproto=udp,local_lock=none,addr=10.0.0.33 0 0
datasafe:/crypt/crypt_vdr /nfs/crypt_vdr nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.33,mountvers=3,mountport=51977,mountproto=udp,local_lock=none,addr=10.0.0.33 0 0
datamachine:/volume1/data /nfs/datamachine nfs rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.55,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=10.0.0.55 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
gvfs-fuse-daemon /home/insecure/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1001,group_id=65533 0 0
truecrypt /tmp/.truecrypt_aux_mnt4 fuse.truecrypt rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/mapper/truecrypt3 /media/truecrypt3 ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0

Maybe that helps. I have no idea - because when I downgrade to 0.5.4 the buttons are fine.
Thanks

_________________
OpenSource the Planet

The bug with cursor position is fixed with latest Lazarus.

You have different device paths so DC detects that as two different devices. First is I think a symlink. What file is the other one: /dev/rootvg/lvhome?

lvhome is a Logical Volume where my /home Filesystem resides. And You were right, it is a link - have a look below.
Everything was created using Yast of openSuSE. So this is a normal behavior, when You create a /boot (which may not be inside a Volume Group) and a LVM Volume Group with other Filesystems. I can't tell If RedHat/Debian/Ubuntu are there any different.

workbench:/dev/disk/by-id> ls -al
lrwxrwxrwx 1 root root 10 Mär 25 18:45 ata-INTEL_SSDSC2MH250A2_LNEL113600JK250DGN-part3 -> ../../sda3

workbench:/dev/rootvg> ls -al
lrwxrwxrwx 1 root root 7 Mär 25 18:45 lvhome -> ../dm-1
lrwxrwxrwx 1 root root 7 Mär 25 18:45 lvroot -> ../dm-2
lrwxrwxrwx 1 root root 7 Mär 25 18:45 lvswap -> ../dm-3

As I said before, this is a normal openSuSE configuration. Maybe You can consider that for a future release of DC.
More than one button for the same device is disturbing but the world doesn't end because of that. So is this is absolutely a low priority issue.

Thanks in advance.

And have a nice weekend

_________________
OpenSource the Planet