jedit-devel Mailing List for jEdit

---

** [plugin-bugs:#1901] Lucene broken with 1.9**

**Status:** open
**Group:** 
**Created:** Wed Jan 31, 2018 01:03 PM UTC by Juergen Weber
**Last Updated:** Wed Jan 31, 2018 01:03 PM UTC
**Owner:** nobody


Lucene search is broken with Java 1.9

Search simply does nothing.

If I switch back to 1.8 it works again, so the only difference is Java version.

Maybe it is sufficient to update Lucene.



13:50:28 [jEdit Worker #3] [error] CentralIndex: Unable to open IndexReader
13:50:28 [jEdit Worker #3] [error] CentralIndex: java.io.IOException: Unable to unmap the mapped buffer: MMapIndexInput(path="C:\Users\weberjn\AppData\Roaming\jEdit\plugins\gatchan.jedit.lucene.LucenePlugin\__CENTRAL__\_0.si")
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.MMapDirectory$2.freeBuffer(MMapDirectory.java:301)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.ByteBufferIndexInput.freeBuffer(ByteBufferIndexInput.java:378)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.ByteBufferIndexInput.close(ByteBufferIndexInput.java:357)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.BufferedChecksumIndexInput.close(BufferedChecksumIndexInput.java:60)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.codecs.lucene50.Lucene50SegmentInfoFormat.read(Lucene50SegmentInfoFormat.java:120)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:326)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:53)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:50)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:660)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:50)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:63)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at gatchan.jedit.lucene.AbstractIndex.initReader(AbstractIndex.java:131)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at gatchan.jedit.lucene.AbstractIndex.getSearcher(AbstractIndex.java:120)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at gatchan.jedit.lucene.CentralIndex.fileUpdated(CentralIndex.java:232)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at gatchan.jedit.lucene.CentralIndex.access$000(CentralIndex.java:59)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at gatchan.jedit.lucene.CentralIndex$1.run(CentralIndex.java:86)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.gjt.sp.util.TaskManager$MyTask._run(TaskManager.java:258)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.gjt.sp.util.Task.run(Task.java:65)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/java.lang.Thread.run(Thread.java:844)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  Suppressed: java.io.IOException: Unable to unmap the mapped buffer: MMapIndexInput(path="C:\Users\weberjn\AppData\Roaming\jEdit\plugins\gatchan.jedit.lucene.LucenePlugin\__CENTRAL__\segments_2")
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.MMapDirectory$2.freeBuffer(MMapDirectory.java:301)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.ByteBufferIndexInput.freeBuffer(ByteBufferIndexInput.java:378)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.ByteBufferIndexInput.close(ByteBufferIndexInput.java:357)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.BufferedChecksumIndexInput.close(BufferedChecksumIndexInput.java:60)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:413)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   ... 15 more
13:50:28 [jEdit Worker #3] [error] CentralIndex:  Caused by: java.lang.IllegalAccessException: class org.apache.lucene.store.MMapDirectory$2$1 cannot access class jdk.internal.ref.Cleaner (in module java.base) because module java.base does not export jdk.internal.ref to unnamed module @30f47094
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:589)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at java.base/java.lang.reflect.Method.invoke(Method.java:556)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.MMapDirectory$2$1.run(MMapDirectory.java:294)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.MMapDirectory$2$1.run(MMapDirectory.java:286)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at java.base/java.security.AccessController.doPrivileged(Native Method)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   at org.apache.lucene.store.MMapDirectory$2.freeBuffer(MMapDirectory.java:286)
13:50:28 [jEdit Worker #3] [error] CentralIndex:   ... 19 more
13:50:28 [jEdit Worker #3] [error] CentralIndex: Caused by: java.lang.IllegalAccessException: class org.apache.lucene.store.MMapDirectory$2$1 cannot access class jdk.internal.ref.Cleaner (in module java.base) because module java.base does not export jdk.internal.ref to unnamed module @30f47094
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:589)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/java.lang.reflect.Method.invoke(Method.java:556)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.MMapDirectory$2$1.run(MMapDirectory.java:294)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.MMapDirectory$2$1.run(MMapDirectory.java:286)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at java.base/java.security.AccessController.doPrivileged(Native Method)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  at org.apache.lucene.store.MMapDirectory$2.freeBuffer(MMapDirectory.java:286)
13:50:28 [jEdit Worker #3] [error] CentralIndex:  ... 20 more
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask: java.lang.NullPointerException
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at org.apache.lucene.search.IndexSearcher.<init>(IndexSearcher.java:163)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at org.apache.lucene.search.IndexSearcher.<init>(IndexSearcher.java:148)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at gatchan.jedit.lucene.AbstractIndex.getSearcher(AbstractIndex.java:121)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at gatchan.jedit.lucene.CentralIndex.fileUpdated(CentralIndex.java:232)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at gatchan.jedit.lucene.CentralIndex.access$000(CentralIndex.java:59)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at gatchan.jedit.lucene.CentralIndex$1.run(CentralIndex.java:86)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at org.gjt.sp.util.TaskManager$MyTask._run(TaskManager.java:258)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at org.gjt.sp.util.Task.run(Task.java:65)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
13:50:28 [jEdit Worker #3] [error] TaskManager$MyTask:  at java.base/java.lang.Thread.run(Thread.java:844)



---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **status**: open --> closed-fixed



---

** [feature-requests:#534] Flag for an open Backup File**

**Status:** closed-fixed
**Group:** none
**Created:** Wed Mar 15, 2017 04:11 PM UTC by robert orton
**Last Updated:** Thu Jan 11, 2018 11:16 AM UTC
**Owner:** Roman Tsourick


Not sure if this is a feature already, but need something to blatently tell user they have opened a temporary file.

scenario: I was deep searching a directory for a pattern and inadvertently clicked on and opened a temporary file that has the "~" character at the end. I edited the file for days and noticed the file date never changed in my ftp program. couldnt figure out why date never changed.

I filter temp files in FTP, so the current file was never shown. So I had been editing "filename.ext~" which was filtered at my FTP, as well as its temporary file, "filename.ext~~". It took me some deciphering to find out what was happening, because the path names are so long, the ext~~ was usually clipped off in most contexts.

So a solution that would make sense at least to me is to show the filname differently in drop down, and maybe a different color in title of window.

Thanks.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

Cool. Thank you!

I used to be the syntax rules maniac, but this time I missed that, dunno why.

I was thinking about the icon, but refused that idea because it will override the dirty status in a scenario when a user modifies buffer first and then locks it.

Could you explain the EditBus.send() call?


---

** [patches:#615] feature #534 Flag for an open Backup File **

**Status:** closed-accepted
**Group:** 
**Created:** Thu Jan 11, 2018 11:13 AM UTC by Roman Tsourick
**Last Updated:** Thu Jan 25, 2018 08:21 PM UTC
**Owner:** Dale Anson
**Attachments:**

- [feature-534-flag-for-an-open-backup-file.patch](https://sourceforge.net/p/jedit/patches/615/attachment/feature-534-flag-for-an-open-backup-file.patch) (6.5 kB; application/octet-stream)


Introduces Buffer's isBackup() function, marks backup file with yellow in BufferSwitcher, adds confirmation on such file open (open/open locked/cancel).

Simple and ready, it is worth inclusion in release I guess.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **assigned_to**: Björn Kautler
- **Group**:  --> 



---

** [jeditlauncher-bugs:#48] jEdit launcher does not recognise Java 9**

**Status:** open
**Group:** 
**Created:** Thu Jan 25, 2018 06:52 PM UTC by jrs40
**Last Updated:** Thu Jan 25, 2018 06:52 PM UTC
**Owner:** Björn Kautler


When will the jEdit Launcher be updated for use with Java 9? When one uses the current jEdit Launcher one gets a Window stating that one must use Java 8. When one dismisses this Window, one is taken to the Java Site to download a Java 8 installation. Thru a lot of trial and error I worked out a way to use jEdit on Windows bypassing the jEdit Launcher by editing Windows Shortcuts and creating a Windows CMD file to run jEdit directly, bypassing the Launcher. When can I expect an update? Remember, Java 8 goes extinct in October 2018.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/jeditlauncher-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/jeditlauncher-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

---

** [plugin-central-submission:#1036] JDiff 3.4.0**

**Status:** open
**Group:** None
**Created:** Thu Jan 25, 2018 08:44 PM UTC by Dale Anson
**Last Updated:** Thu Jan 25, 2018 08:44 PM UTC
**Owner:** nobody


{{{ JDiffPlugin 3.4.0
    Source: Source code is in SVN with the tag jdiffplugin-3_4_0
    Announcement: bug fix release
    Requires Java 1.8
    Requires jEdit 05.04.99.00
    Required plugins: 
        Common Controls 1.7.4 (CommonControlsPlugin)
    
    Short Description: JDiffPlugin is a visual diff and merge utility for jEdit.
    
    Long Description: JDiffPlugin is a visual diff utility for jEdit.
 }}}


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-central-submission/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-central-submission/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

Awesome. I asked Vampire if he could look at the recent jedit launcher
java9 compatibility issue.
I have nothing else to add to jEdit 5.5.


On Thu, Jan 25, 2018 at 12:22 PM, Dale Anson <da...@da...> wrote:

> Okay, both of those patches are taken care of.
>
> On Tue, Jan 23, 2018 at 11:05 AM, Dale Anson <da...@da...> wrote:
>
>> Thanks. I have internet today, I'll take a look at those patches. I did
>> notice the text area build is broken, looks like a straightforward fix.
>>
>> On Jan 18, 2018 3:09 PM, "Alan Ezust" <ala...@gm...> wrote:
>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Alan Ezust <ala...@gm...>
>>> Date: Thu, Jan 18, 2018 at 1:51 PM
>>> Subject: Re: jEdit release?
>>> To: Dale Anson <da...@da...>
>>>
>>>
>>> Oh also patch #569 needs to be rolled back or fixed so that the
>>> indepedent text area is not broken anymore.
>>>
>>>
>>> On Thu, Jan 18, 2018 at 1:49 PM, Alan Ezust <ala...@gm...>
>>> wrote:
>>>
>>>> I am out of town all week, living out of a suitcase. I think there is
>>>> one more patch one of us should review before the release:
>>>>
>>>> https://sourceforge.net/p/jedit/patches/615/
>>>> I will ping Vampire after that is applied and tested.
>>>>
>>>>
>>>>
>>>> On Thu, Jan 18, 2018 at 12:53 PM, Dale Anson <da...@da...>
>>>> wrote:
>>>>
>>>>> Let me know when the release is tagged or out. I'll wait to check in
>>>>> my changes after that. Next week, maybe?
>>>>>
>>>>> On Jan 4, 2018 6:57 PM, "Alan Ezust" <ala...@gm...> wrote:
>>>>>
>>>>>> that's the plan. still wanna follow up on an untitled issue before
>>>>>> release.
>>>>>>
>>>>>> On Jan 4, 2018 1:19 PM, "Dale Anson" <da...@da...> wrote:
>>>>>>
>>>>>>> I thought I saw something about next release for 5.5 is this month?
>>>>>>> I have a bunch of changes to check in but want to wait until after the
>>>>>>> release. I've been fixing all the deprecation warnings from Java 9, I have
>>>>>>> 8 remaining of about 240.
>>>>>>>
>>>>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> --
>>> -----------------------------------------------
>>> jEdit Developers' List
>>> jEd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>
>>>
>

- **status**: open --> closed-accepted
- **assigned_to**: Dale Anson
- **Group**:  --> 
- **Comment**:

Applied in revision  24820, thanks!  A couple of things -- not a big deal, but in the future, pay attention to the bracket placement so it matches the rest of the code. I also added a little code so the lock icon shows in the buffer switcher when the buffer is locked.



---

** [patches:#615] feature #534 Flag for an open Backup File **

**Status:** closed-accepted
**Group:** 
**Created:** Thu Jan 11, 2018 11:13 AM UTC by Roman Tsourick
**Last Updated:** Thu Jan 11, 2018 11:13 AM UTC
**Owner:** Dale Anson
**Attachments:**

- [feature-534-flag-for-an-open-backup-file.patch](https://sourceforge.net/p/jedit/patches/615/attachment/feature-534-flag-for-an-open-backup-file.patch) (6.5 kB; application/octet-stream)


Introduces Buffer's isBackup() function, marks backup file with yellow in BufferSwitcher, adds confirmation on such file open (open/open locked/cancel).

Simple and ready, it is worth inclusion in release I guess.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **assigned_to**: Alan Ezust
- **Group**:  --> 



---

** [plugin-bugs:#1900] Project Viewer inconsistency**

**Status:** open
**Group:** 
**Created:** Thu Jan 25, 2018 02:29 PM UTC by Edward Diener
**Last Updated:** Thu Jan 25, 2018 02:29 PM UTC
**Owner:** Alan Ezust


In PV when I have the "Follow active buffer in tree" option checked, PV does indeed show the active buffer in the PV tree. Yet when I add the active buffer to PV, through the PV "Add current buffer" action, PV does not show the added active buffer in the PV tree. I have to switch to some other buffer and then back to the recently added buffer for PV to show that recently added buffer in the PV tree.

It would be nice if this could be fixed so that PV immediately shows an added current buffer in the PV tree.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **status**: open --> closed-duplicate



---

** [bugs:#4061] Project Viewer inconsistency**

**Status:** closed-duplicate
**Group:** normal bug
**Created:** Thu Jan 25, 2018 02:27 PM UTC by Edward Diener
**Last Updated:** Thu Jan 25, 2018 02:31 PM UTC
**Owner:** nobody


In PV when I have the "Follow active buffer in tree" option checked, PV does indeed show the active buffer in the PV tree. Yet when I add the active buffer to PV, through the PV "Add current buffer" action, PV does not show the added active buffer in the PV tree. I have to switch to some other buffer and then back to the recently added buffer for PV to show that recently added buffer in the PV tree.

It would be nice if this could be fixed so that PV immediately shows an added current buffer in the PV tree.



---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

---

** [jeditlauncher-bugs:#48] jEdit launcher does not recognise Java 9**

**Status:** open
**Group:** 
**Created:** Thu Jan 25, 2018 06:52 PM UTC by jrs40
**Last Updated:** Thu Jan 25, 2018 06:52 PM UTC
**Owner:** nobody


When will the jEdit Launcher be updated for use with Java 9? When one uses the current jEdit Launcher one gets a Window stating that one must use Java 8. When one dismisses this Window, one is taken to the Java Site to download a Java 8 installation. Thru a lot of trial and error I worked out a way to use jEdit on Windows bypassing the jEdit Launcher by editing Windows Shortcuts and creating a Windows CMD file to run jEdit directly, bypassing the Launcher. When can I expect an update? Remember, Java 8 goes extinct in October 2018.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/jeditlauncher-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/jeditlauncher-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

I resubmitted this as a plugin bug, so it can be removed here as a JEdit bug.


---

** [bugs:#4061] Project Viewer inconsistency**

**Status:** open
**Group:** normal bug
**Created:** Thu Jan 25, 2018 02:27 PM UTC by Edward Diener
**Last Updated:** Thu Jan 25, 2018 02:27 PM UTC
**Owner:** nobody


In PV when I have the "Follow active buffer in tree" option checked, PV does indeed show the active buffer in the PV tree. Yet when I add the active buffer to PV, through the PV "Add current buffer" action, PV does not show the added active buffer in the PV tree. I have to switch to some other buffer and then back to the recently added buffer for PV to show that recently added buffer in the PV tree.

It would be nice if this could be fixed so that PV immediately shows an added current buffer in the PV tree.



---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

---

** [plugin-bugs:#1900] Project Viewer inconsistency**

**Status:** open
**Group:** 
**Created:** Thu Jan 25, 2018 02:29 PM UTC by Edward Diener
**Last Updated:** Thu Jan 25, 2018 02:29 PM UTC
**Owner:** nobody


In PV when I have the "Follow active buffer in tree" option checked, PV does indeed show the active buffer in the PV tree. Yet when I add the active buffer to PV, through the PV "Add current buffer" action, PV does not show the added active buffer in the PV tree. I have to switch to some other buffer and then back to the recently added buffer for PV to show that recently added buffer in the PV tree.

It would be nice if this could be fixed so that PV immediately shows an added current buffer in the PV tree.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

---

** [bugs:#4061] Project Viewer inconsistency**

**Status:** open
**Group:** normal bug
**Created:** Thu Jan 25, 2018 02:27 PM UTC by Edward Diener
**Last Updated:** Thu Jan 25, 2018 02:27 PM UTC
**Owner:** nobody


In PV when I have the "Follow active buffer in tree" option checked, PV does indeed show the active buffer in the PV tree. Yet when I add the active buffer to PV, through the PV "Add current buffer" action, PV does not show the added active buffer in the PV tree. I have to switch to some other buffer and then back to the recently added buffer for PV to show that recently added buffer in the PV tree.

It would be nice if this could be fixed so that PV immediately shows an added current buffer in the PV tree.



---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

Hi folks, I'm planning on doing a round of plugin releases the first
weekend of Feb.

As of right now there aren't any release requests, so if there are any
plans, please have them in there by Feb. 3rd.
https://sourceforge.net/p/jedit/plugin-central-submission/

Thanks!
Eric B


-- 
Learn from the past. Live in the present. Work towards the future.
turtlepaws.com - When was the last time you changed your master password?
Blog: http://eric-berry.blogspot.com
jEdit <http://www.jedit.org> - Programmer's Text Editor

I wanted to check if I can see something in the jEdit Activity log, but starting from today (and without having changed anything in the configuration of jEdit), the Java Exception does not occur anymore, no matter how hard I tried! The only oddities are, that the message *Process exit exited with code 0*  is shown in the colour for error messages instead of information messages, and that typing **exit** does not close the console window. I don't know whether these are really bugs; maybe this is the intended behaviour.

I will try a couple of days more, and if the error occurs again, I will check the activity log.


---

** [plugin-bugs:#1898] Console Plugin shows InterruptedIOException after some commands**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Mon Jan 22, 2018 11:30 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

ok I changed the subject again. Any info or relevant logs about how to reproduce it will be appreciated.



---

** [plugin-bugs:#1898] Console Plugin shows InterruptedIOException after some commands**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Mon Jan 22, 2018 11:30 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **summary**: Console Plugin shows InterruptedIOException after each command --> Console Plugin shows InterruptedIOException after some commands



---

** [plugin-bugs:#1898] Console Plugin shows InterruptedIOException after some commands**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Mon Jan 22, 2018 03:26 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

I suggest that you change the title to ".... after some commands". While the red error status is shown always, the exception shows up only sometimes. Is there something I can do, such providing logfiles?


---

** [plugin-bugs:#1898] Console Plugin shows InterruptedIOException after each command**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 07:18 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

---

** [bugs:#4060] Replace text in all open files only works once**

**Status:** open
**Group:** minor bug
**Created:** Sat Jan 20, 2018 11:41 AM UTC by Axel Schwank
**Last Updated:** Sat Jan 20, 2018 11:41 AM UTC
**Owner:** nobody


jEdit Version: 5.4.0
Java Version: Oracle Java 1.8.0-151
Platform: Linux (Kernel Version 4.4.104-18.44)
Some plugins installed, but none used related to this bug

When replacing text in several open buffers with "Replace all" in the search&replace dialog with option "Search in"="open files", and doing this TWICE, the text is only replaced in the currelty active buffer. If you change the "Search in" option to another value and back to "open files", the text is replaced properly in all open buffers.
This bug has been in former jEdit Versions, at least since 5.1.0.

Steps to reproduce:
1. Open several files which all contain some common text
2. Replace this text with the search&replace dialog, using "search in open files" and perform "Replace all"
3. Text gets replaced in all open files
4. Repeat these steps (with other common text or the replaced text above)
5. Text gets replaced only in the current buffer
6. Repeat these steps, but change the option "serach in" to another value and back to "open files"
7. Text gets replaced in all open files


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

ok I changed the subject. I can not reproduce this issue though.



---

** [plugin-bugs:#1898] Console Plugin shows InterruptedIOException after each command**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 07:17 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **summary**: Console Plugin shows InterrupedIOException after each command --> Console Plugin shows InterruptedIOException after each command



---

** [plugin-bugs:#1898] Console Plugin shows InterruptedIOException after each command**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 07:16 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **summary**: Console Plugin shows strange error messages after each comman --> Console Plugin shows InterrupedIOException after each command
- **status**: closed-works-for-me --> open



---

** [plugin-bugs:#1898] Console Plugin shows InterrupedIOException after each command**

**Status:** open
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 05:13 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

I'm not refering to showing the exit status. This is perfectly fine. I want to see the exit status.

Please pay attention to what I reported on. I reported that an exit code 0 is treated as error, and that I can see a Java exception. 

As for the exit status, if the desired behaviour is to always treat an exit status as error, I understand that this is not an issue. The Java exception still might be. 

I also don't quite understand, that a ticket is closed, just because one person exists who doesn't happen to see this behaviour. I am a software developer myself. A bug does not mean that one person in this world does not see a buggy behaviour; it means that there is some person who does see a buggy behaviour.

I am aware that there are bugs which show up under certain circumstances only, so some people can see them and some people don't. This is not unusual. I also understand that you can not attempt to fix a bug, if you are not able to reproduce it.  I am of course willing to provide support as much as I can. If you need additional logging information and tell me how I can turn on logs, I will happily provide this information. Just closing this ticket because the assigned person can not reproduce it, is, IMHO, a bit strange.



---

** [plugin-bugs:#1898] Console Plugin shows strange error messages after each comman**

**Status:** closed-works-for-me
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 02:08 PM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

- **status**: open --> closed-works-for-me
- **Group**:  --> 
- **Comment**:

plugin options - console - system shell - uncheck the option 'show exit status'



---

** [plugin-bugs:#1898] Console Plugin shows strange error messages after each comman**

**Status:** closed-works-for-me
**Group:** 
**Created:** Fri Jan 19, 2018 08:21 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 08:25 AM UTC
**Owner:** nobody
**Attachments:**

- [capture_20180119_091237.jpg](https://sourceforge.net/p/jedit/plugin-bugs/1898/attachment/capture_20180119_091237.jpg) (23.7 kB; image/jpeg)


When I enter a command in the shell of the console plugin, the command is always executed correctly, but in the end, strange error messages are displayed in red; an example can be seen at the attached screenshot. The red  message is at least "Process .... exited with code 0", which is technically correct, but should not be marked as error. In addition, I sometimes see a Java exception displayed.

It's not that the Console plugin would not work at all; I **can** use it, but the error messages are somewhat disturbing.


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/plugin-bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/plugin-bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

---

** [feature-requests:#543] Editing in Ruby mode should by default include '!' and '?' as word characters**

**Status:** open
**Group:** none
**Created:** Fri Jan 19, 2018 09:09 AM UTC by Ronald
**Last Updated:** Fri Jan 19, 2018 09:09 AM UTC
**Owner:** nobody


The "additional word characters" are in general just the underscore ( _ ). jEdit allows to configure different word characters for each edit mode. I suggest that the default settings for Ruby already include the exclamation mark ( ! ) and question mark (?), because they can be part of a word (though only as the last character).

In additional, I suggest (for this reason) to have three lists for "additional word characters anywhere in the word", "additional word characters at the start of a word" and "additional word characters at the end of a word". This would allow finer control of what a word is. In Ruby, we could put exclamation mark and question mark to the "word end list", and the colon (:) to the start word list (because a leading colon denotes a "symbol" and can be considered part of the word, while a trailing colon is a special type of separator in a hash).


---

Sent from sourceforge.net because jed...@li... is subscribed to https://sourceforge.net/p/jedit/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.