jedit-devel Mailing List for jEdit

---

** [plugin-central-submission:#1045] Plugin for Apple macOS**

**Status:** open
**Group:** None
**Created:** Wed May 29, 2019 08:30 PM UTC by Makarius
**Last Updated:** Wed May 29, 2019 08:30 PM UTC
**Owner:** nobody


{{{ MacOS 1.5
    Source: https://sourceforge.net/p/jedit/MacOS
    Announcement: Plugin for Apple macOS for current Java 11 LTS (formally Java 1.9, or later).
    Requires Java 1.9
    Requires jEdit 05.05.99.00
    
    Short Description: Provides Apple macOS integration through features such as better CMD-key mapping, drag-and-drop from Finder and more.
    
    Long Description: The MacOS plugin provides features that are specific to Apple macOS
but not supported out-of-the-box by jEdit.

Features include:
* Drag-and-drop support from Finder
* Preferences through conventional CMD+comma and application menu
* Reveal in finder by CMD/CTRL-clicking in the title bar
* Correct mapping of CMD key in all input fields for better copy-paste functionality
 }}}


---

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.

On Wed, May 29, 2019 at 10:34 AM Makarius <mak...@sk...> wrote:

> OK, with this information I managed to convert this part of the svn to
> git as follows (on Ubuntu 18.04):
>
>   svn2git https://svn.code.sf.net/p/jedit/svn/plugins/MacOSX
>
> The result is now on https://sourceforge.net/p/jedit/MacOS with changes
> as follows (current version ab18798a2e7):
>

awesome!

What needs to be done to publish this plugin officially? There should be
>
no conflict with the existing MacOSX plugin (which is frozen at version
> 1.3).
>

First, post a release announcement on the plugin release request tracker.
A template is created from the macro - properties - create plugin
announcement.

http://www.jedit.org/?page=devel

> Hi Makarius,
> 
> I have a variable called JEDITSVN which is set to
> svn+ssh://ezust@svn.code.sf.net/p/jedit/svn
> <http://ezust@svn.code.sf.net/p/jedit/svn>
> Then I can check out any SVN plugin using the variable like this:
> 
> $ svn co $JEDITSVN/plugins/MacOS/trunk MacOS

OK, with this information I managed to convert this part of the svn to
git as follows (on Ubuntu 18.04):

  svn2git https://svn.code.sf.net/p/jedit/svn/plugins/MacOSX

The result is now on https://sourceforge.net/p/jedit/MacOS with changes
as follows (current version ab18798a2e7):

  * The plugin is called MacOS (again), as capitalized version of the
"macOS" terminology by Apple (since 10.12).

  * All formal Java and property names are "MacOS".

  * The description and documentation sometimes refers to "macOS" instead.

  * Java 9 is required, but I have tested it only with Java 11. It
builds on any OS, e.g. Linux. There is no way to build or use this with
Java 8.


What needs to be done to publish this plugin officially? There should be
no conflict with the existing MacOSX plugin (which is frozen at version
1.3).

Also note that the app launcher for macOS needs to be revisited: it
probably should make a clear decision for the Java version and the
plugin to use.


	Makarius

On 29/05/2019 01:56, Alan Ezust wrote:
> Hi Dale,
> Have you tried changing the L&F while running jEdit inside openJDK 11
> (linux)?

I did not notice anything particular in this respect: it should work
mostly as before.

One note concerning OpenJDK: there are many versions (too many), and I
have converged to use exclusively https://adoptopenjdk.net (bundled with
the application).


> I don't normally use alternate L&Fs so I wouldn't have tried this except
> for when Makarius mentioned that the GTK L&F is nicer in 11, I was
> slightly curious to see it.

Java 11 tries to support GTK 3, but it does not quite work. There were
even some recent announcements saying one should switch back to GTK 2.2.


	Makarius

re: Oracle Licensing of Java.

re:
https://community.software.sil.org/t/oracle-changed-license-for-java-se-8-you-must-decide-what-to-do-dab/2184

A recommendation from another discussion group is to use Coretto. (
https://aws.amazon.com/corretto/) I've never heard of Coretto, but I
thought I'd throw it out here, for anyone who might be experiencing issues
(especially replacing JavaFX, which according to the other discussion is
fully supported in Coretto.)



On Wed, May 8, 2019 at 9:24 PM Jesse Pavel <jp...@al...> wrote:

> Hi Michael,
>
> Just for running jEdit, I'd recommend using OpenJDK 8 with the Hotspot JVM.
>
> Either the JDK or JRE will work fine, unless you're planning to compile
> Java code on your own, in which case you'd need the JDK.
>
> Best,
> Jesse
>
>
> On Wed, May 8, 2019 at 5:28 PM Michael H <cm...@gm...> wrote:
>
>> Thanks Jesse,
>>
>> Do you recommend (for jedit)
>> OpenJDK 8 (LTS) or OpenJDK 11 (LTS)?
>> Hotspot or OpenJ9 for the VM
>> Is there any benefit within Jedit program to installing the full JDK.  I
>> run recorded macro beanshell scripts (that are then pretty heavily
>> modified,) but that's as close to programming as I get.
>>
>> On Wed, May 8, 2019 at 4:16 PM Jesse Pavel <jp...@al...> wrote:
>>
>>> Hi Michael,
>>>
>>> You can get pre-built OpenJDK binaries (including installers) for the
>>> Mac from
>>>
>>>   https://adoptopenjdk.net/releases.html#x64_mac
>>>
>>> Once you have that installed, you should be able to remove the Oracle
>>> JRE, and needn't worry about the licensing changes.
>>>
>>> Best,
>>> Jesse
>>>
>>>
>>> On Wed, May 8, 2019 at 4:38 PM Michael H <cm...@gm...> wrote:
>>>
>>>> I booted a mac for the first time in a few months and Java wanted to
>>>> update.  This time it included a lot red letters warning me the license for
>>>> the JRE has changed, and is now personal use only.
>>>>
>>>> I don't understand well enough, but the JRE is required to run jedit,
>>>> and stuff that I edit with jedit may then be released with a Creative
>>>> Commons license which does not exclude commercial activity.  I feel like
>>>> this exceeds the license which Oracle is now extending.
>>>>
>>>> So I'm reading about how to avoid having to keep up with an apparently
>>>> time limited license, and it seems OpenJDK is the answer. OpenJDK is
>>>> already on linux, but its not clearly available for mac, and although I can
>>>> deal with installing it, I'm not sure on a system that already has both
>>>> Apple JRE and Oracle JRE that I can effectively remove any
>>>> unlicensed/improper to use for a CC3-BY license release. Does anyone have
>>>> pointers to expert advice on the use of something like jedit in Oracles new
>>>> licensing scheme? I've already been working on putting my mac out to
>>>> pasture. This may have accelerated the process.
>>>> --
>>>> -----------------------------------------------
>>>> jEdit Developers' List
>>>> jEd...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>
>>>

I see I only replied to Alan - I'm traveling without my laptop at the
moment. I'm pretty sure I've tested jEdit with Java 10 and 11, but maybe it
was 9 and 10. I'll check next week.

Dale



On Wed, May 29, 2019, 11:24 AM Makarius <mak...@sk...> wrote:

> On 29/05/2019 01:56, Alan Ezust wrote:
> > Hi Dale,
> > Have you tried changing the L&F while running jEdit inside openJDK 11
> > (linux)?
>
> I did not notice anything particular in this respect: it should work
> mostly as before.
>
> One note concerning OpenJDK: there are many versions (too many), and I
> have converged to use exclusively https://adoptopenjdk.net (bundled with
> the application).
>
>
> > I don't normally use alternate L&Fs so I wouldn't have tried this except
> > for when Makarius mentioned that the GTK L&F is nicer in 11, I was
> > slightly curious to see it.
>
> Java 11 tries to support GTK 3, but it does not quite work. There were
> even some recent announcements saying one should switch back to GTK 2.2.
>
>
>         Makarius
>

Hi Dale,
Have you tried changing the L&F while running jEdit inside openJDK 11
(linux)?
It doesn't work at all for me.
I don't normally use alternate L&Fs so I wouldn't have tried this except
for when Makarius mentioned that the GTK L&F is nicer in 11, I was slightly
curious to see it.

Hi Makarius,

I have a variable called JEDITSVN which is set to svn+ssh://
ez...@sv.../p/jedit/svn
Then I can check out any SVN plugin using the variable like this:

$ svn co $JEDITSVN/plugins/MacOS/trunk MacOS

On Tue, May 28, 2019 at 1:45 PM Makarius <mak...@sk...> wrote:

> On 28/05/2019 21:19, Alan Ezust wrote:
> >
> > The original MacOSX plugin is still in Subversion, so I guess we should
> > create a new git repo for the MacOS plugin.
>
> My plan was to use svn2git on Linux, but I cannot even make a plain svn
> checkout.
>
> The web view https://sourceforge.net/p/jedit/svn/HEAD/tree/plugins shows
> a command-line "svn checkout --username=makarius
> svn+ssh://makarius@svn.code.sf.net/p/jedit/svn/jEdit/trunk/ jedit-svn",
> but that is the main jEdit repository.
>

Yes, the wrong address is shown there. I don't know how to fix that.


>
> What is the proper URL for "plugins" or "plugins/MacOSX"?
>
>
>         Makarius
>

On 28/05/2019 21:19, Alan Ezust wrote:
>
> The original MacOSX plugin is still in Subversion, so I guess we should
> create a new git repo for the MacOS plugin.

My plan was to use svn2git on Linux, but I cannot even make a plain svn
checkout.

The web view https://sourceforge.net/p/jedit/svn/HEAD/tree/plugins shows
a command-line "svn checkout --username=makarius
svn+ssh://makarius@svn.code.sf.net/p/jedit/svn/jEdit/trunk/ jedit-svn",
but that is the main jEdit repository.

What is the proper URL for "plugins" or "plugins/MacOSX"?


	Makarius

On 28/05/2019 21:19, Alan Ezust wrote:
> 
> The original MacOSX plugin is still in Subversion, so I guess we should
> create a new git repo for the MacOS plugin.
> Importing the history from svn to git is possible using open source
> tools. I recommend doing that.
> You now have permissions to create the git repo and do the importing.

I've had a brief look at
https://sourceforge.net/p/jedit/svn/HEAD/tree/plugins -- there is an
older MacOS plugin and a newer MacOSX plugin. This corresponds to the
history of names for the Apple Mac Operating System. Here are some more
recent names of the thing:

  Mac OS X 10.10 Yosemite
  Mac OS X 10.11 El Capitan
  macOS 10.12 Sierra
  macOS 10.13 High Sierra
  macOS 10.14 Mojave

The plugin for Java 11 requires de-facto a relatively recent version of
the OS to work really well. The last 3 called "macOS" should be fine,
which is the reason for proposal to use this name for the plugin now.

Is it OK to start a plugin name with lowercase?


BTW, this odd confusion of plugin names and underlying Java versions
will continue with the app bundle for a standalone application on macOS.
A choice needs to be made if it runs on Java 8 or Java 11, and the
appropriate plugin needs to be used.

Now we are back to my tendency to assume that the Java version is >= 11
overall. At least on macOS that should be (almost) always the case: Mac
users are usually quite up-to-date.


	Makarius

---

** [bugs:#4082] Windows 10: NPE in sun.awt.windows.WInputMethod on main view focus change**

**Status:** open
**Group:** minor bug
**Created:** Tue May 28, 2019 07:46 PM UTC by Makarius
**Last Updated:** Tue May 28, 2019 07:46 PM UTC
**Owner:** nobody
**Attachments:**

- [npe.log](https://sourceforge.net/p/jedit/bugs/4082/attachment/npe.log) (5.5 kB; text/x-log)


This is jEdit 5.5.0 on Windows 10 with Java 8u181 or OpenJDK 11.0.3+7 (from adoptopenjdk.net).

Start jEdit regularly, e.g. via "java -jar jedit.jar"; switch to another window; click into the main jEdit view to reactive its focus. Each time this happens, there is an NPE in sun.awt.windows.WInputMethod (see the included log file).

My impression is that it only happens on relatively recent Windows 10. Activation of a dockable jEdit window (not main view) does not have this effect.


---

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.

Makarius,

The original MacOSX plugin is still in Subversion, so I guess we should
create a new git repo for the MacOS plugin.
Importing the history from svn to git is possible using open source tools.
I recommend doing that.
You now have permissions to create the git repo and do the importing.

If you need help building something, you can ask here for help.
As for test infrastructure, some people have started that on some parts of
jEdit but it is not formalized yet.



On Tue, May 28, 2019 at 12:12 PM Makarius <mak...@sk...> wrote:

> On 28/05/2019 20:58, Alan Ezust wrote:
> > The MacOS plugin can be updated to require Java11. I have no objection
> > to that.
> > It needs a new maintainer by the way. I don't have a mac anymore, so I
> > can't do mac development.
> > I do have a mac VM running sierra (not high sierra) so I can
> > occasionally boot it up to do testing but it is not suitable for
> > development.
>
> Normally, I am using Linux, but I have a macMini for this kind of
> testing, with 3-4 versions of macOS (the OS name keeps changing).
>
> I can update the MacOSX plugin, if you grant me sufficient commit rights
> -- I only have them for main jEdit so far. Another possibility is to
> create a new plugin called "macOS".
>
> Note that I don't quite understand the jEdit plugin build and test
> infrastructure.
>
>
>         Makarius
>

On 28/05/2019 20:58, Alan Ezust wrote:
> The MacOS plugin can be updated to require Java11. I have no objection
> to that.
> It needs a new maintainer by the way. I don't have a mac anymore, so I
> can't do mac development.
> I do have a mac VM running sierra (not high sierra) so I can
> occasionally boot it up to do testing but it is not suitable for
> development.

Normally, I am using Linux, but I have a macMini for this kind of
testing, with 3-4 versions of macOS (the OS name keeps changing).

I can update the MacOSX plugin, if you grant me sufficient commit rights
-- I only have them for main jEdit so far. Another possibility is to
create a new plugin called "macOS".

Note that I don't quite understand the jEdit plugin build and test
infrastructure.


	Makarius

The MacOS plugin can be updated to require Java11. I have no objection to
that.
It needs a new maintainer by the way. I don't have a mac anymore, so I
can't do mac development.
I do have a mac VM running sierra (not high sierra) so I can occasionally
boot it up to do testing but it is not suitable for development.

On 28/05/2019 20:03, Alan Ezust wrote:
> 
> What problem does dropping support for Java 8 solve? Is it mac-specific?
> Are there things we need to use from Java 11 in jEdit core to make
> things better? What if it's just the MacOS plugin ?

The MacOSX plugin is indeed a major discontinuity, but my updated
version explicitly requests Java 11 (actually Java 9), so I suppose
jEdit running Java 8 will ignore it and stick to an older version. See
the current patch from
https://isabelle.sketis.net/repos/isabelle-release/file/Isabelle2019-RC3/src/Tools/jEdit/patches/macosx

There were various other details where I was glad to have only  Java 11
to care of, although some users complained about it and wanted to stay
with the (officially end-of-lived Java 8): most notably the quite
different font rendering that is now uniform for OpenJDK and Oracle JDK
(note that the latter cannot be used anymore without a paid license, but
its font rendering as as good or bad as in OpenJDK).


Here are few more changes motivated by Java 11 -- what I can remember on
the spot and what the Isabelle repository history tells:

  * "Lucida Sans Typewriter" is no longer bundled with Java 11. My old
patch of the menu shortcut font no longer works. In fact, it is
presently unclear to me which font would work properly in all versions
on all platforms, so I merely made an adhoc patch to use the "Isabelle
DejaVu" font that is bundled with Isabelle/jEdit, see
https://isabelle.sketis.net/repos/isabelle-release/file/Isabelle2019-RC3/src/Tools/jEdit/patches/accelerator_font

  * The GTK+ look&feel in Java 11 works better and more robustly with
-Djdk.gtk.version=2.2 (that property is ignored by Java 8).

  * The home-made jEdit splash screen (JWindow) on Java 11 had some
problems with certain Linux/X11 window managers; I simply disabled it
uniformly and used java option -splash instead, see
https://isabelle.sketis.net/repos/isabelle-release/rev/089753519be0

  * The Java 11 "java" command is better invoked with option
"--illegal-access=warn" to expose old-style reflective access to
libraries by other people. That is a genuine incompatibility with Java
8, and I am actually delivering Isabelle2019 without that option as a
concession to users who insist in old Java 8; it makes warnings on Java
11 more ugly.


So with some effort it should be possible to do all this for Java 11,
while still supporting Java 8. It is just one of my habits to target
only one major version, and support that really well: I chose Java 11,
but did not fully succeed in all respects yet. Java 8 is semi-supported
right now, and Java 11 has very fine points remaining.


	Makarius

What problem does dropping support for Java 8 solve? Is it mac-specific?
Are there things we need to use from Java 11 in jEdit core to make things
better? What if it's just the MacOS plugin ?



On Tue, May 28, 2019 at 8:26 AM Makarius <mak...@sk...> wrote:

> On 28/05/2019 16:28, Alan Ezust wrote:
> > The nicest thing about jEdit is that it depends only on Java, and no
> > other libraries or toolkits.
> > That way, it can run on java8, 9, 10, 11, 12, on all platforms.
> > Depending on JavaFX would mess that up.
>
> Side-remark: Java 8 to Java 11 is a notable discontinuity; the
> intermediate steps 9 + 10 can be skipped.
>
> Many details need to be revised to make jEdit work smoothly on Java 11:
> I am 99% there with the Isabelle/jEdit distribution, but some fine
> points are still missing. See also
> https://sketis.net/2019/release-candidates-for-isabelle2019
>
> Nonetheless, I would argue for leaving Java 8 behind and move on  to
> Java 11 right now, i.e. make a new jEdit release that strictly requires
> Java 11. Like the switch from Java 6 to Java 7, this will cause some
> pain, but is sooner or later inevitable. (My guess is that Java 8 will
> stay around some time like Windows XP: many user still stuck with it,
> but better left behind.)
>
>
>         Makarius
>

On 28/05/2019 16:28, Alan Ezust wrote:
> The nicest thing about jEdit is that it depends only on Java, and no
> other libraries or toolkits.
> That way, it can run on java8, 9, 10, 11, 12, on all platforms.
> Depending on JavaFX would mess that up.

Side-remark: Java 8 to Java 11 is a notable discontinuity; the
intermediate steps 9 + 10 can be skipped.

Many details need to be revised to make jEdit work smoothly on Java 11:
I am 99% there with the Isabelle/jEdit distribution, but some fine
points are still missing. See also
https://sketis.net/2019/release-candidates-for-isabelle2019

Nonetheless, I would argue for leaving Java 8 behind and move on  to
Java 11 right now, i.e. make a new jEdit release that strictly requires
Java 11. Like the switch from Java 6 to Java 7, this will cause some
pain, but is sooner or later inevitable. (My guess is that Java 8 will
stay around some time like Windows XP: many user still stuck with it,
but better left behind.)


	Makarius

The nicest thing about jEdit is that it depends only on Java, and no other
libraries or toolkits.
That way, it can run on java8, 9, 10, 11, 12, on all platforms.
Depending on JavaFX would mess that up.


On Mon, May 20, 2019 at 4:34 AM Dale Anson <da...@da...> wrote:

> No, there are no plans to convert to JavaFX.
>
> On Mon, May 20, 2019, 3:53 AM Infected Engineers <
> inf...@gm...> wrote:
>
>> Could anyone please answer below question?
>>
>> Regards,
>> Infected Engineers
>>
>> On Sat, 18 May, 2019, 9:49 AM Infected Engineers, <
>> inf...@gm...> wrote:
>>
>>> Hello Everyone,
>>> I have started to use JEdit recently. I just wanted to know if JEdit UI
>>> will ever upgrade to JavaFX?
>>>
>>> Regards,
>>> Infected Engineers
>>>
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEd...@li...
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>

I see it says fixed - but I am getting this:

![](http://https://i.imgur.com/sj2WgMO.png)

That is with the plugin as installed through the jedit plugin manager.  Is there some trick to have it allow [] array syntax?


---

** [plugin-bugs:#1843] PHP 5.4+ short array syntax not recognized in PHPParser**

**Status:** closed-fixed
**Group:** 
**Created:** Tue Feb 09, 2016 03:24 PM UTC by Dynamo Dan
**Last Updated:** Sun Dec 17, 2017 09:14 AM UTC
**Owner:** Matthieu Casanova
**Attachments:**

- [jEdit.png](https://sourceforge.net/p/jedit/plugin-bugs/1843/attachment/jEdit.png) (139.5 kB; image/png)


jEdit 5.3, PHPParser 2.0.5, Ubuntu 12.04 (although I fully expect the bug is on all platforms) Oracle Java 1.7.0_80.  The version of PHP installed on my system is 5.5.

Steps to reproduce:
1. write any code that uses the new short array syntax described in the PHP 5.4 "New features" page on php.net: http://php.net/manual/en/migration54.new-features.php
2. Open a sidekick panel and a error panel as shown in the screenshot.
3. Try to expand any class nodes as shown in the screenshot.
4. Observe the lack of class methods beyond the one in which syntax errors are found.
5. Observe the syntax errors incorrectly reported in the error list panel.



---

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.

No, there are no plans to convert to JavaFX.

On Mon, May 20, 2019, 3:53 AM Infected Engineers <
inf...@gm...> wrote:

> Could anyone please answer below question?
>
> Regards,
> Infected Engineers
>
> On Sat, 18 May, 2019, 9:49 AM Infected Engineers, <
> inf...@gm...> wrote:
>
>> Hello Everyone,
>> I have started to use JEdit recently. I just wanted to know if JEdit UI
>> will ever upgrade to JavaFX?
>>
>> Regards,
>> Infected Engineers
>>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>

Could anyone please answer below question?

Regards,
Infected Engineers

On Sat, 18 May, 2019, 9:49 AM Infected Engineers, <
inf...@gm...> wrote:

> Hello Everyone,
> I have started to use JEdit recently. I just wanted to know if JEdit UI
> will ever upgrade to JavaFX?
>
> Regards,
> Infected Engineers
>

On 18/05/2019 06:19, Infected Engineers wrote:

> I have started to use JEdit recently. I just wanted to know if JEdit UI
> will ever upgrade to JavaFX?

This was discussed occasionally in recent years, but I don't see that
coming.

When JavaFX was first released with Java 7, I was excited to see some
moves in Java GUI technology, but it turned out "too late, too little".
In current Java 11, JavaFX has been "unbundled", i.e. it is an
independent project and even less likely to become the next Java GUI
environment that everybody uses.

So for myself, I am still with classic AWT/Swing -- I am talking here as
the producer of Isabelle/jEdit, see
https://isabelle.in.tum.de/website-Isabelle2019-RC2 (which is already on
Java 11, in contrast to official jEdit).


An alternative for the future might be Java Chromium Embedded Framework
(JCEF) https://bitbucket.org/chromiumembedded/java-cef/src/master -- as
a start it could be used for browsing HTML documentation. A more
ambitious project could imitate editor technology in the style of VSCode
inside jEdit with Chromium-based dockables etc.


	Makarius

Hello Everyone,
I have started to use JEdit recently. I just wanted to know if JEdit UI
will ever upgrade to JavaFX?

Regards,
Infected Engineers

I am running the jenkins daily build server for jEdit.
Today, I noticed the watchbog virus, which I am pretty sure is there
because of Jenkins.
So no daily builds until further notice.

---

** [bugs:#4081] File Browser's collapse button**

**Status:** open
**Group:** minor bug
**Labels:** File browser collapse-button 
**Created:** Tue May 14, 2019 10:01 AM UTC by SAI SUBASH MALLIREDDY
**Last Updated:** Tue May 14, 2019 10:01 AM UTC
**Owner:** nobody
**Attachments:**

- [Screenshot (62)_LI.jpg](https://sourceforge.net/p/jedit/bugs/4081/attachment/Screenshot%20%2862%29_LI.jpg) (177.2 kB; image/jpeg)


Inside the File Browser widget the collapse button isn't collapsing the above section of it where the current directory details are displayed.


---

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.