nc-ng fails to start.

[eteran]

nc-ng fails to start.

[eteran]

Let me look into this, my implementation uses Qt's local sockets instead of X based message passing. Is nedit-ng in your PATH? are you running as an ordinary user or as root?

Also, does the following work?

nc-ng -svrcmd /mnt/Softs/local/nedit-ng/build/nedit-ng

(Assuming that's where your nedit-ng binary is as well)

[eteran]

BTW: thank you for feedback on this project! Nothing is ever perfect, but every little bit of feedback helps get things closer.

[ericxuo]

Hi,

No, nedit-ng was not in my path. I accessed it using a full path. As I considered it was still a debug process, I didn't add it in the PATH env var.
Yes , the command /mnt/Softs/local/nedit-ng/build/nc-ng -svrcmd /mnt/Softs/local/nedit-ng/build/nedit-ng
worked fine.
Then, I have added nedit-ng in the PATH env var and now running nc-ng works fine.

I am a great fan of nedit. So I'm glad to see other people working on it, and to help if I can.
By the way, I have a (stupid ?) question : it is painful to use nedit under Windows. Will nedit-ng be easier to use ?

Regards.

Xuo.

[eteran]

OK, so this seems to be simply a PATH issue. The original nedit uses the system libc function to execute the server, which also searches the PATH (as far as I know). So I'm going to close this bug.

I suppose it is worth looking a good way to have it look for the nedit-ng binary in the same directory as the nc-ng binary if it's not in the PATH though.

Now, on to your question :-).

I plan for nedit-ng to have native support for running on both Windows and macOS! But it's not there yet, the code still has a few (relatively minor) usages of POSIX APIs that will need to be reworked. But you can expect that after the first major release, that I will have non-linux platforms in the works :-).