Author Topic: MeShell commandline frontend timetable  (Read 3390 times)

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 22
  • Posts: 487
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #30 on: May 21, 2020, 04:28:09 pm »
I read netlabs groups via Seamonkey newsreader since ages. Guess every news reader will handle it. NNTP, server name - news.gmane.org, port 119

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 169
  • Posts: 2423
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #31 on: May 21, 2020, 04:59:12 pm »
Gmane stopped working here some time back, just tried with SM and it timed out. I'm subscribed to the mailing list, which is low volume. Start here, http://www.netlabs.org/site/community.xml

Heikki Kekki

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #32 on: May 22, 2020, 08:27:13 am »
Gmane stopped working here some time back, just tried with SM and it timed out. I'm subscribed to the mailing list, which is low volume. Start here, http://www.netlabs.org/site/community.xml
I use ProNews/2 and recall Gmane didn't work for few days some time back. Latest post I see in gmane.org.netlabs.community:
Code: [Select]
Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail
From: Andreas Schnellbacher <---@------.------.>
Newsgroups: gmane.org.netlabs.community
Subject: Re: svn dead - Trac works
Date: Mon, 27 Apr 2020 17:50:54 +0200
« Last Edit: May 22, 2020, 08:46:23 pm by Martin Iturbide »

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 169
  • Posts: 2423
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #33 on: May 22, 2020, 08:35:27 am »
Still timing out here, though I admit I seldom try. Last message is 3 years and 3 days old that I see.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 26
  • Posts: 503
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #34 on: May 22, 2020, 09:12:37 am »
Heikki, could you remove my email address from above?

Edit on 18:20 GMT: I've just written an email to the admin.
« Last Edit: May 22, 2020, 08:21:01 pm by Andreas Schnellbacher »

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 43
  • Posts: 964
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #35 on: May 22, 2020, 03:01:44 pm »
Hi All

Yes, Andi, those are the settings in use for news.gmane and, like Dave, all I ever see is a response that tells me connection timed out.

Why would news.gmane work for some people but give a "connection timed out" to others?


Regards

Pete

Martin Vieregg

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 5
  • Posts: 200
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #36 on: May 22, 2020, 03:24:36 pm »
(subject: contact to 4os2 authors)
Silvan Scherrer told me the e-mail address of Andreas Buchinger, but I did not receive an answer. Does anyone has contact to Steven Levine?

Martin Vieregg

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 5
  • Posts: 200
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #37 on: May 22, 2020, 04:40:20 pm »
I have found a suspect behaviour of MeShell and Info-Zip

Code: [Select]
[C:\] zip<RETURN>
  adding: -

zip error: Interrupted (aborting)
(wild binary characters)

In the log file, it is seen that "ZIP^M^J" is sent correctly to cmd.exe, without added spaces. I have no idea at all what happens here.

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 22
  • Posts: 487
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #38 on: May 22, 2020, 04:46:32 pm »
Hi All

Yes, Andi, those are the settings in use for news.gmane and, like Dave, all I ever see is a response that tells me connection timed out.

Why would news.gmane work for some people but give a "connection timed out" to others?


Regards

Pete
Sorry you're right. gmane newsgroups don't work here anymore too. Just tested and it timed out. Previously I though it works cause usually all my newsgroups are read at startup and I did not get any error message.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 26
  • Posts: 503
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #39 on: May 22, 2020, 08:17:14 pm »
Forget about gmane. They won't come back. It's dead since a long time. They managed to restore a part, but not the netlabs.org tree.

Mailing lists exist on netlabs.org, but according to Martin V., registration isn't possible ATM. I am subscribed to many netlabs.org mailing lists, hence my posting.

Laurence Pithie

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 57
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #40 on: May 22, 2020, 08:24:48 pm »
Code: [Select]
[C:\] zip<RETURN>
  adding: -

zip error: Interrupted (aborting)
(wild binary characters)
When I try to  compress stdin in version 0.63 of MeShell the EOF doesn't seem to reach the zip process, so I have to use ctrl-c to interrupt the process. Is that the behaviour you are seeing?

 AFAIR you are using a named pipe to communicate between the parent process and the cmdhelper process. So, if you write an EOF to the named pipe from the parent, reading the EOF in the cmdhelper process is interpreted as  there's no data in the pipe, so it doesn't write anything to the standard input of the zip process.
Code: [Select]
[C:\]cat <RETURN>
Shows the same behaviour, Typing the EOF character (ctrl-z) doesn't end the CAT process, it's ignored. The simplest work around  is probably to use a semaphore to indicate to the cmdheloer process that it should write an EOF to the standard input of the command running in the shell when the user types ctrl-z in the parent application.

Martin Vieregg

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 5
  • Posts: 200
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #41 on: May 22, 2020, 11:00:23 pm »
I have contact now with the second 4os2 author Andreas Buchinger. I think now I will manage the changes I need for MeShell. Thank you.

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 169
  • Posts: 2423
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #42 on: May 23, 2020, 02:44:21 am »
I have found a suspect behaviour of MeShell and Info-Zip

Code: [Select]
[C:\] zip<RETURN>
  adding: -

zip error: Interrupted (aborting)
(wild binary characters)

In the log file, it is seen that "ZIP^M^J" is sent correctly to cmd.exe, without added spaces. I have no idea at all what happens here.

Are you opening your pipe in binary mode?

Martin Vieregg

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 5
  • Posts: 200
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #43 on: May 23, 2020, 10:50:21 am »
The zip.exe pipe problem is not related to MeShell. This results in a normal commandline window:

Code: [Select]
[C:\]zip >out.txt
  adding: -              (now pressing Ctrl-C)

zip error: Interrupted (aborting)

[C:\]do which zip
H:\SOFTWARE\SHARE\PATH\zip.exe (219 kB;14.08.2010 03:11)
C:\USR\BIN\zip.exe (107 kB;20.02.2018 15:56)

[C:\]C:\USR\BIN\zip.exe >out.txt
  adding: -              (now pressing Ctrl-C)

zip error: Interrupted (aborting)

[C:\]type out.txt
(binary nonsens characters)               
[C:\]

It seems to be an Info-Zip bug. Unzip works. Windows zip.exe has the same buggy behaviour.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 26
  • Posts: 503
    • View Profile
Re: MeShell commandline frontend timetable
« Reply #44 on: May 23, 2020, 06:03:03 pm »
No, it's not a bug. From zip --help:

If zipfile and list are omitted, zip compresses stdin to stdout.