Bug in /usr/bin/less in SUSE 9.3?
![](https://seccdn.libravatar.org/avatar/23bfdb15d4a3fa042c8e1049d8e807d5.jpg?s=120&d=mm&r=g)
Hi! I have the following problem with /usr/bin/less (less-382-41) in SUSE 9.3 FTP edition for i386. I enter... $ less big-file.txt ...and nothing happens. Instead, I get another shell prompt, but I can't write anything (at least it's not echoed on screen). I press return and get a new shell prompt, but on the same row as the previous (no newline between). I hit Ctrl-D to exit that shell, and now the "less" screen shows up, and everything is back to normal. Strangely, "less < big-file.txt" works fine, and all other situations where less reads from stdin. I have tried different terminal emulators, and the bug persists. When I log into another machine and do "less file" (where less is part of another OS), there is no problem. Therefore, I believe the bug is in less. Perhaps in a library, since vimdiff seems to have the same problem. Has anyone else encountered this? -- Best Regards, Tom Weber
![](https://seccdn.libravatar.org/avatar/3d65ce348306eb0e36a6ec890e3e1b2d.jpg?s=120&d=mm&r=g)
On Thursday 08 September 2005 15:19, Tom Weber wrote:
Hi!
I have the following problem with /usr/bin/less (less-382-41) in SUSE 9.3 FTP edition for i386. I enter...
$ less big-file.txt
...and nothing happens. Instead, I get another shell prompt, but I can't write anything (at least it's not echoed on screen). I press return and get a new shell prompt, but on the same row as the previous (no newline between). I hit Ctrl-D to exit that shell, and now the "less" screen shows up, and everything is back to normal.
Strangely, "less < big-file.txt" works fine, and all other situations where less reads from stdin. I have tried different terminal emulators, and the bug persists. When I log into another machine and do "less file" (where less is part of another OS), there is no problem. Therefore, I believe the bug is in less. Perhaps in a library, since vimdiff seems to have the same problem.
Has anyone else encountered this?
-- Best Regards, Tom Weber
less [filename] seems to be working here OK on 9.3, version info: ~> which less /usr/bin/less ~> less -V less 382+iso254 Copyright (C) 2002 Mark Nudelman less comes with NO WARRANTY, to the extent permitted by law. For information about the terms of redistribution, see the file named README in the less distribution. Homepage: http://www.greenwoodsoftware.com/less Japanized part of Less Copyright (c) 1994-2000 Kazushi (Jam) Marukawa
![](https://seccdn.libravatar.org/avatar/861b5545c111d2257fa12e533e723110.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-09-08 at 16:19 +0200, Tom Weber wrote:
$ less big-file.txt
How big?
...and nothing happens. Instead, I get another shell prompt, but I can't write anything (at least it's not echoed on screen). I press return and get a new shell prompt, but on the same row as the previous (no newline between). I hit Ctrl-D to exit that shell, and now the "less" screen shows up, and everything is back to normal.
Strangely, "less < big-file.txt" works fine, and all other situations where less reads from stdin. I have tried different terminal emulators, and the bug persists. When I log into another machine and do "less file" (where less is part of another OS), there is no problem. Therefore, I believe the bug is in less. Perhaps in a library, since vimdiff seems to have the same problem.
Has anyone else encountered this?
No... Does that file have "strange" chars? Is your system fully updated (YOU)? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDIeHttTMYHG2NR9URAqkmAJ9baSnkDI7boouPPVH9SxZ7GpBJ9QCffsDQ ow3o+swn//yZ1ZWR22KoMkM= =ocyd -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R.
-
Fergus Wilde
-
Tom Weber