1. ed on XP
- Posted by Robert Craig <rds at RapidEuphoria.com> Dec 18, 2003
- 416 views
Lately I've been doing a lot of editing, converting thousands of lines of C to Euphoria. This is all part of the project to convert the Euphoria "front-end" and translator to Euphoria. I'm noticing that when running ed on XP there's a tiny, almost imperceptible, delay from the time I hit a key to the time it's echoed on the screen. This didn't used to happen on earlier versions of Windows, not even on my old 486 running Windows 3.1, so it's not that Euphoria itself is slow. I'm now running a Pentium-4 and the delay sometimes throws my timing off a bit so I, say, delete an extra character that I didn't intend to, etc. I think Microsoft on XP has chosen to emulate DOS screen I/O in a very slow way. I know on NT they used to introduce an extra process to handle the simulated DOS screen, so the characters that you typed were transmitted from one process to another. Anyway, I've found a really easy solution. Do the following: 1. run: makecon.exw in euphoria\bin You can double-click it. This will create exwc.exe, a console-oriented version of exw.exe. 2. edit euphoria\bin\ed.bat, replacing "ex.exe" with "exwc.exe" Now when you run ed, it will use the Windows console version of Euphoria instead of the DOS version to interpret ed.ex. ed seems to run fine. I'm using a 43-line console window in XP to match the default setting in ed.ex. The slight typing delay is gone, and ed starts up instantly. On older versions of Windows, I think you should stick with ex.exe. Note: you could simply use exw.exe. It's just that you'll have an extra console window on your desktop while you edit. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
2. Re: ed on XP
- Posted by "Greg Haberek" <g.haberek at comcast.net> Dec 19, 2003
- 409 views
I tried this. Now Ctrl+Home and Ctrl+End don't work. I use these a lot. Any solution? Also, I copied ed.bat to edw.bat so i can run with ex.exe or exwc.exe. Just a tip. ----- Original Message ----- From: "Robert Craig" <rds at RapidEuphoria.com> To: "EUforum" <EUforum at topica.com> Subject: ed on XP > > > Lately I've been doing a lot of editing, > converting thousands of lines of C to Euphoria. > This is all part of the project to convert the > Euphoria "front-end" and translator to Euphoria. > > I'm noticing that when running ed on XP > there's a tiny, almost imperceptible, delay from the > time I hit a key to the time it's echoed on the screen. > This didn't used to happen on earlier versions of Windows, > not even on my old 486 running Windows 3.1, so it's > not that Euphoria itself is slow. > I'm now running a Pentium-4 and the delay sometimes > throws my timing off a bit so I, say, delete an extra > character that I didn't intend to, etc. > > I think Microsoft on XP has chosen to emulate DOS > screen I/O in a very slow way. I know on NT they used to > introduce an extra process to handle the simulated > DOS screen, so the characters that you typed were > transmitted from one process to another. > > Anyway, I've found a really easy solution. > Do the following: > 1. run: > makecon.exw > in euphoria\bin > You can double-click it. This will create exwc.exe, > a console-oriented version of exw.exe. > > 2. edit euphoria\bin\ed.bat, replacing "ex.exe" with "exwc.exe" > > Now when you run ed, it will use the Windows console version of > Euphoria instead of the DOS version to interpret ed.ex. > ed seems to run fine. I'm using a 43-line console window in XP > to match the default setting in ed.ex. The slight typing delay > is gone, and ed starts up instantly. > > On older versions of Windows, I think you should stick with ex.exe. > > Note: you could simply use exw.exe. It's just that you'll > have an extra console window on your desktop while you edit. > > Regards, > Rob Craig > Rapid Deployment Software > http://www.RapidEuphoria.com > > > > TOPICA - Start your own email discussion group. FREE! > >
3. Re: ed on XP
- Posted by "Greg Haberek" <g.haberek at comcast.net> Dec 19, 2003
- 411 views
> Still using Ed? Why? > > Arent there plenty of Windows based editors out there? It depends on what I'm doing. When I'm poking around in the command prompt, looking at files, I find that ED is the best, as I can just type "ed filename.ex" then Page Down or Up, or Ctrl+Home or Ctrl+End through the file, then Esc+Q. Its very productive, especially being able to display multiple files side by side. For actual editing, I use MEditor. I'm also writing my own editor, but I've put it on the back burner with most of my other projects. Sometimes I use ED because I feel like being different, too. ~Greg "Be unique, just like everyone else."
4. Re: ed on XP
- Posted by Robert Craig <rds at RapidEuphoria.com> Dec 19, 2003
- 393 views
Greg Haberek writes: > I tried this. Now Ctrl+Home and Ctrl+End don't work. > I use these a lot. Any solution? Use Ctrl+T to move to the top of the file. Use Ctrl+B to move to the bottom of the file. For some reason, with exw in a console, Ctrl+Home generates the same key code as Home, and Ctrl+End generates the same key code as End. It's the same way on Linux. By the way, the F-keys are the same, except for F11 and F12. If you use F12 to insert a comment, you might want to edit ed.ex to have: if platform() = WIN32 then F11 = 343 F12 = 344 else F11 = 389 F12 = 390 end if Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
5. Re: ed on XP
- Posted by Robert Craig <rds at RapidEuphoria.com> Dec 19, 2003
- 401 views
Alexander CARACATSANIS wrote: > I did as above, and now find that hitting F12 displays in the expected > comment notation, with the cursor blinking under the first hyphen. Can I > change ed.ex to make it display the two hyphens, then a space, then the > cursor? It's easy to change the behavior of F12. When you press F12 a sequence of pre-set keystrokes are "fed" into ed. You can edit CUSTOM_KEYSTROKES, as shown below. I guess you just need to remove: & ARROW_DOWN I added the ARROW_DOWN so I could quickly comment out several lines. -------- START OF USER-MODIFIABLE PARAMETERS ----------- -- make your own specialized macro command(s): constant CUSTOM_KEY = F12 constant CUSTOM_KEYSTROKES = HOME & "-- " & ARROW_DOWN Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com