|
From: Shlomy R. <sre...@gm...> - 2009-08-24 21:23:19
|
On Mon, Aug 24, 2009 at 10:06 PM, Shlomy Reinstein<sre...@gm...> wrote: >>> [snip] You can find a fixed version here: http://community.jedit.org/?q=node/view/4253 >>> You can now specify mode-specific fold strings and they should work fine. >>> >> Hmm, I just tested Your last version. I think it works different in the >> way that I could deactivate "use default fold strings" for the desired >> mode and the folds hasn't gone away. But nevertheless only the default >> fold strings are applied. >> >> Robert > > Strange, I tested it and it worked fine... Can you provide a precise > scenario where this does not work as expected? It would be best if you > could attach a small sample file to demonstrate it, along with the > reproduction steps. > > Shlomy > Just now I tested it again and it seemed at first to work like you wrote - i.e. after deactivating the check-box, the folds haven't gone away but remained the same. It took me some time to realize that the buffer had "buffer local properties" that caused the folding mode to become "explicit" on each load, so "custom" folding mode was inactive... as soon as I changed back to "custom", it started working fine - activating / deactivating the check-box switched between the two fold strings. So, if you get this again, please make sure that: 1. You are using "custom" folding mode for the buffer (the folding mode is specified on the status bar by default). 2. You have changed the fold strings settings for the correct mode (the buffer mode is also specified in the status bar). Or, can it be that you're using my first fix for the ConfigurableFoldHandler plugin, that just resolves the performance problem? I created two different "plugin beta version" files in the community site - first one for the performance fix, second one that included both the performance fix and the mode-specific fold strings fix. I am not sure that the same link that was used for the first version is also used for the second... Shlomy |