Bug 78068 - long filenames and terminal overwrite
long filenames and terminal overwrite
Product: Red Hat Linux
Classification: Retired
Component: ncftp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-11-18 12:21 EST by Ben Woodard
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-18 12:21:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ben Woodard 2002-11-18 12:21:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When I try to get a long file name. Once it is completed the ncftp program
doesn't clear the line properly when scrolling the filename over.

ncftp ...pdates/7.3/en/os/SRPMS > ls ker*
kernel-2.4.18-17.7.x.src.rpm           kernel-2.4.18-18.7.x.src.rpm
ncftp ...pdates/7.3/en/os/SRPMS > $c.rpm nel-2.4.18-18        

What is wrong in this picture is the last line. When I gave it enough to
complete kernel-2.4.18-18.7.x.src.rpm it wrote that and scrolled the line over
so that only the "c.rpm" is visible. That is fine. However, it forgot to erase
the rest of the filename from the terminal screen.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. connect to some ftp server with deep paths and long filenames e.g. ftp.redhat.com
2. go down a deep path e.g. the updates directory for a particular release of a
3. tab complete a file

Actual Results:  ncftp ...pdates/7.3/en/os/SRPMS > $c.rpm nel-2.4.18-18        

Expected Results:  ncftp ...pdates/7.3/en/os/SRPMS > $c.rpm

Additional info:
Comment 1 Ben Woodard 2002-11-18 12:33:05 EST
Nevermind. I tested it with the 7.3 version of ncftp and it seems to work fine.

Note You need to log in before you can comment on or make changes to this bug.