Article View: comp.os.os2.programmer
Article #2090Re: Programmer's Editors
From: David Charlap
Date: Thu, 15 Oct 1992 18:15
Date: Thu, 15 Oct 1992 18:15
59 lines
3052 bytes
3052 bytes
In article <sal8.64.0@po.cwru.edu> sal8@po.cwru.edu (Steve Luzynski) writes: >I've got some stuff on the list already: >Autoindent (of course) Autoindent should be with various operating modes for different languages (like Emacs does). I like the fact that when I edit C code, the indents follow the braces and parentheses. With lisp code, the indenting is different, etc. If you could find a simply way to define various indenting modes, the modes could be user-definable. I can work with you to come up with a working protocol for specifiying user-defined indent schemes. >Split windows on the same or different files in 1 instance of the editor Two different ways should be allowed: A separate MDI window or a split point. Excel does this. You cal either drag a "split" marker across a scroll bar to split an existing window or you can open a second window onto the same file. >drag 'n drop editing If you wish. I do think that button-2 over a piece of selected text should pop up a menu of commonly used options. Perhaps a user-selectable subset of program commands. >pick yer own colors Use either the color/font palettes or a notebook of settings. Actually, a settings notebook would be a great idea for all options. Much better than multiple independant dialogs for system settings. >and maybe keyword highlighting (like in Borland's windows based editors) Make sure it can be turned off. I don't like that. Use-definable keystrokes for everything and a command-line. Sort of like Emacs. This way, you can use any interface you want - type a command, use the mouse, or use keystrokes. It shouldn't be that hard to do, either. You just make the entire program command-line driven and have the menus and keystrokes dump commands on the line. Regular expression searching is nice. Since regexp.c is included in gcc (I believe), this shouldn't be too hard to install. I think that close-brackets (like ], ), }, >) should have the program "flash" the matching open-bracket or let you know if there's no matching character. These options may be difficult to do (I haven't seen them all in any one editor yet!), so I don't expect them in an initial release, but keep them in mind for version 2. -- David Charlap |"there aren't 50,000 things for which it's worth writing dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough ----------------------+ programmers to create that much good software. Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"
Technical Details
Message-ID:
<1992Oct15.181551.26270@njitgw.njit.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340References:
<sal8.64.0@po.cwru.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340 From: dic5340@hertz.njit.edu (David Charlap) Newsgroups: comp.os.os2.programmer Subject: Re: Programmer's Editors Message-ID: <1992Oct15.181551.26270@njitgw.njit.edu> Date: 15 Oct 92 18:15:51 GMT References: <sal8.64.0@po.cwru.edu> Sender: news@njit.edu Organization: New Jersey Institute of Technology, Newark, N.J. Lines: 59 Nntp-Posting-Host: hertz.njit.edu