Activity for Ernie Rael
-
Ernie Rael posted a comment on ticket #109
I'm wrong about library jars being included in jvi.jar. Everything in is the jvi-code/dist directory, the libraries are in jvi-code/dist/lib
-
ran the build again today, it just worked Cool. Note that the jvi build produces jar files that run under jdk-11, but language constructs from jdk-19 can be used (frgaal magic). Note that you can do java -jar dist/jvi.jar to bring up the test window. jvi.jar should have everything needed to link/build against. It contains the jvi-core and jvi-swing jars along with various jars. Depending on your needs you might want to use individual jars, rather than the bundle. To get started, depending on your...
-
There's https://sourceforge.net/p/jvi/raelity-gradle/ which is the source I used to build the plugin. But the following would indicate that you can ignore that. I just tried moving aside 1. ~/.gradle 2. <mvn-repo>/com/raelity/namedservices-merge 3, <mvn-repo>/com/raelity/gradle 4. <mvn-repo>/org/frgaal Downloaded fresh source from http://hg.code.sf.net/p/jvi/code into jvi-code did JAVA_HOME=/ref/openjdk/jdk-11 ./gradlew run The first time I tried, I didn't set JAVA_HOME and ran into trouble (but...
-
That's weird. The plugin, and instructions on how to use it are at https://plugins.gradle.org/plugin/com.raelity.namedservices-merge I'll take a look.
-
Check out the jVi source, see https://sourceforge.net/p/jvi/code/, and in the top level directory do ./gradlew run This brings up a JEditorPane (JTextArea isn't enough) with jVi installed. This is built from the jvi-cmd directory, using the jars from jvi-core and jvi-swing. This is minimal. Also see README.
-
If you provide steps to recreate, I'll give it a try. (I don't understand how it happened). Command mode is after ":".
-
I guess jstack is recommend (there are several ways). See https://www.baeldung.com/java-thread-dump for a pretty good description. similar with the others, except this time it worked Wow, that is intriguing.
-
Thanks for isolating the issue. I'm on gtk, I've tested with those LAFs, 1920x1080. Seems it must be HiDPI I won't have much time for a few days. I'd like to file a NB issue. Would you get get a stack trace while it's going crazy, so I can include it? Might help narrow it down. Hopefully one of the LAF maintainers will be interested, the FlatLaf get a lot of attention right now.
-
If you do that, let me know so I can subscribe to it.
-
I'm on recent linux release (popOS). I download the zip; don't use an installer. I'm running 16; I've run all versions, plus build my own on occation. During testing, I install jVi in a variety of ways. Starting up NetBeans with a clean userdir/cachedir using the --userdir/--cachedir options, install the update center, then install jVi is one of the things I do. Did you look into the NetBeans messages.log, maybe there's some exception. $ env|grep -i xdg XDG_CONFIG_DIRS=/etc/xdg/xdg-pop:/etc/xdg XDG_MENU_PREFIX=gnome-...
-
Did you try resizing the window? 2 machines, that's weird. I can't reproduce it. Did it ever work? Did you import settings? A clean install of both NetBeans and jVi , without importing settings, is something to try.
-
This sounds vaguely familiar. Don't remember what the issue is, JDK, MAC, or what. Could you try resizing the options window, for example make it very big? I can't reproduce it. I don't see another bug report about it.
-
jvi suddenly quit working in Netbeans 12.0
-
2.0, jdk11
-
include config for jar signing, commented out
-
remove nb-uc from this repository, moved to nbvi
-
specify jdk1.8.
-
use jdk1.8, HAS_ANCIENT_NB_HACKS 78f337c53d56, Build nb-uc for 11.0 (not .2).
-
nb-uc points to NetBeans-11-and-later
-
remove ancient nbm used to hack NB internals.
-
Fix issue lookup's resultChanged might be called NOT in EDT.
-
Added tag HAS_ANCIENTS for changeset 78f337c53d56
-
changes made by IDE
-
Standalone WindowsProvider for a NB that has proposed changes incorporated.
-
Maven update center. Basically all defaults. Add to pom for maven central.
-
Change to NB license
-
Add <extra-compilation-unit>... so don't see errors on source in editor.
-
Package patch as modules.
-
Clean up structure for windows patch
-
move stuff to patchsrc directory.
-
baby steps to get an NBM to work.
-
Get update center module to hack/clear _removed after install.
-
checkpoint the friend hack code
-
NBMs with windows patch
-
get rid of dummy-suite, use makeupdatedesc directly for single modules.
-
Update the nbm with "main" from build.xml.
-
Use default platform.
-
Add nb70 update center for jVi.
-
New pin.
-
Build jvi support nbm under a module suite
-
Add popup separator, remove unused files
-
take out useless log statement
-
jvi global action prototype
-
move tar file into checkpoint directory
-
UC post install project
-
Added tag WorksInstanceCreate for changeset cebcb67d792a
-
Rework to use instanceCreate instead of shadow.
-
Start the instance file approach
-
stash tar file of editor.pin experiment
-
Get rid of PinFactory, general cleanup
-
cleanup/refactor file names
-
Pin fire an event when clear() for all the Pin to sync their enable.
-
Works. Big bug was filesystem didn't behave as advertised.
-
Added tag WorksShadowOrig for changeset 126f339b5121
-
Always create an Object if fixupShadow called.
-
Identified/filed the various NB bugs. Implement simple workarounds
-
Fix bug in weak listener setup
-
getting ready to introduce MultiFileSystem
-
fix bug in .hgignore
-
Provide description and nbm signing.
-
Make it a red icon.
-
add a 24x24 icon
-
add action to all editor popups.
-
Removed experimetal action api depend, bump spec ver
-
Change package hierarchy
-
Clean up, hook up "pin" icon.
-
After create project, add action wizard
-
works, lots of history/check commented out. Needs icon work.
-
jvi no cursor on jdk8
-
Changed the default for the option, so it works out of the box for most people. Also changed the name so doesn't mention MAC.
-
":w" broken
-
Backspace and autocompletion
-
Can't reproduce. No comments several years. closing.
-
Netbeans8.0 / jvi stopped working after installing other plugins
-
Can't reproduce. No comments several years. closing.
-
Fixed in jVi-2.0.13.
-
URISyntaxException when opening Netbeans
-
Request JavaVi implement the :cd command
-
Available since jVi-2.0
-
Thanks, this time it's an expected exception. The bug is that jVi prints it. I've fixed it here. I thought I would a while to see if anything else shows up since there were so many rapid fire releases. Have you tried :e* ?
-
Error when closing editor window
-
Got hold of a windows system. Found a couple more windows issues clipboard handling both on Linux, broke windows clipboard handling :e*, :cd,:e path handling issues with '\' in filename (was treated like an escape) v2.0.11 is now available and fixes these issues
-
I've uploaded https://sourceforge.net/projects/jvi/files/jVi-for-NetBeans/NetBeans-12_JDK-11/nbvi-2.0.10.rc2.zip/download Give it a try if you get a chance. If I don't hear anything negative, I'll upload to the jVi update center tomorrow.
-
Instead of " I'm going to use @; since it represents your location in a file, at sign feels good. Any problem with a Windows filename having that char in it? If I don't hear of any problem soon, it's going in.
-
Thanks very much for the report. (I'm on Linux now, no Windows testing) With v2.0.9 jVi saves the cursor position when a file closes, and uses it to restore the cursor position if the file is reopened. Vim uses a buffer mark named ", jVi uses the same name. This ends up creating a preferences node named of double quote, which is legal, accd to the jdk docs The only restrictions on this name are that it cannot be the empty string, and it cannot contain the slash character ('/') So I'd say this is...
-
Glad you're enjoying it.
-
You can get the fix pointing an update center to https://sourceforge.net/projects/jvi/files/jVi-for-NetBeans/NetBeans-12_JDK-11/UC/ Or downloading and installing from nbvi-2.0.rc1.zip
-
Fixed, release soon. JDK-11 only, hope that's ok. Thanks for 1=*, nice case. Transitioned from window to linux at home (for joy) took longer than expected; spending time on it helps.
-
BTW, good luck and feel free to ask questions
-
Greetings, in the jvi repository's top directory you can do ant run"which runs a demo/debug jVi; no file IO, but you can copy/paste into jVi; ViFS is the interface you implement to hook into your apps file IO for stuff like :w. The demo code is <repo>/src/com/raelity/jvi/cmd. This is probably the best place to start. The Play*.java in the directory are mostly simple implementations of the interfaces needed to plug jvi into swing component. The website's help files are pretty accurate about what implemented...
-
What is the "leader key"?
-
I don't understand. There's missing information about the failure. Steps to reproduce are needed. What, if anything, was in the output window as mentioned in the error dialog? Version numbers, NB and jVi could be provided.
-
The trace shows the jVi exception occurs before any modules are enabled and that the exception is happening while trying to print an error message because the compilation of a regex failed (probably a regex syntax error). During startup, jVi compiles the user's last regex from the previous session, see Search.startupInitializePattern on the stack. Looks like it's too early to print an error message since there's an exception. This seems to indicate that while you were trying to get this to work,...
-
I don't understand the question or anything about partex. Please clarify the problem and what you expect.
-
Done. Stanley, I don't know to what this is referring.
-
I also tried mapping the long command. Unfortunately, it says to many fields. This indicates that there are blanks in the mapping. Need to use<Space> like in vim. See http://jvi.sourceforge.net/?vimhelp/map.txt.html#:map-special-keys
-
Escape from using Ctrl-c or Ctrl-[
-
This is not as simple as I'd hoped. You can't change the direct of the java runtime. StackOverflow Notice that there's a issue against java marked "won't fix". I'll think about how I might track a virtual cwd, a key part is detecting when :cd abc would fail. I think handling :!xxx is already done with java's process builder and you can specify a directory. RobertS, was the ^R in command line insert useful?
-
If memory serves, this is fixed. Can someone, Andy?, confirm.
1 >
