-
-
Notifications
You must be signed in to change notification settings - Fork 29
Use -NF (no fork) on ldinit during loadup #850
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
nbriggs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. The echo sysout "$1" duplicates the info you'll get when it echoes running: ... with the sysout name.
|
Was that a "merge" or a "squash and merge" ?? It left a merge comment in the log that shouldn't have been there if it was a "squash and merge". |
|
I believe I just clicked merge
… On Jul 20, 2022, at 12:13 PM, Nick Briggs ***@***.***> wrote:
Was that a "merge" or a "squash and merge" ?? It left a merge comment in the log that shouldn't have been there if it was a "squash and merge".
—
Reply to this email directly, view it on GitHub <#850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJMQU2UAE52PO3CN35TVVBFXLANCNFSM54EA5D2Q>.
You are receiving this because you modified the open/close state.
|
|
But after downloading and trying, I still see that message.
… On Jul 20, 2022, at 12:14 PM, Ron Kaplan ***@***.***> wrote:
I believe I just clicked merge
> On Jul 20, 2022, at 12:13 PM, Nick Briggs ***@***.*** ***@***.***>> wrote:
>
>
> Was that a "merge" or a "squash and merge" ?? It left a merge comment in the log that shouldn't have been there if it was a "squash and merge".
>
> —
> Reply to this email directly, view it on GitHub <#850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJMQU2UAE52PO3CN35TVVBFXLANCNFSM54EA5D2Q>.
> You are receiving this because you modified the open/close state.
>
|
|
Worked for me: You don't have your own copy of run-medley somewhere else on your path do you? |
|
For the merges, choose "squash and merge" rather than "merge" -- it should default to the last one you used. |
|
No, I’m going thru the one in the standard place (but I see that GITFNS shows it but can’t do the copy, it’s one level up from the directories).
I don’t see the UNIXCOMM message, but I suppose I thought that the garbled MAKEINIT message would also disappear. But as long as it doesn’t look like an error, that’s OK.
… On Jul 20, 2022, at 12:23 PM, Nick Briggs ***@***.***> wrote:
Worked for me:
--------------
sysout tmp/init.dlinit
running: ldeinit -g 1042x790 -sc 1024x768 -m 256 -NF tmp/init.dlinit
greet: /Users/briggs/Projects/medley/sources/XREM.CM
MAKEINIT.EXPRESSIONSSNSSSsions:SIONS
---- made ----
-rw-r--r-- 1 briggs staff 4973568 Jul 20 12:21 tmp/init-mid.sysout
--------------
You don't have your own copy of run-medley somewhere else on your path do you?
—
Reply to this email directly, view it on GitHub <#850 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJIYLIBICCA44OQANUTVVBG4DANCNFSM54EA5D2Q>.
You are receiving this because you modified the open/close state.
|
|
The garbled MAKEINIT message is because something is writing CR instead of LF when it puts out: |
No description provided.