a218@mindlink.UUCP (Charlie Gibbs) (09/05/90)
In article <david.7294@starsoft.UUCP> david@starsoft.UUCP (Dave Lowrey) writes: >6. A more complete pattern matching ability. Inclusion of such 'wild cards' > as ^ for start of line and $ for end of line would really help. Ideally, > full regular expressions are needed. I can't help with the other stuff, but try substituting control-J (the newline character) for the ^ or $ you've mentioned above. Works fine for searching for or replacing strings at the beginning or end of a line. Charlie_Gibbs@mindlink.UUCP Intel puts the "backward" in "backward compatibility."
david@starsoft.UUCP (Dave Lowrey) (09/05/90)
I am posting this wish list of things that I would like to see changed or
added to CygnusEd Pro 2.0 in the hopes that someone conected with it's
development will see it.
I am also mailing (U.S.Snail) a copy to ASDG Inc.
1. The editor appears to require a contiguous chunk of memory to store
the file in. This can be a problem with large files, or in fragmented
memory situations. I have a file that I can only edit when I first
boot my system. If I have made a few things resident, or am running
something, it won't load the file. DME (Matt Dillon's PD editor) WILL
load the file, so I must have enough total memory avaliable.
2. Have CED load appropriate configuration files whenever it is activated,
and there are no active buffers. Now, I have F3 set to "Quit and Die" so
that I can have a different configuration file loaded when I use ED.
The "startup" script should be run every time ED is executed, not just
when CED is first activated.
The reason I need this is that I edit different types of files at
different times. I have different configuration files for each
file type (.c, .h, etc). CED only loads the configuration file
automayically when it is FIRST activated.
3. Allow the specification of configuration files on the ED command line.
This would be nice for commands that call "pagers" or "editors". Being
able to specify a configuration file on the command line would allow
those invocations to use their own configurations.
4. You should have a facility that allows "script" files to be written
in plain text.
5. Allow AREXX scripts to specify key bindings.
6. A more complete pattern matching ability. Inclusion of such 'wild cards'
as ^ for start of line and $ for end of line would really help. Ideally,
full regular expressions are needed.
7. Allow "mouse buttons" to be part of the key qualifiers (i.e.
Left_Button-Shift-A = foobar).
8. The ability to "read" your current key bindings.
I am sure there are a few things I have forgotten, but this list covers
the basics.
CygnusEd Pro is a good editor. However, if my suggestions are added, it
would be even better.
Dave Lowrey
--
----------------------------------------------------------------------------
These words be mine. The company doesn't care, because I am the company! :-)
Dave Lowrey | david@starsoft or {uhnix1,moray}!starsoft!david
Starbound Software Group |
Houston, TX | "Dare to be stupid!" -- Weird Al Yankovic