Dear LXR developers, The default ctags used in Linux system is Exuberant Ctags (v5.8). And its development has stopped since 2009. Should LXR switch to use the forked ctags, Universal Ctags? It has many improvements, and new features/languages added. I tried it and found the LXR configuration works fine with it except the kind letter 'F' used for SQL2 in the file templates/ectags.conf, because the kind letter 'F' is reserved in the Universal Ctags. And LXR could make use of the new development in...
Dear LXR developers, The default ctags used in Linux system is Exuberant Ctags (v5.8). And its development has stopped since 2009. Should LXR switch to use the forked ctags, Universal Ctags? It has many improvements, and new features/languages added. I tried it and found the LXR configuration works fine with it except the kind letter 'F' used for SQL2 in the file templates/ectags.conf, because the kind letter 'F' is served in the Universal Ctags. And LXR could make use of the new development in the...
Sorry, again I missed the backslash \ in the ful expanded expression. Without a parenthesis, the full expanded regular expression would become '\.bitmap|bmp|gif|icon?|jp2|jpe?g|pjpe?g|png|svg|tiff?|xbm|xpm$' Thus it could match any string containing ".bitmap", "gif" or "tif", or string ending with "xpm", right? Best, Shuwei
Hi Andre-Littoz, Sorry, when I copied the line onto the bug report page, the backslach \ was somehow removed by the system? Since the value graphicfile in the configuration file lxr.conf is set to 'bitmap|bmp|gif|icon?|jp2|jpe?g|pjpe?g|png|svg|tiff?|xbm|xpm' Without a parenthesis, the full expanded regular expression would become '.bitmap|bmp|gif|icon?|jp2|jpe?g|pjpe?g|png|svg|tiff?|xbm|xpm$' Thus it could match any file with an extension ".bitmap", or any string containing "gif" or "tif". etc, right?...
unparenthesized multiple regular image file patterns