Karr, David writes: > Nope, that didn't help. I first tried just renaming the "semantic" > directory in the xemacs tree, which didn't help, so then I tried > specifically uninstalling that package from the Xemacs installer, and > that also didn't help. It still inserts the imports at the top of the > file.
David, Does the Classes menu appear in the Java source buffer into which you are trying to import classes. If so, does this message correctly display the variables and methods of the classes in that buffer? Does the senator menu? Also please post a complete problem report so that we don't have to guess what your setup is. Paul > > > -----Original Message----- > > From: Paul Kinnucan [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 15, 2004 2:44 PM > > To: Karr, David > > Cc: [EMAIL PROTECTED] > > Subject: RE: Any way to customize where import generates the > > import statement? > > > > > > Karr, David writes: > > > Note that my setup did not "replace" the version of > > Semantic, I just put > it in the load-path before other > > instances of Semantic (and I verified > that by inspecting > > the value after startup). The User Guide > specifically > > says to REMOVE the older instances. Is there any reason to > > > expect this might be my problem? > > > > Yes. XEmacs seems to always load packages included in the > > distribution before any packages on the load-path. > > > > Paul > > > > > > > > > > > -----Original Message----- > > > > From: Paul Kinnucan [mailto:[EMAIL PROTECTED] > > > > Sent: Sunday, November 14, 2004 10:02 PM > > > > To: Karr, David > > > > Cc: [EMAIL PROTECTED] > > > > Subject: RE: Any way to customize where import generates the > > > > import statement? > > > > > > > > > > > > Karr, David writes: > > > > > I see now that the user guide just says it inserts at the > > > > head of the > buffer, but the code appears to be a little > > > > more sophisticated, where it > tries to figure out where it > > > > should insert the import > > > > > (jde-import-get-import-insertion-point). However, the result > > > > is the > same. It just inserts the new import before the > > > > package statement. I > guess I'll try a little debugging of > > > > that function. > > > > > > > > Hi David, > > > > > > > > The import statements are supposed to be inserted AFTER the > > > > package statement. That's how it's always worked for me and > > > > how it worked when I just tested it by creating: > > > > > > > > file Foo.java > > > > package jmath; > > > > > > > > class Foo { > > > > JButton button; > > > > } > > > > > > > > and doing C-c C-v C-z with point on JButton. The result is > > > > > > package jmath; > > > > > > > > import javax.swing.JButton; > > > > > > > > public class Foo { > > > > JButton button; > > > > } > > > > > > > > > > > > I'm mystified that it works differently for you. Please send > > > > a test case that I can use to reproduce the bug. > > > > > > > > Paul > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Karr, David > > > > > > > > > > > > Is there any way to customize where import statements are > > > > > > generated? It presently inserts them at the head of the > > > > > > buffer, which means I still have to move them after they're > > > > > > generated. I always put imports in a block with no blank > > > > > > lines, after the "package" statement, with a blank line > > > > > > before and after the block. I see there are options for > > > > > > specifying how imports are grouped, but I assume that's > > > > > > separate from where they're initially inserted. > > > > > > > > > > > >
