-
Notifications
You must be signed in to change notification settings - Fork 17
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
Multiple executions in IRB causes error #45
Comments
Please use It automatically requires the Also, it allows opening a window multiple times with no practical problem. The only known issue it suffers from is when you close the window (via x button or by quitting), it keeps the window open, but if you re-open the window with different title/content, the new title/content shows up, so it's not a problem practically speaking. Otherwise, you have another option for playing around with Glimmer DSL for LibUI applications. Start the Glimmer Meta-Example (via I believe both options above should address your concerns/goals, so I am closing this issue. But, if you still have issues or you have other comments to share, please reply or even re-open the issue if needed. |
Sorry for resurrecting this, but I don't think this fixes my issue. At least, repeating the issue in
Typing in the example I gave above, the second invocation (even with new contents) doesn't render. I am able to start multiple applications from the meta-example viewer, but it doesn't really solve the issue of not being able to use them in IRB. |
You do not have to be sorry for resurrecting this. However, this might just be a Linux-only issue as it works fine on my Mac. I didn't think of testing on Linux. I'm sorry about this. I will take a look when I get a chance. By the way, by "should address your concerns/goals", I meant addressing the ultimate goal behind using both IRB and Meta-Example, which is to be able to prototype Ruby Glimmer apps quickly. To me personally, the Meta-Example is good enough in addressing that goal/concern to the point that I rarely use IRB. Sometimes, it is a good idea to step back and realize that a certain tool is not needed if there are better alternatives that address the same goals behind it, and I sometimes have to discipline myself against using a certain popular tool (letting go of attachment to it) if I have other more effective tools at my disposal. Otherwise, I would be hurting productivity in finishing apps for customers unnecessarily. But, perhaps there is a goal for why to use IRB that the Meta-Example does not address, like being able to go up in the command history to re-run previous commands. So, I will still look into the issue on Linux to figure out if there is a fix for it. And, I hope that the Meta-Example could address part of your goal/concern in the meantime until the IRB issue is resolved if possible. |
Thanks - let me know if there's anything you want me to help/test on my end.
That makes sense, each person works differently. The project I'm working on relies on communicating with several live connections which are best handled interactively, hence IRB. |
That makes sense. Sounds good. I’ll let you know if I need any help. I haven’t had a chance to take a look on Linux yet, but I’ll let you know as soon as I have. |
I was able to reproduce and confirm this issue on Linux. I could not come up with a fix for it yet, but if I do in the future, you will hear of it here. |
When running a simple example in IRB, I get a weird result where running a program multiple times causes the second invocation to make an empty window.
Here's an example interaction:
This looks like an analogue of this issue in the underlying LibUI bindings.
I'm using Debian GNU/Linux 6.1.0-6-amd64, ruby 3.1.2p20, XOrg Version: 1:7.7+23 and dwm-6.2.
The text was updated successfully, but these errors were encountered: