From: Richard W. <ric...@se...> - 2001-03-27 15:21:12
|
From: "Slava Pestov" <sl...@je...> > > 1. Error List > > Has the error-list plugin "previous-error-causes exception" problem > It is fixed in my private copy, which I am not going to release until > jEdit 3.1final, because it relies on 3.1 APIs. I guess I'll stick with my private macro until then. > > 2. Keyboard mappings > > coded paths and stuff. What happens if I put some keyboard bindings > > in the EditorScheme files? > You can freely copy properties from machine to machine; the only > hard-coded paths are the recent files. And the location of templates. I remember copying the properties file from one machine to another and then jEdit hung and would not even start. When I stopped copying the properties file around the problem stopped. Would this have anything to do with the template directory? > > 3. Package name guesser, Constructor macro. > The JCompiler plugin already provides a package guesser in it's > 'buildtools' package (see the Run java macro included with jEdit > for an example of its use) I have looked at the buildtools package and its package guesser. It parses through the buffer looking for the package name. This means you have to manually type the package name into the buffer yourself. The macro I wrote looks at the classpath and the buffer path and takes a guess at the package name from that. When creating a new .java file my macro would help but the buildtools package would only work after my macro ran or the user supplied the package name manually. ---------------------------------------------------------------------- Richard F. Wan email: ric...@se... Phone: 403 263 3287 Fax: 403 265 5690 Servidium Inc. Suite 800, 840 7th Ave SW Calgary, Alberta, Canada T2P 3G2 |