lxr-developer Mailing List for LXR Cross Referencer (Page 7)
Brought to you by:
ajlittoz
Menu
▾
▴
lxr-developer — Don't use, active developers only
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(11) |
Jun
(21) |
Jul
(14) |
Aug
(83) |
Sep
(23) |
Oct
(37) |
Nov
(52) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(28) |
Feb
(40) |
Mar
(21) |
Apr
(8) |
May
(21) |
Jun
(13) |
Jul
(9) |
Aug
(5) |
Sep
(8) |
Oct
(7) |
Nov
(2) |
Dec
|
| 2003 |
Jan
(2) |
Feb
(1) |
Mar
(11) |
Apr
(4) |
May
(6) |
Jun
(15) |
Jul
(4) |
Aug
(4) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2004 |
Jan
(4) |
Feb
|
Mar
(4) |
Apr
(12) |
May
(5) |
Jun
(9) |
Jul
(47) |
Aug
(1) |
Sep
(1) |
Oct
(7) |
Nov
|
Dec
(1) |
| 2005 |
Jan
(4) |
Feb
(2) |
Mar
(3) |
Apr
(10) |
May
(9) |
Jun
(15) |
Jul
(3) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(10) |
Dec
(4) |
| 2006 |
Jan
(1) |
Feb
|
Mar
(9) |
Apr
(5) |
May
(1) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
|
Dec
(3) |
| 2007 |
Jan
(2) |
Feb
(1) |
Mar
(32) |
Apr
(3) |
May
(3) |
Jun
(16) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(4) |
Dec
(3) |
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(46) |
Apr
(70) |
May
(15) |
Jun
(13) |
Jul
(1) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(5) |
Feb
(4) |
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(7) |
Nov
(6) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(85) |
Apr
(18) |
May
(4) |
Jun
(3) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(20) |
| 2012 |
Jan
(17) |
Feb
(16) |
Mar
(13) |
Apr
(18) |
May
|
Jun
(6) |
Jul
(6) |
Aug
(10) |
Sep
(15) |
Oct
(10) |
Nov
(25) |
Dec
(1) |
|
From: SourceForge.net <no...@so...> - 2011-12-21 20:08:20
|
Bugs item #3463504, was opened at 2011-12-21 12:05 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3463504&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: genxref Group: current cvs Status: Open >Resolution: Fixed Priority: 7 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Missing test for ectagsbin existence in genxref Initial Comment: If config parameter 'ectagsbin' is not defined, sub indexfile in Generic.pm will silently ignore the tagging phase leading to erratic behaviour later when browsing the source-tree (from inaccurate marking to no marking at all, depending on the state of the DB). A test should be made in genxref to abort as early as possible the task with a self-explanatory error message. ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 12:08 Message: Test made in genxref with an attempt to find ctags (which ctags). If ctags can be found, config parameter is temporarily adjusted with a caveat to user. Unhappily, the warning message can go unnoticed in genxref output. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 12:08 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3463504&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-12-21 20:05:01
|
Bugs item #3463504, was opened at 2011-12-21 12:05 Message generated for change (Tracker Item Submitted) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3463504&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: genxref Group: current cvs Status: Open Resolution: None Priority: 7 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Missing test for ectagsbin existence in genxref Initial Comment: If config parameter 'ectagsbin' is not defined, sub indexfile in Generic.pm will silently ignore the tagging phase leading to erratic behaviour later when browsing the source-tree (from inaccurate marking to no marking at all, depending on the state of the DB). A test should be made in genxref to abort as early as possible the task with a self-explanatory error message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3463504&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-12-21 17:44:26
|
Bugs item #3330950, was opened at 2011-06-25 06:31 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3330950&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: current cvs >Status: Closed Resolution: Accepted Priority: 3 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Generic.pm does unnecessary initialisation Initial Comment: Initialisation of generic parser is don in sub read_config. Since it is called only once, it is a good place to proceed with various tests, such as tools version number. This is done with the Perl backtick construct, executing a shell command as an independent process. Some security rules may forbid such a parallel execution from a web server (e.g. on SourceForge). Thus, initialisation aborts and LXR can't display files. To circumvent the problem, initialisation should detect whether it is call from shell contect (i.e. from genxref) or from web context. Since there is no need of ctags in web context, this verification should not be attempted. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 09:44 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 09:43 Message: All the tests on auxiliary tools have been moved to genxref which is easier since genxref is executed in shell context. Moreover, LXR data is always initialised by genxref which is run only once in a while, at least not every time you need LXR. Change in CVS for next release (0.10). ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 09:43 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3330950&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-12-21 17:43:44
|
Bugs item #3330950, was opened at 2011-06-25 06:31 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3330950&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: current cvs Status: Open >Resolution: Accepted Priority: 3 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Generic.pm does unnecessary initialisation Initial Comment: Initialisation of generic parser is don in sub read_config. Since it is called only once, it is a good place to proceed with various tests, such as tools version number. This is done with the Perl backtick construct, executing a shell command as an independent process. Some security rules may forbid such a parallel execution from a web server (e.g. on SourceForge). Thus, initialisation aborts and LXR can't display files. To circumvent the problem, initialisation should detect whether it is call from shell contect (i.e. from genxref) or from web context. Since there is no need of ctags in web context, this verification should not be attempted. ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 09:43 Message: All the tests on auxiliary tools have been moved to genxref which is easier since genxref is executed in shell context. Moreover, LXR data is always initialised by genxref which is run only once in a while, at least not every time you need LXR. Change in CVS for next release (0.10). ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 09:43 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3330950&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-12-21 17:36:22
|
Feature Requests item #3289779, was opened at 2011-04-19 12:56 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=3289779&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Browsing Interface Group: None >Status: Closed Priority: 5 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Nobody/Anonymous (nobody) Summary: Remove interaction between variables and URL args Initial Comment: Variables are passed to diff, ident, search and source scripts as varname=value while state information and requests are also passed as param=value. If a variable is given the same name as a state information argument (e.g. showattic or raw), mayhem may result. To avoid this potential problem, use a prefix for all internal URL args, e.g. a dot, and forbid that prefix in variable names. ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-21 09:36 Message: The interaction has been removed by prefixing all internal parameters with an underscore _. A new rule/restriction will be added to the documentation to forbid an initial underscore or dollar in variable names. The rationale for the dollar is the need to override user variable value without resorting to a script. At the next LXR invocation, sub httpinit will do the trick before relinquishing control to the specific script. Code is in CVS for the next release (0.10). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=3289779&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-12-06 21:19:17
|
Feature Requests item #3452739, was opened at 2011-12-06 12:17 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=3452739&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None Group: None Status: Open >Priority: 3 Private: No Submitted By: arno. (arno-) >Assigned to: Andre-Littoz (ajlittoz) Summary: JavaScript support Initial Comment: Hi, Here is a patch for minimal JavaScript support. My installation index a project containing (among other) many JavaScript files, and I've used this patch for many years. Regards ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-12-06 13:19 Message: Well, it is rather a "feature request" than a bug because there is not yet JavaScript support in LXR. I received a contribution from a user a couple of weeks ago about that same JavaScript support. I'll compare and merge your patches. Time permitting, I'll tru to release a new version before the beginning of next year. Stay tuned. ajl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=3452739&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-12-06 20:17:33
|
Bugs item #3452739, was opened at 2011-12-06 12:17 Message generated for change (Tracker Item Submitted) made by arno- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3452739&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: arno. (arno-) Assigned to: Nobody/Anonymous (nobody) Summary: JavaScript support Initial Comment: Hi, Here is a patch for minimal JavaScript support. My installation index a project containing (among other) many JavaScript files, and I've used this patch for many years. Regards ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3452739&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 08:45:39
|
Bugs item #3434724, was opened at 2011-11-07 17:38 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3434724&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: SCM support >Group: current cvs Status: Open Resolution: None Priority: 5 Private: No Submitted By: Blade Doyle (bladedoyle) >Assigned to: Andre-Littoz (ajlittoz) Summary: CVS.pm does not work with branching tags Initial Comment: LXR version: 0.9.10 No indexes are created for branched tags Using CVS.pm ---------------------- The "CVS.pm" code for "sub parsecvs" does not work with branching tags. No indexes are created for them. For branches RCS version numbers contain a "0" to indicate they are a branch. When mapping 'symbols' to a real revision number the code needs to find what actual revision number for a branching tag is. Currently for a branched tag the parsecvs function looks through the rcs file and finds that a branching tag (ex: FOO) is associated with revision (ex: 1.2.0.3). But that isn't an actual revision number 1.2.0.3. So we need some additional code in the parsecvs function to find the actual revision number for branched tags. I am attaching an example of some code that appears to solve the problem. (I don't claim to be an expert on the RCS file format but I looked at a few rcs files and found a pattern that seems to hold up) ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-11-09 00:45 Message: Thanks Blade. I'll make tests as soon as I have some spare time and see if it can be made into a generic rule. I'll issue a 0.10 release when checking is complete. ajl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3434724&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-11-08 01:38:55
|
Bugs item #3434724, was opened at 2011-11-07 17:38 Message generated for change (Tracker Item Submitted) made by bladedoyle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3434724&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Blade Doyle (bladedoyle) Assigned to: Nobody/Anonymous (nobody) Summary: CVS.pm does not work with branching tags Initial Comment: LXR version: 0.9.10 No indexes are created for branched tags Using CVS.pm ---------------------- The "CVS.pm" code for "sub parsecvs" does not work with branching tags. No indexes are created for them. For branches RCS version numbers contain a "0" to indicate they are a branch. When mapping 'symbols' to a real revision number the code needs to find what actual revision number for a branching tag is. Currently for a branched tag the parsecvs function looks through the rcs file and finds that a branching tag (ex: FOO) is associated with revision (ex: 1.2.0.3). But that isn't an actual revision number 1.2.0.3. So we need some additional code in the parsecvs function to find the actual revision number for branched tags. I am attaching an example of some code that appears to solve the problem. (I don't claim to be an expert on the RCS file format but I looked at a few rcs files and found a pattern that seems to hold up) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3434724&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-10-24 08:08:09
|
Bugs item #3427606, was opened at 2011-10-23 22:04 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3427606&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing >Group: current cvs Status: Open Resolution: None Priority: 5 Private: No Submitted By: sjs205 (sjs205) Assigned to: Nobody/Anonymous (nobody) Summary: .htaccess-apache2 doesn't work under Apache2.2 Initial Comment: The same as bug ID: 2783472: sudo tail /var/log/apache2/error.log -n 1 [Sun Oct 23 20:48:17 2011] [error] [client 86.147.245.75] failed to resolve handler `ModPerl::RegistryPrefork': This package can't be used under threaded MPMs at /usr/lib/perl5/ModPerl/RegistryPrefork.pm line 12.\nCompilation failed in require at (eval 3) line 3.\n $ apache2 -V Server version: Apache/2.2.14 (Ubuntu) Server built: Sep 1 2011 09:52:34 Server's Module Magic Number: 20051115:23 Server loaded: APR 1.3.8, APR-Util 1.3.9 Compiled using: APR 1.3.8, APR-Util 1.3.9 Architecture: 64-bit Server MPM: Worker threaded: yes (fixed thread count) forked: yes (variable process count) Server compiled with.... -D APACHE_MPM_DIR="server/mpm/worker" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D DYNAMIC_MODULE_LIMIT=128 -D HTTPD_ROOT="" -D SUEXEC_BIN="/usr/lib/apache2/suexec" -D DEFAULT_PIDLOG="/var/run/apache2.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types" -D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf" $ perl -v This is perl, v5.10.1 (*) built for x86_64-linux-gnu-thread-multi $ uname -a Linux DevBox 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010 x86_64 GNU/Linux If any further information is required then please ask. ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-10-24 10:08 Message: Hello, This problem seems to be related to the interaction between Perl and Apache. The main difference with my configuration is "Server MPM: Prefork" in mine. Try with the Perl guys and tell me about it. Meanwhile, I keep this bug open. Regards, ajl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3427606&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-10-23 20:04:02
|
Bugs item #3427606, was opened at 2011-10-23 21:04 Message generated for change (Tracker Item Submitted) made by sjs205 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3427606&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: sjs205 (sjs205) Assigned to: Nobody/Anonymous (nobody) Summary: .htaccess-apache2 doesn't work under Apache2.2 Initial Comment: The same as bug ID: 2783472: sudo tail /var/log/apache2/error.log -n 1 [Sun Oct 23 20:48:17 2011] [error] [client 86.147.245.75] failed to resolve handler `ModPerl::RegistryPrefork': This package can't be used under threaded MPMs at /usr/lib/perl5/ModPerl/RegistryPrefork.pm line 12.\nCompilation failed in require at (eval 3) line 3.\n $ apache2 -V Server version: Apache/2.2.14 (Ubuntu) Server built: Sep 1 2011 09:52:34 Server's Module Magic Number: 20051115:23 Server loaded: APR 1.3.8, APR-Util 1.3.9 Compiled using: APR 1.3.8, APR-Util 1.3.9 Architecture: 64-bit Server MPM: Worker threaded: yes (fixed thread count) forked: yes (variable process count) Server compiled with.... -D APACHE_MPM_DIR="server/mpm/worker" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D DYNAMIC_MODULE_LIMIT=128 -D HTTPD_ROOT="" -D SUEXEC_BIN="/usr/lib/apache2/suexec" -D DEFAULT_PIDLOG="/var/run/apache2.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types" -D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf" $ perl -v This is perl, v5.10.1 (*) built for x86_64-linux-gnu-thread-multi $ uname -a Linux DevBox 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010 x86_64 GNU/Linux If any further information is required then please ask. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3427606&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-08-01 08:41:11
|
Bugs item #3382013, was opened at 2011-07-29 11:30 Message generated for change (Comment added) made by kevinwalls You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: v0.9.9 >Status: Closed Resolution: Invalid >Priority: 1 Private: No Submitted By: Kevin Walls (kevinwalls) Assigned to: Andre-Littoz (ajlittoz) Summary: Missing dot in Generic.pm Initial Comment: LXR 0.9.9, but looks to be the same in 0.9.10 also. Nothing runs, basically. Sorry, lost the exact command but failure is: [Thu Jul 28 11:08:40 2011] [error] [client x.x.x.x] [Thu Jul 28 11:08:40 2011] fatal: main, line 224: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^\t\t\t\t\t# reminder: no initial space in the grammar, ...referrer info etc... This must need the following, a missing dot before a question-mark: diff -C 3 lib/LXR/Lang/Generic.pm.orig lib/LXR/Lang/Generic.pm *** lib/LXR/Lang/Generic.pm.orig Sun Mar 27 10:51:25 2011 --- lib/LXR/Lang/Generic.pm Fri Jul 29 11:27:50 2011 *************** *** 217,223 **** $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) --- 217,223 ---- $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (.?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) ..which runs fine. The same statement is in lib/LXR/Lang.pm WITH the missing dot in place. ---------------------------------------------------------------------- >Comment By: Kevin Walls (kevinwalls) Date: 2011-08-01 09:41 Message: Oooops - OK, sorry for the spam!... I can't explain this, but the released tarball is fine and my install has not only gained the dot we are talking about, but there is an extra TAB character on the same line... I have no idea where this comes from, it's not like I've been intentionally changing the file, I just went to look once I hit the error (in the other copy of the same expression). But, it looks like some craziness in my copy which is fixed by unpacking it again. I thought I'd stumbled on something useful/important, but really its just my own problem. Thanks for the guidance. 8-) ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-07-30 08:54 Message: I am upset by your comment: I checked both my working development copy and the reference I put on the lxr.sf.net site and found that the 0.9.9 and 0.9.10 versions of generic.pm and Lang.pm are identical. They have no dot in the (?| prefix flag construct. I didn't check the released tarball. Please verify your copy and tell me if I made an error. This would be a very serious bug. ---------------------------------------------------------------------- Comment By: Kevin Walls (kevinwalls) Date: 2011-07-29 22:47 Message: Ah right, thanks.. So I'm missing out on the include file stuff! I had wondered if I had a Perl version that was behind, but was happy things were running. 8-) (I just checked the same statement in lib/LXR/Lang.pm in 0.9.10 and I see now it has changed to REMOVE the dot, I guess I was fooled as I was looking at 0.9.9 and the dot was there.) ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-07-29 22:01 Message: No, your suggested fix doesn't solve the bug. I don't exactly know what it does, but sure, it messes up #include processing: the file name is reduced to the first delimiter (i.e. " or >) and the hyperlink is not generated. The cause is in Perl. Your version is probably 5.8.8 whereas the syntax is 5.10. See comments # 3 & 4 in topic "Help on non-regression test" of forum Help. It is covered in depth in the discussion. Basically, (?| requests that all captures in the alternatives keep the same numbers. Your proposed change says a first alternative (.?| optionnally captures a single character and is followed by a series of alternatives. Since the first always succeeds, the others are never tested. If you think that 5.8.8-flavoured Perl is still ubiquitous, I can issue rather quickly a 0.9.11 release to downgrade the syntax. The easiest way to go is to upgrade your Perl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-07-30 07:54:41
|
Bugs item #3382013, was opened at 2011-07-29 12:30 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: v0.9.9 >Status: Pending Resolution: Invalid Priority: 5 Private: No Submitted By: Kevin Walls (kevinwalls) Assigned to: Andre-Littoz (ajlittoz) Summary: Missing dot in Generic.pm Initial Comment: LXR 0.9.9, but looks to be the same in 0.9.10 also. Nothing runs, basically. Sorry, lost the exact command but failure is: [Thu Jul 28 11:08:40 2011] [error] [client x.x.x.x] [Thu Jul 28 11:08:40 2011] fatal: main, line 224: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^\t\t\t\t\t# reminder: no initial space in the grammar, ...referrer info etc... This must need the following, a missing dot before a question-mark: diff -C 3 lib/LXR/Lang/Generic.pm.orig lib/LXR/Lang/Generic.pm *** lib/LXR/Lang/Generic.pm.orig Sun Mar 27 10:51:25 2011 --- lib/LXR/Lang/Generic.pm Fri Jul 29 11:27:50 2011 *************** *** 217,223 **** $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) --- 217,223 ---- $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (.?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) ..which runs fine. The same statement is in lib/LXR/Lang.pm WITH the missing dot in place. ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-07-30 09:54 Message: I am upset by your comment: I checked both my working development copy and the reference I put on the lxr.sf.net site and found that the 0.9.9 and 0.9.10 versions of generic.pm and Lang.pm are identical. They have no dot in the (?| prefix flag construct. I didn't check the released tarball. Please verify your copy and tell me if I made an error. This would be a very serious bug. ---------------------------------------------------------------------- Comment By: Kevin Walls (kevinwalls) Date: 2011-07-29 23:47 Message: Ah right, thanks.. So I'm missing out on the include file stuff! I had wondered if I had a Perl version that was behind, but was happy things were running. 8-) (I just checked the same statement in lib/LXR/Lang.pm in 0.9.10 and I see now it has changed to REMOVE the dot, I guess I was fooled as I was looking at 0.9.9 and the dot was there.) ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-07-29 23:01 Message: No, your suggested fix doesn't solve the bug. I don't exactly know what it does, but sure, it messes up #include processing: the file name is reduced to the first delimiter (i.e. " or >) and the hyperlink is not generated. The cause is in Perl. Your version is probably 5.8.8 whereas the syntax is 5.10. See comments # 3 & 4 in topic "Help on non-regression test" of forum Help. It is covered in depth in the discussion. Basically, (?| requests that all captures in the alternatives keep the same numbers. Your proposed change says a first alternative (.?| optionnally captures a single character and is followed by a series of alternatives. Since the first always succeeds, the others are never tested. If you think that 5.8.8-flavoured Perl is still ubiquitous, I can issue rather quickly a 0.9.11 release to downgrade the syntax. The easiest way to go is to upgrade your Perl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-07-29 21:47:27
|
Bugs item #3382013, was opened at 2011-07-29 11:30 Message generated for change (Comment added) made by kevinwalls You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: v0.9.9 >Status: Open Resolution: Invalid Priority: 5 Private: No Submitted By: Kevin Walls (kevinwalls) Assigned to: Andre-Littoz (ajlittoz) Summary: Missing dot in Generic.pm Initial Comment: LXR 0.9.9, but looks to be the same in 0.9.10 also. Nothing runs, basically. Sorry, lost the exact command but failure is: [Thu Jul 28 11:08:40 2011] [error] [client x.x.x.x] [Thu Jul 28 11:08:40 2011] fatal: main, line 224: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^\t\t\t\t\t# reminder: no initial space in the grammar, ...referrer info etc... This must need the following, a missing dot before a question-mark: diff -C 3 lib/LXR/Lang/Generic.pm.orig lib/LXR/Lang/Generic.pm *** lib/LXR/Lang/Generic.pm.orig Sun Mar 27 10:51:25 2011 --- lib/LXR/Lang/Generic.pm Fri Jul 29 11:27:50 2011 *************** *** 217,223 **** $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) --- 217,223 ---- $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (.?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) ..which runs fine. The same statement is in lib/LXR/Lang.pm WITH the missing dot in place. ---------------------------------------------------------------------- >Comment By: Kevin Walls (kevinwalls) Date: 2011-07-29 22:47 Message: Ah right, thanks.. So I'm missing out on the include file stuff! I had wondered if I had a Perl version that was behind, but was happy things were running. 8-) (I just checked the same statement in lib/LXR/Lang.pm in 0.9.10 and I see now it has changed to REMOVE the dot, I guess I was fooled as I was looking at 0.9.9 and the dot was there.) ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-07-29 22:01 Message: No, your suggested fix doesn't solve the bug. I don't exactly know what it does, but sure, it messes up #include processing: the file name is reduced to the first delimiter (i.e. " or >) and the hyperlink is not generated. The cause is in Perl. Your version is probably 5.8.8 whereas the syntax is 5.10. See comments # 3 & 4 in topic "Help on non-regression test" of forum Help. It is covered in depth in the discussion. Basically, (?| requests that all captures in the alternatives keep the same numbers. Your proposed change says a first alternative (.?| optionnally captures a single character and is followed by a series of alternatives. Since the first always succeeds, the others are never tested. If you think that 5.8.8-flavoured Perl is still ubiquitous, I can issue rather quickly a 0.9.11 release to downgrade the syntax. The easiest way to go is to upgrade your Perl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-07-29 21:01:42
|
Bugs item #3382013, was opened at 2011-07-29 12:30 Message generated for change (Settings changed) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Lang support Group: v0.9.9 >Status: Pending >Resolution: Invalid Priority: 5 Private: No Submitted By: Kevin Walls (kevinwalls) >Assigned to: Andre-Littoz (ajlittoz) Summary: Missing dot in Generic.pm Initial Comment: LXR 0.9.9, but looks to be the same in 0.9.10 also. Nothing runs, basically. Sorry, lost the exact command but failure is: [Thu Jul 28 11:08:40 2011] [error] [client x.x.x.x] [Thu Jul 28 11:08:40 2011] fatal: main, line 224: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^\t\t\t\t\t# reminder: no initial space in the grammar, ...referrer info etc... This must need the following, a missing dot before a question-mark: diff -C 3 lib/LXR/Lang/Generic.pm.orig lib/LXR/Lang/Generic.pm *** lib/LXR/Lang/Generic.pm.orig Sun Mar 27 10:51:25 2011 --- lib/LXR/Lang/Generic.pm Fri Jul 29 11:27:50 2011 *************** *** 217,223 **** $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) --- 217,223 ---- $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (.?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) ..which runs fine. The same statement is in lib/LXR/Lang.pm WITH the missing dot in place. ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-07-29 23:01 Message: No, your suggested fix doesn't solve the bug. I don't exactly know what it does, but sure, it messes up #include processing: the file name is reduced to the first delimiter (i.e. " or >) and the hyperlink is not generated. The cause is in Perl. Your version is probably 5.8.8 whereas the syntax is 5.10. See comments # 3 & 4 in topic "Help on non-regression test" of forum Help. It is covered in depth in the discussion. Basically, (?| requests that all captures in the alternatives keep the same numbers. Your proposed change says a first alternative (.?| optionnally captures a single character and is followed by a series of alternatives. Since the first always succeeds, the others are never tested. If you think that 5.8.8-flavoured Perl is still ubiquitous, I can issue rather quickly a 0.9.11 release to downgrade the syntax. The easiest way to go is to upgrade your Perl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-07-29 10:30:35
|
Bugs item #3382013, was opened at 2011-07-29 11:30 Message generated for change (Tracker Item Submitted) made by kevinwalls You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.9.9 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin Walls (kevinwalls) Assigned to: Nobody/Anonymous (nobody) Summary: Missing dot in Generic.pm Initial Comment: LXR 0.9.9, but looks to be the same in 0.9.10 also. Nothing runs, basically. Sorry, lost the exact command but failure is: [Thu Jul 28 11:08:40 2011] [error] [client x.x.x.x] [Thu Jul 28 11:08:40 2011] fatal: main, line 224: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^\t\t\t\t\t# reminder: no initial space in the grammar, ...referrer info etc... This must need the following, a missing dot before a question-mark: diff -C 3 lib/LXR/Lang/Generic.pm.orig lib/LXR/Lang/Generic.pm *** lib/LXR/Lang/Generic.pm.orig Sun Mar 27 10:51:25 2011 --- lib/LXR/Lang/Generic.pm Fri Jul 29 11:27:50 2011 *************** *** 217,223 **** $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) --- 217,223 ---- $source =~ s/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space ! (.?| (\")(.+?)(\") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) ..which runs fine. The same statement is in lib/LXR/Lang.pm WITH the missing dot in place. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3382013&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-06-25 13:31:16
|
Bugs item #3330950, was opened at 2011-06-25 15:31 Message generated for change (Tracker Item Submitted) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3330950&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Lang support Group: current cvs Status: Open Resolution: None Priority: 3 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Generic.pm does unnecessary initialisation Initial Comment: Initialisation of generic parser is don in sub read_config. Since it is called only once, it is a good place to proceed with various tests, such as tools version number. This is done with the Perl backtick construct, executing a shell command as an independent process. Some security rules may forbid such a parallel execution from a web server (e.g. on SourceForge). Thus, initialisation aborts and LXR can't display files. To circumvent the problem, initialisation should detect whether it is call from shell contect (i.e. from genxref) or from web context. Since there is no need of ctags in web context, this verification should not be attempted. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3330950&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-06-11 07:59:29
|
Bugs item #3314739, was opened at 2011-06-10 17:17 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3314739&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.9 >Status: Closed >Resolution: Fixed Priority: 2 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: sub dirdesc doesn't always return a value Initial Comment: sub dirdesc in Local.pm is used to synthesize a description of a directory to display it in the listing. If it does not find a README.* file, it returns no value (i.e. = undefined). Content of the description table cell is then empty and browsers may delete the cell. Since the cell is not rendered, CSS decoration is not applied. To keep the cell (i.e. to be able to render at least a border and a background), sub dirdesc should return a "neutral" value in the no README case like a non-braking space (HTML  ). ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-06-11 09:59 Message: Added: return " "; as last statement in dirdesc ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-06-11 09:59 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3314739&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-06-10 15:17:18
|
Bugs item #3314739, was opened at 2011-06-10 17:17 Message generated for change (Tracker Item Submitted) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3314739&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.9 Status: Open Resolution: None Priority: 2 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: sub dirdesc doesn't always return a value Initial Comment: sub dirdesc in Local.pm is used to synthesize a description of a directory to display it in the listing. If it does not find a README.* file, it returns no value (i.e. = undefined). Content of the description table cell is then empty and browsers may delete the cell. Since the cell is not rendered, CSS decoration is not applied. To keep the cell (i.e. to be able to render at least a border and a background), sub dirdesc should return a "neutral" value in the no README case like a non-braking space (HTML  ). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3314739&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-05-08 19:12:07
|
Bugs item #3293079, was opened at 2011-04-26 14:11 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3293079&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: current cvs >Status: Closed >Resolution: Fixed Priority: 4 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Bad links to README in Local.pm Initial Comment: dirdesc in Local.pm displays an abstract of README file taken from the current directory. Text is passed to sub markupstring where it is processed SEQUENTIALLY, first identifier, next files. When a file name can also be categorized as an identifier, processing is done twice, thus messing up the idref of the first path. Also, link to the file is internally done instead of using fileref, resulting in no version in the link and no separator before the filename (thus a faulty full path). Moreover, since sub descreadme can be called for README and README.text, both filenames should be taken into consideration using an argument instead of the hard-coded README. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-05-08 21:12 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3293079&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-05-08 16:50:06
|
Bugs item #3299072, was opened at 2011-05-08 18:44 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3299072&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.9 >Status: Closed >Resolution: Fixed Priority: 4 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Bad links to markers in Local.pm Initial Comment: When trying to print some file-specific description in directory listing, sub markupstring is called with bad argument $Path->{'virt'}. Variable $Path is nowhere defined (a forgotten change when Config.pm was revamped?) It should be $dir. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-05-08 18:50 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3299072&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-05-08 16:44:34
|
Bugs item #3299072, was opened at 2011-05-08 18:44 Message generated for change (Tracker Item Submitted) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3299072&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.9 Status: Open Resolution: None Priority: 4 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Bad links to markers in Local.pm Initial Comment: When trying to print some file-specific description in directory listing, sub markupstring is called with bad argument $Path->{'virt'}. Variable $Path is nowhere defined (a forgotten change when Config.pm was revamped?) It should be $dir. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3299072&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-05-07 13:42:13
|
Bugs item #3204089, was opened at 2011-03-09 13:07 Message generated for change (Settings changed) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3204089&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: current cvs Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Image files never displayed Initial Comment: LXR v0.9.8 Graphic file cannot be displayed because synthesized URL is a query for LXR to process a source file instead of a simple file path. Proposed patch for Common.pm: -316,321 110307 (replace lines 316 to 321 with:) &$outfun("<ul><table><tr><th valign=\"center\"><b>Image: </b></th></tr>\n"); &$outfun("<tr><td>"); &$outfun("<img src=\"$config->{virtroot}" . $pathname . "\" border=\"0\"" . " alt=\"$pathname cannot be displayed by this browser\">\n"); &$outfun("</td></tr></table></ul>"); --------------- end of patch ----------------- ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-05-07 15:42 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-04-30 13:30 Message: The proposed patch does not solve the problem: LXR's DocumentRoot points to the directory where the scripts are stored, NOT to the source tree. Consequently, <img src=...> cannot serve the graphic file. For the plain files case, one can create a symbolic link to the source tree in the LXR directory and access the file the file through this link. The by-pass link is configured in lxr.conf. For the SCM cases, further thought is needed. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-12 11:11 Message: Solved simultaneously with 3204085 ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-12 11:11 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3204089&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-04-30 11:30:18
|
Bugs item #3204089, was opened at 2011-03-09 13:07 Message generated for change (Comment added) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3204089&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: current cvs Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Image files never displayed Initial Comment: LXR v0.9.8 Graphic file cannot be displayed because synthesized URL is a query for LXR to process a source file instead of a simple file path. Proposed patch for Common.pm: -316,321 110307 (replace lines 316 to 321 with:) &$outfun("<ul><table><tr><th valign=\"center\"><b>Image: </b></th></tr>\n"); &$outfun("<tr><td>"); &$outfun("<img src=\"$config->{virtroot}" . $pathname . "\" border=\"0\"" . " alt=\"$pathname cannot be displayed by this browser\">\n"); &$outfun("</td></tr></table></ul>"); --------------- end of patch ----------------- ---------------------------------------------------------------------- >Comment By: Andre-Littoz (ajlittoz) Date: 2011-04-30 13:30 Message: The proposed patch does not solve the problem: LXR's DocumentRoot points to the directory where the scripts are stored, NOT to the source tree. Consequently, <img src=...> cannot serve the graphic file. For the plain files case, one can create a symbolic link to the source tree in the LXR directory and access the file the file through this link. The by-pass link is configured in lxr.conf. For the SCM cases, further thought is needed. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-12 11:11 Message: Solved simultaneously with 3204085 ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-12 11:11 Message: This has now been fixed in CVS. If you can install the new version and check that it solves your problem, then it would be very useful. Thanks for reporting this defect and helping to make LXR better. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3204089&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2011-04-26 12:11:56
|
Bugs item #3293079, was opened at 2011-04-26 14:11 Message generated for change (Tracker Item Submitted) made by ajlittoz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3293079&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: current cvs Status: Open Resolution: None Priority: 4 Private: No Submitted By: Andre-Littoz (ajlittoz) Assigned to: Andre-Littoz (ajlittoz) Summary: Bad links to README in Local.pm Initial Comment: dirdesc in Local.pm displays an abstract of README file taken from the current directory. Text is passed to sub markupstring where it is processed SEQUENTIALLY, first identifier, next files. When a file name can also be categorized as an identifier, processing is done twice, thus messing up the idref of the first path. Also, link to the file is internally done instead of using fileref, resulting in no version in the link and no separator before the filename (thus a faulty full path). Moreover, since sub descreadme can be called for README and README.text, both filenames should be taken into consideration using an argument instead of the hard-coded README. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=3293079&group_id=27350 |
6 messages has been excluded from this view by a project administrator.
