Ticket #743 (assigned enhancement)
No option for hooking up <STDIN> in Padre
| Reported by: | crz | Owned by: | szabgab |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | Run | Version: | 0.50 |
| Keywords: | Cc: |
Description
Hi,
Right now when we are executing code that expects input through <STDIN> file handler there is no option to input the variables. the output window that pops out isn't writable.
I believe this is a must needed feature and believe this would be looked upon by whoever is in charge of the module with needed importance.
Thanks
crz
Change History
comment:2 Changed 2 years ago by crz
- Type changed from defect to enhancement
At first it seemed like this work around also was not happening at my end. So before reporting here I seeked the help of a friend. It turned out that I didn't have Xterm installed. After the installation it worked. Thanks for the help.
However we have a couple of suggestions.
1) My friend's Padre version was older and it had an indication about using xterm but mine which is .50 doesn't have it. Can you add it? It would be easy for novices like me.
2) Also my friend has a suggestion about giving an option for allowing the end user to hook this function to any terminal he has at his end, like say Konsole, instead of hard coding it to the Xterm.
Thanks
crz

The workaround is marking the checkbox Edit/Preferences/Run? Parameters/Use? external window for execution