Date: Fri, 8 Jun 2001 21:40:03 -0700 (PDT) From: Dima Dorfman <dima@unixfreak.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/27972: talk feature Message-ID: <200106090440.f594e3k02273@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/27972; it has been noted by GNATS. From: Dima Dorfman <dima@unixfreak.org> To: sebster@sebster.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/27972: talk feature Date: Fri, 08 Jun 2001 21:37:24 -0700 sebster@sebster.com writes: > > >Number: 27972 > >Category: bin > >Synopsis: losing information with talk > >Description: > Using the talk utility it is possible to communicate to other users, however > if they have something to say that is longer than your buffer you lose the > information without any way to check what was said. > >How-To-Repeat: > Say a lot to somebody in a talk window in a short amount of time. > >Fix: > A very simple fix which would make talk about 1000 times more convenient > (IMHO) would be to flip the windows: put "me" in the bottom, and "him" in > the top window. That way, whether you are on the console or in an xterm, > you can scroll back to see what the other person said. In general, I like this, and the second patch you posted looks good upon visual inspection. I haven't had time to investigate it further, but already have a few questions: * Did you actually test that doing this will allow you to scroll up and see your party's messages? I haven't tested it myself, but have an eerie feeling that it may not work. * What do you think of making this new behavior conditional on a command-line option? Some people may not care for this (e.g., they only use talk for one or two line communications), but may get annoyed at the sudden change of orientation. Thanks, Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106090440.f594e3k02273>