MySQL Bugs: #3282: Editing of certain lines in the mysql history fails

Bug #3282	Editing of certain lines in the mysql history fails
Submitted:	24 Mar 2004 6:38	Modified:	26 Mar 2004 2:30
Reporter:	Jochen Kokemüller	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	4.1.2-alpha-nightly-20040311-log	OS:	Linux (SuSE Linux 9.0)
Assigned to:		CPU Architecture:	Any

Description:
I write the MySQL queries my appliction does into a log-file. I monitor this log-file by a simple "tail -f" when i than copy and paste a long line, i.e. with line breaks to the mysql client using the standard KDE procedure of the middle-mouse-button click i can execute the query. But if i go upwards in the history (i.e. cursor up) and try to edit the line, the cursor jumps arround and even the line disappears.
If i first enter the "line" in xemacs, and copy it then to the mysql client. This does not happen! So i guess "tail -f" produces chars that disturb the client.

How to repeat:
Produce a long SQL-line.
Output it with "tail".
Copy and Paste it to the mysql-client
Use the History of the mysql client!

Suggested fix:
Filter the chars entering into the client.

Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem is not the result of a bug.
For a list of more appropriate places to ask for help using MySQL
products, please visit http://www.mysql.com/support/

Thank you for your interest in MySQL.

Additional info:

Copying text depends on too many factors to be considered MySQL client problem. It may depend on character sets and terminal settins used in both source and target where text is copied.