OpenEuphoria

1. More Manual Typo/errors

• Posted by K_D_R Nov 16, 2015
• 1911 views

Forked from Re: manual typo for public function gcd(atom p, atom q)

In the manual discussion of maybe_any_key The Two examples given appear to have been copied from the previous entry for "any_key" without prepending "maybe_"

Also, the program "regexps.ex" in the demo folder uses "maybe_any_key" consequently the program does not pause as needed under Linux.

-- in the demo program regexps.ex change: 
-- maybe_any_key() 
-- to: 
ifdef UNIX  then 
any_key() 
elsifdef WINDOWS then 
maybe any_key() -- Requires Windows XP or later or Windows 2003 or later to work 
end ifdef 

Ken

3. Re: More Manual Typo/errors

• Posted by K_D_R Nov 19, 2015
• 1819 views

"Suppose we can figure out how to do so.."?? Shawn, you have lost the plot completely. A number of LINUX editors have supported the use of a terminal for years. Even before terminal support was added to WEE I simply ran WEE from a command line in a terminal, loaded the console program I was editing in the editor and then, once I executed the console program, I switched back to the terminal window to see the console programs output. This worked fine because my console program required a key press to exit. The latest version of WEE supports execution of a console program in a terminal - which works for some console programs, but not for other console programs such as the demo, "regexps.ex" which only works as expected in a GUI's terminal, provided you ask for a key press in order to keep the program from terminating instantly.

We should not assume that Unix console programs are run from the console - especially euphoria demo programs. GUI editors with terminal support are now ubiquitous. It is likely that a new user will use a GUI Editor to explore Euphoria's demo programs. Console demo programs can easily be easily adapted to run from a GUI editor at the cost of one command asking for a key press - which places no onerous burden on any user who executes the console demo directly from the console.

-- in the demo program "regexps.ex" 
-- replace line: 
-- maybe_any_key() -- This command is absolutely useless!!!! 
-- with: 
any_key("\nPress Any Key to Exit") 

5. Re: More Manual Typo/errors

• Posted by jimcbrown (admin) Nov 19, 2015
• 1856 views

The difference is that the stupid operating system provides a concept of a console subsystem vs a GUI subsystem. Consoles simply work differently there, and it's relatively simple to determine if a Windoze console is in use or not. This is what maybe_any_key() uses.

On nix, it's not trivial to determine if a process is running directly inside an xterm or similar program, as opposed to running inside of an ssh or telnet or rlogin session, or in something like GNU screen.

I think the consensus is that, under nix, since the IDE is the one that knows if it started the child process inside of an xterm or not (unlike process itself), it should be the one responsible for keeing that xterm alive after the process ends.

Then these GUI editors should support an option like "Run via xterm - keep xterm alive after process ends" or a similar setting.

If you are fond of a particular editor that does not support this sort of setting, there are also workarounds you can use. E.g. http://stackoverflow.com/questions/3512055/avoid-gnome-terminal-close-after-script-execution

Alternatively, we could come up with an euiw for nix, where the only difference from eui is that the nix euiw simply always returns 0 for has_console(). Then set up the editor to run code with euiw instead of eui.

-- in the demo program "regexps.ex" 
-- replace line: 
-- maybe_any_key() -- This command is absolutely useless!!!! 
-- with: 
any_key("\nPress Any Key to Exit") 

Right, but if someone is running it from the command line directly, via a getty session (outside of X), then pausing here is probably the wrong thing to do - it's unnecessary since you won't lose output after the key press. Ditto if I'm running the program directly on the command line.

That said, if someone has a patch or some code that can, under Linux/GNU, determine if a process is running under an xterm or something, I'm not necessarily opposed to reviewing it and including it. It's just not a very easy thing to do.

7. Re: More Manual Typo/errors

• Posted by SDPringle Nov 21, 2015
• 1829 views

A switch could be added to the std/console.e to make this kind of thing work the way it should

ifdef NO_CONSOLE then 
    public function has_console() 
        return 0 
    end function 
elsedef 
    public function has_console() 
        -- stuff that is there now 
    end function 
end ifdef 

Then in the GUI settings you put:

gnome-terminal -command 'eui -D NO_CONSOLE $filename' 

9. Re: More Manual Typo/errors

• Posted by SDPringle Dec 02, 2015
• 1620 views

Can someone make this into a ticket please...

11. Re: More Manual Typo/errors

• Posted by jimcbrown (admin) Dec 02, 2015
• 1586 views

While some workarounds that could be implemented in euphoria were discussed, I think the undisputed and correct solution remains to fix the IDE to add the required prompt, instead of changing how maybe_any_key() works.