Re: ksh file completion bug
Hi! Thanks to all who have replied. I'm really baffled with this. I've upgraded to a more recent snapshot, and it has gone away since. However I'm not really sure that the error was in the previous snapshot, in fact it was probably a PEBKAC, but I've no idea what could've been the problem. Anyway, sorry for the noise. Daniel -- LIVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
ksh file completion bug
Hi! With ksh's Vi edit mode I've experienced the following: If a file's size is exactly 2GiB or more, pdksh fails to complete its name during filename completion (eg.: hitting TAB or CTRL+e or whatever). If the file's size is just one byte short of the 2 gigs, then the completion works fine. Quick way to test it: $ dd if=/dev/zero of=./2GiB bs=1024 count=2097152 $ ls -la 2GTABTABTABTAB ... = nothing Daniel ps.: this is under -current and i386 -- LIVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
Re: ksh file completion bug
On Mon, Feb 22, 2010 at 10:50:39PM +0100, LEVAI Daniel wrote: | Hi! | | With ksh's Vi edit mode I've experienced the following: | If a file's size is exactly 2GiB or more, pdksh fails to complete its name | during filename completion (eg.: hitting TAB or CTRL+e or whatever). | If the file's size is just one byte short of the 2 gigs, then the completion | works fine. | | Quick way to test it: | $ dd if=/dev/zero of=./2GiB bs=1024 count=2097152 | $ ls -la 2GTABTABTABTAB ... = nothing | | | Daniel | | | ps.: this is under -current and i386 That's some weird shit you've got going there... $ dd if=/dev/zero of=2gigabyte bs=2048 count=1 seek=1048575 $ echo 2gTAB - immediately completes to 2gigabyte. $ echo $VISUAL vi $ echo $SHELL /bin/ksh $ echo $KSH_VERSION @(#)PD KSH v5.2.14 99/07/13.2 $ sysctl kern.version kern.version=OpenBSD 4.7-beta (GENERIC.MP) #86: Wed Feb 10 07:17:52 MST 2010 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Tried it on an (admittedly older) i386 and sparc64 machine and got the same. Also tried it with a non-sparse file (seek= creates sparse files when you're writing past the end of the file) and it still worked. So .. uhm .. works for me [TM] Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/
Re: ksh file completion bug
Quick way to test it: $ dd if=/dev/zero of=./2GiB bs=1024 count=2097152 $ ls -la 2GTABTABTABTAB ... = nothing I don't have any problem with this test under current, i386. -- Vivien MOREAU / vpm
Re: ksh file completion bug
On 23 February 2010 c. 00:50:39 LEVAI Daniel wrote: Hi! With ksh's Vi edit mode I've experienced the following: If a file's size is exactly 2GiB or more, pdksh fails to complete its name during filename completion (eg.: hitting TAB or CTRL+e or whatever). If the file's size is just one byte short of the 2 gigs, then the completion works fine. Quick way to test it: $ dd if=/dev/zero of=./2GiB bs=1024 count=2097152 $ ls -la 2GTABTABTABTAB ... = nothing No such problem seen so far. Even after recompiling ksh from -CURRENT. (but seen another one - about TAB _after_ exiting vi mode, will investigate it later...) -- Best wishes, Vadim Zhukov A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
