Black Hole
May contain traces of nut
I take that to mean line 33, which is indeed the second occurrence.l.33 of/mod/webif/html/browse/rename.jim
.
I take that to mean line 33, which is indeed the second occurrence.l.33 of/mod/webif/html/browse/rename.jim
.
It might be a difficult idea to implement, while many packages store settings in webif.db others don't and often the key names differ from the menu settings name plus there are the various Humax settings on various settings pagesThe addition of a "find" search box to the WebIF home page would prove useful to some, who don't know where to find some of the settings (I sometimes have to hunt).
Yes. I was forgetting the WebIF pages are generated dynamically instead of being static HTML (which would be easy to search).It might be a difficult idea to implement, while many packages store settings in webif.db others don't and often the key names differ from the menu settings name plus there are the various Humax settings on various settings pages
Be still my beating heartI was just about to post this before all the excitement started this morning...
Got a bad head cold?Be still by beating heart
TheI was just about to post this before all the excitement started this morning...
The WebIf (1.4.9-5 in use) doesn't seem to handle folder names containing commas properly. Here is an example of two folders containing identical content that don't display properly:
...
class="filesize"
span element is present but not populated. This depends on calculating an ID string from the folder name in JS that is the same as the ID when generated from the folder name in Jim. Sadly, we get for a folder with name "Flow,ers":JS: "RmxvdyUyQ2Vycw"
Jim: "RmxvdyxlcnM"
escape()
makes ',' into '%2C' but the Jim proc ::js::escape
that is meant to be equivalent doesn't. In turn this is because in a bracket expression in a regular expression the character '-' has to be first or last in the set of characters and ranges. Therefore:--- a/webif/lib/utils
+++ b/webif/lib/utils
@@ -102,7 +102,7 @@
proc ::js::escape {str} {
return [subst -nobackslashes -novariables \
- [regsub -all -- {[^A-Za-z0-9@*_+-./]+} $str \
+ [regsub -all -- {[^A-Za-z0-9@*_+./-]+} $str \
{[::js::_escape {&}]}]]
}
I knew you'd know! Thanks, that one would have taken me days...In turn this is because in a bracket expression in a regular expression the character '-' has to be first or last in the set of characters and ranges.
subst
that I took my eye off man -k 7 regex
.