Re: Couple of nits about Cygwin

[Kazuhiro Fujieda <fujieda@jaist.ac.jp>]

>>> On Tue, 25 Jul 2000 21:37:50 -0400
>>> Chris Faylor <cgf@cygnus.com> said:

> The change below just moves your code to the input part of cygwin rather
> than the output.  It seems to work as well as putting it in the write
> part.

I'm afraid I don't like this solution. I'm annoyed with the
cursor flushing every time I type something. I prefer solving
this problem in the configuration of readline included in bash
as the following. This solution makes the cursor flush on using
the right arrow key.

--- bash/lib/readline/rlconf.h-	Fri Jul 28 08:03:08 2000
+++ bash/lib/readline/rlconf.h	Fri Jul 28 08:11:11 2000
@@ -45,7 +45,7 @@
 
 /* If defined, use the terminal escape sequence to move the cursor forward
    over a character when updating the line rather than rewriting it. */
-/* #define HACK_TERMCAP_MOTION */
+#define HACK_TERMCAP_MOTION
 
 /* The string inserted by the `insert comment' command. */
 #define RL_COMMENT_BEGIN_DEFAULT "#"

____
  | AIST      Kazuhiro Fujieda <fujieda@jaist.ac.jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com