Menu

#16 width of terminal window is not taken into account

open-fixed
nobody
None
5
2006-02-12
2006-01-05
Max
No

I'm using ysmICQ 2.9.6 in wide X-windows terminal (of
width more than 100 chars). In spite of that ysmICQ
cuts all outgoing message at length 63, e.g. it shows
outgoing messages like

ON> m Somebody my long outgoing message .... bla-b$

while there a lot of space left at the end of the same
line.

I also vote for an option to disable such cutting and
let the outgoing messages spread over as many lines as
needed.

Discussion

  • rad2k

    rad2k - 2006-02-12
    • status: open --> closed-fixed
     
  • rad2k

    rad2k - 2006-02-12

    Logged In: YES
    user_id=429334

    Hi Inpet!

    Thanks for your report. I'm closing the issue though as I
    believe the following will help you overcome the situation.

    You don't mention what input library you are using (ysmICQ
    supports two, readline and getline, getline is bundled
    with ysm and readline is used if the library is installed).

    Given your output and that the line finishes with a $
    character, I believe you're using getline.

    I'd recommend you to install readline in your system and
    refer to ysm's documentation in order to get readline
    working (it should compile with readline support right
    away if the library is found).

    readline shouldn't have the problems you mention.

    I hope that solves your issue and once again, thanks for
    your great comments and support.

    Regards,
    rad2k

     
  • Max

    Max - 2006-02-12

    Logged In: YES
    user_id=806096

    With readline, there is a similar problem.

    It scrolls the entered test to the left. So when I send long
    message it shows the following:

    <...the end of my very long message.

    Moreover, the end of this line is at position 80 despite
    that the width of my terminal is more than 100 chars and
    there is still plenty of space at the right.

     
  • Max

    Max - 2006-02-12
    • status: closed-fixed --> open-fixed
     

Log in to post a comment.