Editing in the XQuery buffer - 2 RFEs

On Wed, Oct 13, 2010 at 1:50 AM, C. M. Sperberg-McQueen <cmsmcq at blackmesatech.com> wrote: > In my use of BaseX I am regularly troubled by one minor shortcoming > (as I see it :) in the interactive graphical user interface. When I am > concentrating hard on formulating a query, my fingers automatically > type Emacs keystrokes to move the cursor around. The result is > that I end up inserting ^A, ^D, ^E, and ^K characters into the buffer. > (Other Emacs users might end up with stray ^N and ^P characters, > but this usually doesn't happen to me.) > > It would make the XQuery box in the GUI a lot more convenient for > me if these keystrokes had their normal Emacs meaning there. > Consider that a request for enhancement. > > In the meantime, I have the problem that if I type one of these > characters by accident, and then move away from the location > (which happens quite often, since some of these characters are > often parts of sequences of cursor movements), then I get an error > message from BaseX (e.g. the message now showing in my > status bar, "[XPST0003] Query contains an illegal character (#1)." > But there is no visual indication of where the stray character is: > all of these characters are invisible in the XQuery buffer. > > If it were possible to make these illegal characters visible in some > way (as "^A" or some kind of dot or box, for example), it would > help at least those users who, like me, have Emacs keystrokes > wired into their fingers. > > Another RFE. > > Thanks! > > Michael > > -- > **************************************************************** > * C. M. Sperberg-McQueen, Black Mesa Technologies LLC > * http://www.blackmesatech.com > * http://cmsmcq.com/mib > * http://balisage.net > **************************************************************** > > > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >

On Oct 12, 2010, at 8:20 PM, Christian Grün wrote: > Michael, > > thanks for your feedback. I hope you were successful switching to our > latest versions?

> Some more questions: > > – does the problem persist with our latest minor verion (6.2.9)? > Source: http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.2.9/basex-6.2.9.jar

> – as I didn't manage yet to reproduce the issue: which keys do you > exactly use to end up with the control codes, and which OS are you > using? In BaseX, shortcuts like ctrl+a should only responsible for > marking all the text, etc.

On Thu, Oct 14, 2010 at 1:07 AM, C. M. Sperberg-McQueen <cmsmcq at blackmesatech.com> wrote: > On Oct 13, 2010, at 8:21 AM, C. M. Sperberg-McQueen wrote: >> >> p.s. If there is a dmg package for 6.2.9, or instructions for >> integrating newer jar files into an existing BaseX.app, I'd be >> grateful for a pointer -- the color highlighting of syntax problems >> is a good help! > > In case other Mac users need to upgrade their BaseX.app to > new jar files and don't already know how, I'll just record that the > following procedure worked fine for me: > > (1) in a shell window, navigate to > > /Applications/BaseX.app/Contents/Resources/Java/repo/org/basex/basex > > In my case, this contained a directory named 6.1, > containing basex-6.1.jar. > > (2) Create a 6.2 directory, and copy the new jar file into > it. In my case: > > mkdir 6.2; mv ~/Downloads/basex-6.2.9.jar ./6.2 > > (3) Edit the file /Applications/BaseX.app/Contents/info.plist > in an XML editor. Find the key/value pair for ClassPath > and change it appropriately. In my case, this meant changing > > <key>ClassPath</key> > <array><string>$JAVAROOT/repo/org/basex/basex/6.1/basex-6.1.jar</string></array> > > to > > <key>ClassPath</key> > <!--* > <array><string>$JAVAROOT/repo/org/basex/basex/6.1/basex-6.1.jar</string></array> > *--> > <array><string>$JAVAROOT/repo/org/basex/basex/6.2/basex-6.2.9.jar</string></array> > > Save the file. > > (4) Relaunch BaseX. > > In case of difficulty, check to make sure you didn't accidentally render the > info.plist document ill-formed. > > There may be other better ways to do this, but this seemed simple enough > to me. > > -- > **************************************************************** > * C. M. Sperberg-McQueen, Black Mesa Technologies LLC > * http://www.blackmesatech.com > * http://cmsmcq.com/mib > * http://balisage.net > **************************************************************** > > > > >

On Oct 13, 2010, at 8:21 AM, C. M. Sperberg-McQueen wrote: > > p.s. If there is a dmg package for 6.2.9, or instructions for > integrating newer jar files into an existing BaseX.app, I'd be > grateful for a pointer -- the color highlighting of syntax problems > is a good help!

> Btw, I've asked the Mac users in our project > to check out if they can reproduce the control code issue.

> In case other Mac users need to upgrade their BaseX.app to > new jar files and don't already know how, I'll just record that the > following procedure worked fine for me:

> <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>osxappbundle-maven-plugin</artifactId> > <version>1.0-alpha-2</version> > <configuration> > <mainClass>org.basex.BaseXWin</mainClass> > <iconFile>${basedir}/etc/build/OSXBundle/BaseX.icns</iconFile> > <jvmVersion>1.5+</jvmVersion> > </configuration> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>bundle</goal> > </goals> > </execution> > </executions> > </plugin>