I have a strange problem. From my desktop (FC3/KDE) I can ftp from Konsole to my FC3 servers and the up arrow shows my command history and the backspace key moves you back a space like expected. However, when I ftp from my linux servers to another ftp server, the up arrow gives me '^[[A'. In addition, a coworker with a Windows desktop sees the same behavior but also loses his backspace ability when ftp'ing from the linux servers. My backspace works fine. He is always connecting to the servers through secureCRT. Can anyone offer any insight as to why this happens and how to correct it? Not having history in ftp is annoying.
Thanks,
Brad
On Friday 1 July 2005 10:42, brad wrote:
I have a strange problem. From my desktop (FC3/KDE) I can ftp from Konsole to my FC3 servers and the up arrow shows my command history and the backspace key moves you back a space like expected. However, when I ftp from my linux servers to another ftp server, the up arrow gives me '^[[A'. In addition, a coworker with a Windows desktop sees the same behavior but also loses his backspace ability when ftp'ing from the linux servers. My backspace works fine. He is always connecting to the servers through secureCRT. Can anyone offer any insight as to why this happens and how to correct it? Not having history in ftp is annoying.
The problem is related to the 'readline' library and its initialization file stored in /etc/inputrc on your FC3 server. In most distributions there are some comments in that file that explain how to change things. Many console applications make use of readline most notably /bin/bash. Here is my /etc/inputrc ------------------------>8---------------------------------------------- # /etc/inputrc - global inputrc for libreadline # See readline(3readline) and `info rluserman' for more information.
# Be 8 bit clean. set input-meta on set output-meta on
# To allow the use of 8bit-characters like the german umlauts, comment out # the line below. However this makes the meta key not work as a meta key, # which is annoying to those which don't need to type in 8-bit characters.
# set convert-meta off
# try to enable the application keypad when it is called. Some systems # need this to enable the arrow keys. # set enable-keypad on
# see /usr/share/doc/bash/inputrc.arrows for other codes of arrow keys
# do not bell on tab-completion # set bell-style none
# some defaults / modifications for the emacs mode $if mode=emacs
# allow the use of the Home/End keys # "\e[1~": beginning-of-line # "\e[4~": end-of-line
# allow the use of the Delete/Insert keys # "\e[3~": delete-char # "\e[2~": quoted-insert
# mappings for "page up" and "page down" to step to the beginning/end # of the history # "\e[5~": beginning-of-history # "\e[6~": end-of-history
# alternate mappings for "page up" and "page down" to search the history "\e[5~": history-search-backward "\e[6~": history-search-forward
# # mappings for Ctrl-left-arrow and Ctrl-right-arrow for word moving "\e[5C": forward-word "\e[5D": backward-word "\e\e[C": forward-word "\e\e[D": backward-word
# $if term=rxvt # "\e[8~": end-of-line # $endif
# for non RH/Debian xterm, can't hurt for RH/DEbian xterm "\eOH": beginning-of-line "\eOF": end-of-line
# for freebsd console # "\e[H": beginning-of-line # "\e[F": end-of-line
$endif
On Fri, 2005-07-01 at 11:30 -0500, Jason Clinton wrote:
The problem is related to the 'readline' library and its initialization file stored in /etc/inputrc on your FC3 server. In most distributions there are some comments in that file that explain how to change things. Many console applications make use of readline most notably /bin/bash. Here is my /etc/inputrc
I thought that was the case also, but my /etc/inputrc files are identical....same size and everything. That makes sense because they are both FC3. I was thinking that maybe KDE added an environment variable that makes it work on the desktop and not on the server.
Thanks,
Brad
Hi,
On Fri, Jul 01, 2005 at 01:19:07PM -0500, brad wrote:
I thought that was the case also, but my /etc/inputrc files are identical....same size and everything. That makes sense because they are both FC3. I was thinking that maybe KDE added an environment variable that makes it work on the desktop and not on the server.
On the desktop machine look for a ~/.inputrc file.
On Fri, 2005-07-01 at 23:27 -0500, Uncle Jim wrote:
Hi,
On Fri, Jul 01, 2005 at 01:19:07PM -0500, brad wrote:
I thought that was the case also, but my /etc/inputrc files are identical....same size and everything. That makes sense because they are both FC3. I was thinking that maybe KDE added an environment variable that makes it work on the desktop and not on the server.
On the desktop machine look for a ~/.inputrc file.
There is one buried in ~/.kde but this is all that it contains:
[Mouse] Acceleration=1.8 MouseButtonMapping=RightHanded ReverseScrollPolarity=false Threshold=4
That doesn't look like anything that would cause the up arrow to bring up history.
Thanks,
Brad
What is the shell you are using on the servers? If you are using bash, what does "shopt" show on the servers? Maybe history is turned off on the servers at the shell level? What is the ftp package used on the servers? Is it different from the ftp package used on the servers? Have you tried installing ncftp as a client on the servers?
HTH, Brian J. Densmore
--- brad wrote:
I have a strange problem. From my desktop (FC3/KDE) I can ftp from Konsole to my FC3 servers and the up arrow shows my command history and the backspace key moves you back a space like expected. However, when I ftp from my linux servers to another ftp server, the up arrow gives me '^[[A'. In addition, a coworker with a Windows desktop sees the same behavior but also loses his backspace ability when ftp'ing from the linux servers. My backspace works fine. He is always connecting to the servers through secureCRT. Can anyone offer any insight as to why this happens and how to correct it? Not having history in ftp is annoying.
Thanks,
Brad
Kclug mailing list [email protected] http://kclug.org/mailman/listinfo/kclug
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com