fubukimaru / msxirc Goto Github PK

The client won't work with UNAPI implementations in ROM. It works fine if UNAPI implementation is in RAM or Memory Mapped RAM segment.

This project doesn't have any license associated.

We should discuss it and ask @pterodl if he has any preference. What do you think @ducasp?

I would go for something like GPL 3.

IRC-Hispano is the main server for spanish speaking people. It has been there for a long time.

If you configure MSXIRC to connect to irc.irc-hispano.org it hangs. This has happened since the first version of MSXIRC.
Are we covering everything related to IRC connections? What is this server doing differently?

It redirects you to proxy servers, so maybe this is what is not working correctly.

If you enter to a given channel you're not allowed to send or receive messages. Moreover, the nick list is corrupted.

How to reproduce it:

• Connect to irc.freenode.org
• Join #msx: Everything works alright as expected
• Join #retroinformatica: Cannot write nor receive messages. Nick list corrupted.

Is it possible that it has to do with the channel name length?

In order to offer installation using just the MSX (YEAH! WE DON'T WANT TO USE OUR PCs!) we can create a MSXHub package (https://msxhub.com/).

I propose the following steps:

• Create a github release
• Make a script to build the new MSXHub package in this repo
• Transfer that to MSXHUB repository for pull request

It would be nice that this process is as automated as possible, so that each new release gets published automatically.

A new feature request...

As is, the client won't update the nicklist, it is loaded by the time you enter the channel, and it stays the same no matter how many people leave or enter the channel.

I believe that Pasha didn't plan for this feature in the initial release and at least I won't work on it for now, but just keep it on the wishlist. It will be a tad complicated as it will involve adding and removing entries from the nick list and that might leave "empty" spaces or need moving buffers around, so it is not a trivial task, but I believe it will be a cool feature for a future revision.

If you give a filename / ini filename as parameter for MSXIRC, even though the file is loaded ok and parameters are correctly read, when trying to connect MSXIRC is trying to resolve the filename instead of the server name...

Program is MSX2 or better only, so it should not try to execute on MSX1 and warn about it.

Also, if there is no TCPIP UNAPI available, should just quite and leave an error message about it.

It is possible to exit the program hitting CTRL+C on several places, and it won't return the screen to regular fonts / regular colors and functionality

Program need at least a few mapper segments free and will run without mapper and crash when connecting

Strings are not always meaningful for users, i.e.: No more server control records... And there are a few errors that can be fixed

There is no documentation about how to use the program, it is intuitive on some areas, and not on others, so a text manual would be great