I still have a copy of swish-e 2.4.7 and I can send it to you but I rather recommend using Glimpse for source tree indexing.
Swish-e will hit on the file without any detail. Glimpse is more accurate as it returns file + line number.
From personal experience, Swish-e is a tool for indexing HTML sites where the relevant information is the page containing the queried text and your browser will display the page. Glimpse returns the line number and LXR can immediately scroll to the line of interest. This seems to me a more adequate choice when you are reading source code.
In addition, Swish-e duplicates the source tree to use this copy as a look up tool while Glimpse indexes need only 5-10% tree size.
A complete rewrite of Swish-e has been done as SWISH++ (available on SourceForge) but I have not tested it and don't know how it would integrate with LXR. I just skimmed the features page and fear it is even more HTML-oriented than the original Swish-e. Anyway, IMHO, using Swish-e in LXR is probably hijacking Swish-e.
You may also have difficulties to find Glimpse, though it is present on many download sites (I think UArizona stopped maintaining the application) but I also have a copy of 4.18.6 version.
Tell me your intention and I send you a tarball.
Last edit: Andre-Littoz 2021-05-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep. LXRSwishe is a backup plan. We lost our server and I have to rebuild
it. I'm doing a trial on openGROK at the moment. but if that doesn't pan
out, we may return to LXR/Swish-e.
I still have a copy of swish-e 2.4.7 and I can send it to you but I rather
recommend using Glimpse for source tree indexing.
Swish-e will hit on the file without any detail. Swish-e is more accurate
as it returns file + line number.
From personal experience, Swish-e is a tool for indexing HTML sites where
the relevant information is the page containing the queried text and your
browser will display the page. Glimpse returns the line number and LXR can
immediately scroll to the line of interest. This seems to me a more
adequate choice when you are reading source code.
In addition, Swish-e duplicates the source tree to use this copy as a look
up tool while Glimpse indexes need only 5-10% tree size.
A complete rewrite of Swish-e has been done as SWISH++ (available on
SourceForge) but I have not tested it and don't know how it would integrate
with LXR. I just skimmed the features page and fear it is even more
HTML-oriented than the original Swish-e. Anyway, IMHO, using Swish-e in LXR
is probably hijacking Swish-e.
You may also have difficulties to find Glimpse, though it is present on
many download sites (I think UArizona stopped maintaining the application)
but I also have a copy of 4.18.6 version.
A lot of effort has been invested in LXR configuration process. The present release has a configuration script configure-lxr.pl which dramatically simplifies the task. For a simple tree, it is a matter of less than one minute, compared to the former tedious manual configuration of lxr.conf. Only for that, you should upgrade.
There are also lots of new features and an impressive performance boost in generating the cross-references.
Not the least, there is a comprehensive manual (albeit too verbose).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still have a copy of swish-e 2.4.7 and I can send it to you but I rather recommend using Glimpse for source tree indexing.
Swish-e will hit on the file without any detail. Glimpse is more accurate as it returns file + line number.
From personal experience, Swish-e is a tool for indexing HTML sites where the relevant information is the page containing the queried text and your browser will display the page. Glimpse returns the line number and LXR can immediately scroll to the line of interest. This seems to me a more adequate choice when you are reading source code.
In addition, Swish-e duplicates the source tree to use this copy as a look up tool while Glimpse indexes need only 5-10% tree size.
A complete rewrite of Swish-e has been done as SWISH++ (available on SourceForge) but I have not tested it and don't know how it would integrate with LXR. I just skimmed the features page and fear it is even more HTML-oriented than the original Swish-e. Anyway, IMHO, using Swish-e in LXR is probably hijacking Swish-e.
You may also have difficulties to find Glimpse, though it is present on many download sites (I think UArizona stopped maintaining the application) but I also have a copy of 4.18.6 version.
Tell me your intention and I send you a tarball.
Last edit: Andre-Littoz 2021-05-06
Yep. LXRSwishe is a backup plan. We lost our server and I have to rebuild
it. I'm doing a trial on openGROK at the moment. but if that doesn't pan
out, we may return to LXR/Swish-e.
I very much appreciate your reply.
On Tue, May 4, 2021, 2:44 AM Andre-Littoz ajlittoz@users.sourceforge.net
wrote:
Out of curiosity, which LXR version was installed on your lost server?
0.9.5, I would expect to uptake latest.
On Thu, May 6, 2021, 4:49 AM Andre-Littoz ajlittoz@users.sourceforge.net
wrote:
A lot of effort has been invested in LXR configuration process. The present release has a configuration script configure-lxr.pl which dramatically simplifies the task. For a simple tree, it is a matter of less than one minute, compared to the former tedious manual configuration of lxr.conf. Only for that, you should upgrade.
There are also lots of new features and an impressive performance boost in generating the cross-references.
Not the least, there is a comprehensive manual (albeit too verbose).