- Oberon - mailman3.inf.ethz.ch

F1 and F2 keys in A2 rev.10272. Was A2 multi-desktop switching vs. Oberon subsystem.
by peter＠easthope.ca 15 Nov '23

15 Nov '23

Michael and all, From: Michael Schierl schierlm at gmx.de, Mon Jul 31 22:19:02 CEST 2023 > In latest gitlab version, you can either disable global hotkeys > completely by pressing the F12 key, or you can edit Hotkeys.xml and > change the hotkeys for desktop switching to anything that does not > interfere with your Oberon usage. rev.9799 and revision.10272 from http://user.informatik.uni-bremen.de/fld/UnixAos/ are installed in Linux Debian on a 64 bit Lenovo ThinkCentre. Three lines in HotKeys.XML differ. Output from Diff.Do is here. http://easthope.ca/Diff.Do.HotKeys.XML.9799.10272.jpg In the Oberon subsystem of 10272, F1 and F2 keys are inactive with the distributed HotKeys.XML. Ie. the three lines are commented out as in the Diff cited above. F1 and F2 remain inactive if the three lines are activated (commented in). That hints that the failure in 10272 is independent of HexKeys.XML. Configuration.XML is updated in 10272. I'm not trying to use the Configuration.XML from 9799 in 10272. So I wonder whether the Oberon subsystem changed from 9799 to 10272. Can anyone confirm that the F1 and F2 keys in the Oberon subsystem of 10272 work or not? Thanks, ... P.L. -- VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Re (2): Removing unnecessary and embedded RETURNs.
by peter＠easthope.ca 13 Nov '23

13 Nov '23

J=F6rg, Thanks for the replies. From: "joerg.straube(a)iaeth.ch" <joerg.straube(a)iaeth.ch> Date: Mon, 13 Nov 2023 05:08:37 +0000 > The idea with the state machine is good. I spent some hours tossing ideas before adopting that. Of course my self-evaluation risks bias. =8~) > I don't understand your remark "ReadText is external to this byte > padding" In my point of view in the ELSE part of state 3 you would > have to strip the stuffed period. Initially, I had exactly the same thought and worked in that direction. Then resorted to empiricism to clarify how "byte stuffing" fit in the process. ReadText takes bytes from the communication link and puts them in the MailMessages file. MailMessages can be examined directly with an editor. It is plain text with lines ending CR LF. According to my tests and observations this is the process. (1) Sending MUA "byte stuffs" the message body. (2) The sending MUA submits to the communication link with End-of-message represented by CR LF "." CR LF. (3) The stream of bytes is transmitted unchanged over the link. (4) The receiving MUA takes bytes from the link and appends to MailMessages until CR LF "." CR LF. The sequence CR LF "." CR LF is included in MailMessages to mark the end of the message. Observe that a byte stuffed line '".." blah blah blah CR LF' is always distinct from end-of-message, CR LF "." CR LF. "Byte stuffing" is a clever idea. =8~) (5) When the recipient requests to see the messge, the receiving MUA extracts it from the MailMessages file and displays with periods "unstuffed". If you have the Mail module working, make a test message containing a line beginning with a period and send it to yourself. Then examine the MailMessages file with an editor. There the line beginning with two periods will be visible. The message is displayed with periods "unstuffed". Here is my summary. (1) "Stuff" any line where the first byte is ".". (2) Submit to transmitting link. (3) ... (4) Receive off the link. (5) "Unstuff" and display. Stuffing and message transfer are distinct. I should have written that stuffing is external to transmission rather than transmission is external to stuffing. ReadText is part of transmission. ReadText should not alter "stuffing". Incidentally "full stop padding" or "period padding" are better terms than "byte stuffing". "Period" is more specific than "byte" and "padding" is more correct than "stuffing". Padding is on the perimeter of something whereas stuffing is inside. From: "joerg.straube(a)iaeth.ch" <joerg.straube(a)iaeth.ch> Date: Mon, 13 Nov 2023 05:37:10 +0000 > As the last line with only =93.CRLF=94 is not considered part of the text, = > you should delay Files.Write(R, ch); in state 3, 4, 5 until you know whethe= > r it=92s the termination case or byte-stuffed case. Explanation above. Stuffing remains in MailMessages. Unstuffing occurs when the message is extracted from MailMessages and displayed. If periods are unstuffed in MailMessages, a message line containing only a period can appear to be end-of-message. =8~/ > the original code does not copy the starting =93.=94 of a line to the file, See above and verify empirically. > copies over the final CRLF. In most cases, this additional CRLF at > the end does not harm but is - strictly speaking - not correct. I agree but suppose a message is submitted ending with these bytes and no folllowing CR LF. The end of my message. My Mail.Sig.Text file contains these two lines. -- My mail signature. If the MUA does not add an end-of-line to separate the message body and signature, these two lines will be transmitted. The end of my message.-- My mail signature. That breaks the signature delimiter syntax from RFC 3676. https://en.wikipedia.org/wiki/Signature_block#Standard_delimiter So we don't know whether a CR LF between the end of the message body and the signature was added by the human sender or by the MUA. The ambiguity is imposed by RFC 3676. I don't know a good resolution but usually end a message body with CR LF. Thanks for the discussion, ... P.L. -- VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Re: [Oberon] Removing unnecessary and embedded RETURNs.
by joerg.straube＠iaeth.ch 13 Nov '23

13 Nov '23

Peter The idea with the state machine is good. One remark: I don’t understand you remark “ReadText is external to this byte padding” In my point of view in the ELSE part of state 3 you would have to strip the stuffed period. In other words: you would have to reposition and copy the Files.Write(R, ch); to almost all your cases br Jörg Von: Oberon <oberon-bounces(a)lists.inf.ethz.ch> im Auftrag von peter(a)easthope.ca <peter(a)easthope.ca> Datum: Sonntag, 12. November 2023 um 15:58 An: oberon(a)lists.inf.ethz.ch <oberon(a)lists.inf.ethz.ch> Betreff: Re: [Oberon] Removing unnecessary and embedded RETURNs. This is my alternative Mail.ReadText with no RETURN. ReportError was helpful in debugging; probably can be deleted now. Apology for the verbose comments. Added to help a non-expert understand the non-obvious activity. =8~) I wonder whether this use of CASE is good practise. Observations? Thanks, ... P.L. PROCEDURE ReportError(c: CHAR); BEGIN Texts.WriteString(W, "Mail.ReadText(): LF absent at CASE "); Texts.Write(W, c); Texts.Write(W, "."); Texts.WriteLn(W); Texts.Append(Oberon.Log, W.buf); HALT(6) END ReportError; (* According to Post Office Protocol, the end of a message body is marked by character sequence CR LF "." CR LF. A message line can begin with a period. To distinguish from end-of-message, the message sender prepends an additional period which is removed before the message is displayed to the recipient. ReadText is external to this byte padding. https://en.wikipedia.org/wiki/Post_Office_Protocol https://tools.ietf.org/html/rfc1939#section-3 *) PROCEDURE ReadText(S: NetTools.Session; VAR R: Files.Rider); VAR buffer: ARRAY BufLen OF CHAR; len, readLen, i: SIGNED32; ch: CHAR; progress: CHAR; (* "0"= continuing "1"= CR "2"= CR LF "3"= CR LF "." "4"= CR LF "." CR "5"= CR LF "." CR LF = end-of-message; or no more characters *) BEGIN readLen := 0; i := readLen; progress := "0"; WHILE progress < "5" DO (* Write byte to the MailMessages file. *) IF i = readLen THEN (* More characters required. *) len := NetSystem.Available(S.C); IF (len = 0) & (NetSystem.State(S.C) # NetSystem.inout) THEN progress := "5" ELSE IF len > (BufLen-2) THEN readLen := BufLen-2 ELSE readLen := len END; NetSystem.ReadBytes(S.C, 0, readLen, buffer); DEC(len, readLen); i := 0 END ELSE (* i < readLen. character available *) ch := buffer[i]; CASE progress OF "0": IF ch = Strings.CR THEN progress := "1" END | "1": IF ch = Strings.LF THEN progress := "2" ELSE ReportError(progress) END | "2": IF ch = Strings.CR THEN progress := "1" ELSIF ch = "." THEN progress := "3" ELSE progress := "0" END | "3": IF ch = Strings.CR THEN progress := "4" ELSE progress := "0" END | "4": IF ch = Strings.LF THEN progress := "5" ELSE ReportError(progress) END END; Files.Write(R, ch); INC(i) END END END ReadText; - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope -- Oberon(a)lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon

1 1

Re: [Oberon] Removing unnecessary and embedded RETURNs.
by peter＠easthope.ca 12 Nov '23

12 Nov '23

This is my alternative Mail.ReadText with no RETURN. ReportError was helpful in debugging; probably can be deleted now. Apology for the verbose comments. Added to help a non-expert understand the non-obvious activity. =8~) I wonder whether this use of CASE is good practise. Observations? Thanks, ... P.L. PROCEDURE ReportError(c: CHAR); BEGIN Texts.WriteString(W, "Mail.ReadText(): LF absent at CASE "); Texts.Write(W, c); Texts.Write(W, "."); Texts.WriteLn(W); Texts.Append(Oberon.Log, W.buf); HALT(6) END ReportError; (* According to Post Office Protocol, the end of a message body is marked by character sequence CR LF "." CR LF. A message line can begin with a period. To distinguish from end-of-message, the message sender prepends an additional period which is removed before the message is displayed to the recipient. ReadText is external to this byte padding. https://en.wikipedia.org/wiki/Post_Office_Protocol https://tools.ietf.org/html/rfc1939#section-3 *) PROCEDURE ReadText(S: NetTools.Session; VAR R: Files.Rider); VAR buffer: ARRAY BufLen OF CHAR; len, readLen, i: SIGNED32; ch: CHAR; progress: CHAR; (* "0"= continuing "1"= CR "2"= CR LF "3"= CR LF "." "4"= CR LF "." CR "5"= CR LF "." CR LF = end-of-message; or no more characters *) BEGIN readLen := 0; i := readLen; progress := "0"; WHILE progress < "5" DO (* Write byte to the MailMessages file. *) IF i = readLen THEN (* More characters required. *) len := NetSystem.Available(S.C); IF (len = 0) & (NetSystem.State(S.C) # NetSystem.inout) THEN progress := "5" ELSE IF len > (BufLen-2) THEN readLen := BufLen-2 ELSE readLen := len END; NetSystem.ReadBytes(S.C, 0, readLen, buffer); DEC(len, readLen); i := 0 END ELSE (* i < readLen. character available *) ch := buffer[i]; CASE progress OF "0": IF ch = Strings.CR THEN progress := "1" END | "1": IF ch = Strings.LF THEN progress := "2" ELSE ReportError(progress) END | "2": IF ch = Strings.CR THEN progress := "1" ELSIF ch = "." THEN progress := "3" ELSE progress := "0" END | "3": IF ch = Strings.CR THEN progress := "4" ELSE progress := "0" END | "4": IF ch = Strings.LF THEN progress := "5" ELSE ReportError(progress) END END; Files.Write(R, ch); INC(i) END END END ReadText; - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Removing unnecessary and embedded RETURNs.
by peter＠easthope.ca 11 Nov '23

11 Nov '23

Hi, Mail in ETH Oberon has many RETURNs which are unnecessary or embedded in a procedure body. Some procedures offer a challenge, to me at least. This is one. Comprehending how the intended purpose is accomplished was difficult. In a day or two, will post an alternative. PROCEDURE ReadText(S: NetTools.Session; VAR R: Files.Rider); VAR buffer: ARRAY BufLen OF CHAR; len, rlen, i, offs: SIGNED32; state: SIGNED16; ch, old: CHAR; BEGIN old := 0X; offs := 1; len := NetSystem.Available(S.C); state := NetSystem.State(S.C); WHILE (len > 0) OR (state = NetSystem.inout) DO IF len > (BufLen-2) THEN rlen := BufLen-2 ELSE rlen := len END; NetSystem.ReadBytes(S.C, 0, rlen, buffer); i := 0; WHILE i < rlen DO ch := buffer[i]; IF ch = Strings.CR THEN Files.Write(R, ch); IF (offs = 2) & (old = ".") THEN Files.Write(R, Strings.LF); RETURN END; offs := 0 ELSE IF (offs > 0) OR (ch # ".") THEN Files.Write(R, ch) END; INC(offs) END; old := ch; INC(i) END; DEC(len, rlen); IF len <= 0 THEN len := NetSystem.Available(S.C); state := NetSystem.State(S.C) END END END ReadText; - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Oberon keyboard tweaks
by Hans Klaver 07 Nov '23

07 Nov '23

Hi all, Have you ever felt the desire to use the arrow keys while editing text or playing ObTris (Oberon Tetris) in Project Oberon 2013? Or wondered how to make changes to the keyboard code translation table in Input.Mod? I did, and I noticed that making such changes is not entirely trivial. So after fiddling with this for some time and succeeding to make most of the tweaks that I needed I wrote a small Tutorial on this. You can find it here: https://github.com/hansklav/Oberon-keyboard-tweaks Hoping it will useful to others, With regards, Hans Klaver

8 14

NetSystem.Available and NetSystem.State.
by peter＠easthope.ca 06 Nov '23

06 Nov '23

Hi, Oberon NetSystem is visible here. https://gitlab.inf.ethz.ch/felixf/oberon/-/blob/main/source/Unix.Oberon.Net… Eight constants are declared for the return values of State. According to the response from TCP, State can return four of those values. State is unable to return in, out, waitCon and errorCon. I wonder about use of the return values not included in State. NetTools.Connected is a pertinent example. (** Check if connection C is still open for incoming (mode = NetSystem.in) or outgoing (mode = NetSystem.out) data. *) PROCEDURE Connected*(C: NetSystem.Connection; mode: SIGNED16): BOOLEAN; VAR state: SIGNED16; BEGIN state := NetSystem.State(C); RETURN state IN {mode, NetSystem.inout} END Connected; The local state will never be assigned NetSystem.in or NetSystem.out. Therefore "RETURN state IN {mode, NetSystem.inout}" simplifies to "RETURN state = NetSystem.inout". Correct? Did the author of NetSystem include in, out, waitCon and errorCon to allow for a future generalization? Other ideas? Thanks, ... P.L. - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Line wrapping. Was "Oberon keyboard tweaks"
by peter＠easthope.ca 04 Nov '23

04 Nov '23

August Karlstrom fusionfile at gmail.com Thu Nov 2 19:38:35 CET 2023 > Talking about text editing, is there a command in Oberon for wrapping > paragraphs of text? I can't imagine having to insert manual line > breaks in the right places when editing a paragraph of text, and > having to reach for the mouse in between. From: Chris Burrows <cfbsoftware(a)gmail.com> Date: Sat, 4 Nov 2023 08:14:22 +1030 > Do you mean 'word processing' rather than 'text editing'? Oberon has > different tools designed to suit each activity. Chris, suppose you open Edit or ET and put a "word" such as this in an empty file. 123456789 Copy the characters more than a dozen times so you have something similar to this. 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 =8~/ Here in A2 > Oberon, ET the line runs off the viewer on the right. I can break the line and see this. 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 Then all the characters are visible. =8~) In an editor which auto-wraps, a non-issue. Mail.CutLines was provided to break long lines in email messages into visible lengths; correct? Reading email isn't it? Nobody calls it word processing. I found CutLines useful outside email but Wrap may not be needed. Is wrapping available other than CutLines and Wrap? Thx, ... P.L. - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Re: [Oberon] Mail.Wrap. Was "Oberon keyboard tweaks"
by peter＠easthope.ca 03 Nov '23

03 Nov '23

From: August Karlstrom <fusionfile(a)gmail.com> Date: Thu, 2 Nov 2023 19:38:35 +0100 > Talking about text editing, is there a command in Oberon for wrapping > paragraphs of text? https://en.wikibooks.org/wiki/Oberon/A2/Oberon.Mail.Mod#Wrap A spin off from the precursory Mail.CutLines rmaining in the module. I was motivated by a bug and a limitation in CutLines. Mail.Wrap still doesn't handle non-character entities. A gerealized Text.Wrap would be better. If you use Wrap and find a problem, please let me know. Thx, ... P.L. - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0

Re: [Oberon] Oberon keyboard tweaks
by peter＠easthope.ca 03 Nov '23

03 Nov '23

From: August Karlstrom <fusionfile(a)gmail.com> Date: Thu, 2 Nov 2023 19:38:35 +0100 > Talking about text editing, is there a command in Oberon for wrapping > paragraphs of text? https://en.wikibooks.org/wiki/Oberon/A2/Oberon.Mail.Mod#Wrap A spin off from the precursoy Mail.CutLines rmaining in the module. I was motivated by a bug and a limitation in CutLines. Mail.Wrap still doesn't handle non-character entities. With that added Text.Wrap would be more appropriate than Mail.Wrap. If you use Wrap and find a problem, please let me know. Thx, ... P.L. - VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:PeterEasthope

1 0