seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

zsh: user-defined signal 1 ko <FILENAME> #743

New Issue
Closed
opened 2022-07-25 13:00:10 +02:00 by xyproto · 1 comment
xyproto commented 2022-07-25 13:00:10 +02:00 (Migrated from github.com)
Copy Link

Hi,

When I launch the editor ko to open a file, it works fine under Alacritty or Konsole, but crashes under cool-retro-term.

Steps to reproduce the issue.

  1. Install the O editor (o and ko executables) from this project: https://github.com/xyproto/o
  2. Launch ko to open any file, like for example ko .zshrc or ko .Xdefaults.
  3. Observe the user-defined signal 1 error message.
  4. Observe that it works in other terminal emulators.

Expected behavior:

  • To launch the ko GTK GUI.

Speculations:

  • This could have something to do with the USR1 signal. ko launches o and then sends the USR1 signal to it, and the error message mentions user-defined signal 1.

Thanks for creating cool-retro-term! It has a relaxing and nostalgic feel, to me, that is hard to reproduce with any other terminal emulator.

Hi, When I launch the editor `ko` to open a file, it works fine under Alacritty or Konsole, but crashes under `cool-retro-term`. Steps to reproduce the issue. 1. Install the O editor (`o` and `ko` executables) from this project: https://github.com/xyproto/o 2. Launch `ko` to open any file, like for example `ko .zshrc` or `ko .Xdefaults`. 3. Observe the `user-defined signal 1` error message. 4. Observe that it works in other terminal emulators. Expected behavior: * To launch the `ko` GTK GUI. Speculations: * This could have something to do with the USR1 signal. `ko` launches `o` and then sends the `USR1` signal to it, and the error message mentions `user-defined signal 1`. Thanks for creating `cool-retro-term`! It has a relaxing and nostalgic feel, to me, that is hard to reproduce with any other terminal emulator.
xyproto commented 2022-07-25 13:10:32 +02:00 (Migrated from github.com)
Copy Link

Never mind, it happens in other terminal emulators too, when ko is run the second time.

Never mind, it happens in other terminal emulators too, when `ko` is run the second time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#743
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?