Re: [fossil-users] New search features
On 2/2/15, Michai Ramakers m.ramak...@gmail.com wrote: IMHO it's safe to use Fossil trunk tip for daily work like many people here do. I'm usually running something close to trunk tip if not that very check-in as Fossil self-hosting repo and also on the SQLite site. You can always see which version of fossil is running on those sites by looking at the footer at the bottom of every page. Generally speaking, you should be safe running whatever the Fossil website itself is running. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Old problem not entirely gone?
On Mon, Feb 02, 2015 at 03:23:46PM -0700, Warren Young wrote: On Feb 1, 2015, at 7:08 AM, Jan Danielsson jan.m.daniels...@gmail.com wrote: The annoying thing is that when it fails, it wipes away whatever progress it has made. Yes, well, that’s the nature of transactional DB updates: all or nothing. How difficult would it be to allow fossil to pick up where it left off in such a case? Are you seriously asking for Fossil to allow a local clone to be in an inconsistent state after an error? Why does it have to be an inconsistent state? At the very least, it could ask for isatty(stdout) whether it should just retry. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Abort commit on empty message
On 2/2/15, Paolo Bolzoni paolo.bolzoni.br...@gmail.com wrote: Dear list, Something I actually like of git is that to abort a commit you just have to leave the editor without saving. It somewhat works with fossil too, but you have to confirm you want to abort the commit. So, I was wondering, it is possible to abort the commit on empty commit message? I have my VISUAL environment variable set which pops up a GUI text editor for the commit message. So I just press ^C in the original shell window to abort the commit. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Hello, On 2 February 2015 at 19:46, jungle Boogie jungleboog...@gmail.com wrote: On 2 February 2015 at 10:32, mario ma...@include-once.org wrote: P.S. Could we get like `dev-1.30.1` tags in between major releases? This is one of those significant new features that might warrant it. I agree with this! Especially since 1.30 was already increased: https://www.fossil-scm.org/index.html/info/09fe92ad728cf5f45bb4a9e1169cfb16a6363510 just out of interest (I didn't really follow this thread): do you (and/or original poster) already compile your own binaries? For Linux and *BSD it's really trivial; the build process is easy and the build is very clean (see http://fossil-scm.org/index.html/doc/tip/www/build.wiki for details). I have almost no experience on Windows systems, although for WinXP I used Visual Studio (IIRC) to build Fossil every now and then after a major fix, which is also quite painless. I didn't follow the evolution of Windows building, so perhaps now only Cygwin or Mingw are supported - no idea here; I just didn't have a need to recompile on Windows recently. IMHO it's safe to use Fossil trunk tip for daily work like many people here do. I myself have never lost a file because of Fossil (and don't know of anyone who did). Using an official Fossil release for 'safety' instead of trunk tip just doesn't cross my mind. In fact I don't think there's much hype here about official releases - I'm sure many people feel the same. (Ignore all of the above if I misunderstood your comment :-) Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
I never thought I could be so excited about a new Fossil feature. These are amazing changes, and will only be getting better. Thank you so much! -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Sunday, February 01, 2015 8:48 PM To: fossil-users Subject: [fossil-users] New search features The tip of trunk now supports full-text search on Check-in comments, Documentation, Tickets, and Wiki. The https://www.fossil-scm.org/ website is itself running this code, so you can see examples of the search features there: https://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.html https://www.fossil-scm.org/fossil/ticket https://www.fossil-scm.org/fossil/wiki To experiment with this in your own repositories, you have to enable searching in the new /srchsetup page (reachable by clicking on Search under the Admin menu). This code is still under active development. Your suggestions and comments are welcomed. CSS and presentation are areas where community input is especially encouraged. Note that all searching is currently a full text scan. The code does not yet generate a full-text index. Hence, the current implementation will not scale, though it seems to do well enough on a moderately sized repository such as Fossil itself, or SQLite, or even Tcl. Future enhancements will likely add optional full-text index support. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Hi Michai, On 2 February 2015 at 11:34, Michai Ramakers m.ramak...@gmail.com wrote: just out of interest (I didn't really follow this thread): do you (and/or original poster) already compile your own binaries? For Linux and *BSD it's really trivial; the build process is easy and the build is very clean (see http://fossil-scm.org/index.html/doc/tip/www/build.wiki for details). I follow trunk and update very, very frequently. No sense living in the past and missing all the updates! Since 1.30 was released, there have been a few dozen updates to trunk: https://www.fossil-scm.org/index.html/timeline?ym=2015-01n=224y=a 12 in the last two days!: https://www.fossil-scm.org/index.html/timeline?ym=2015-02n=16y=a -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Old problem not entirely gone?
On Feb 1, 2015, at 7:08 AM, Jan Danielsson jan.m.daniels...@gmail.com wrote: The annoying thing is that when it fails, it wipes away whatever progress it has made. Yes, well, that’s the nature of transactional DB updates: all or nothing. How difficult would it be to allow fossil to pick up where it left off in such a case? Are you seriously asking for Fossil to allow a local clone to be in an inconsistent state after an error? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil watch-face
Haven't worn a watch in 15 years because the extra weight annoys my arm while typing, so i am a bit out of touch on such topics :/. But yes, i later read that it is a Pebble (which means nothing to me). (sent from a mobile device - please excuse brevity, typos, and top-posting) - stephan beal http://wanderinghorse.net On Feb 2, 2015 11:50 PM, David Given d...@cowlark.com wrote: On 02/02/15 15:18, Stephan Beal wrote: [...] Not sure what kind of watch - seems to be one of those new-fangled e-watches. Judging by the buttons, it's a Pebble: https://getpebble.com/ It's actually an *old* fashioned e-watch --- 128kB RAM, 7 day battery life. My LG G is lucky to get 18 hours... -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─ http://www.cowlark.com ─ │ There does not now, nor will there ever, exist a programming │ language in which it is the least bit hard to write bad programs. --- │ Flon's Axiom ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Modifying the Ticket types to add your To_Do is very easy. Go to the Admin page and click Tickets. Modify the Common page. That's it. And if you would prefer To Do instead of To_Do, just enclose your phrase in double-quotes. Marty -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Johan Kuuse Sent: Monday, February 02, 2015 3:39 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] New search features snip b. Suggestion: What about adding a 'To_Do' type to the Ticket types? --- Code_Defect Build_Problem Documentation Feature_Request Incident To_Do --- Before using fossil, I basically had a text file with two sections, BUGS and TODO. When something was fixed, I added the word FIXED to the end of that line. Quite primitive, but it worked, for a small amount of bugs and todos. During time, though, this primitive system became not very maintainable. That was one of the reasons why I started to use fossil. My BUGS may now be opened, updated, and closed with a fine granularity, but I am missing managing my TODO list in the way. And, to be honest, it seems that http://www.fossil-scm.org/fossil/wiki?name=To+Do+List is missing it too. :-) Best Regards, Johan Kuuse ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Old problem not entirely gone?
On Feb 2, 2015, at 3:28 PM, Joerg Sonnenberger jo...@britannica.bec.de wrote: On Mon, Feb 02, 2015 at 03:23:46PM -0700, Warren Young wrote: Are you seriously asking for Fossil to allow a local clone to be in an inconsistent state after an error? Why does it have to be an inconsistent state? At the very least, it could ask for isatty(stdout) whether it should just retry. SQLite already has retry behavior in its locking. I presume Fossil hasn’t disabled that. After sending that prior message, I did think of a way to allow retries without inconsistency, but it would surely slow Fossil down: there could be a mode that turns cloning into a replay of the master repo’s timeline. That is, every change made to the master gets applied to the slave, in the order it was made. This means local files get updated multiple times, even if later changes wipe out prior ones. The advantage is that after each changeset is applied, the tree is again in a consistent state. That might not help the NetBSD repo, though, depending on how it was constructed. If it’s a history-preserving conversion from CVS or similar, this would possibly work. If on the other hand there was a point where a huge existing tree was imported into an SCM (Fossil or a predecessor) as-is, you have a good chance that the timeout will happen during processing of that initial huge commit. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] configure reset skin resets too much
Fwiw: ambivalent (sent from a mobile device - please excuse brevity, typos, and top-posting) - stephan beal http://wanderinghorse.net On Feb 3, 2015 12:16 AM, Richard Hipp d...@sqlite.org wrote: On 2/2/15, David Given d...@cowlark.com wrote: On 28/01/15 23:33, David Given wrote: It seems that doing 'fossil config reset skin' *also* resets the index path to the default. Does anyone have an opinion on this? I'm not going to do a merge without a sign-off... I don't have a strong feeling about it either way. I won't object. But do seek out further buy-in. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Old problem not entirely gone?
Thus said Jan Danielsson on Sun, 01 Feb 2015 15:08:07 +0100: In that thread the commit http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640 was brought up as a potential fix. I updated to get the fix and then tried running a clone, and I could indeed get the entire repository. This fix is server side, and the NetBSD repository is running version: http://www.fossil-scm.org/index.html/info/3d49f04587 And as far as I can tell, did not have the fix in for this until http://www.fossil-scm.org/index.html/info/ebac09bcf7 Which means perhaps the NetBSD repositories need a newer Fossil? Andy -- TAI64 timestamp: 400054d01abc ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
SEARCH FEATURE REQUEST: After performing a search and clicking on a link of interest, it would be nice if the returned page has the search term highlighted throughout the page. I've seen this in other search functions and have found it handy. Depending on the page that contains the search term, finding the search term can be tedious. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Sunday, February 01, 2015 8:48 PM To: fossil-users Subject: [fossil-users] New search features The tip of trunk now supports full-text search on Check-in comments, Documentation, Tickets, and Wiki. The https://www.fossil-scm.org/ website is itself running this code, so you can see examples of the search features there: https://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.html https://www.fossil-scm.org/fossil/ticket https://www.fossil-scm.org/fossil/wiki To experiment with this in your own repositories, you have to enable searching in the new /srchsetup page (reachable by clicking on Search under the Admin menu). This code is still under active development. Your suggestions and comments are welcomed. CSS and presentation are areas where community input is especially encouraged. Note that all searching is currently a full text scan. The code does not yet generate a full-text index. Hence, the current implementation will not scale, though it seems to do well enough on a moderately sized repository such as Fossil itself, or SQLite, or even Tcl. Future enhancements will likely add optional full-text index support. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] configure reset skin resets too much
On 28/01/15 23:33, David Given wrote: It seems that doing 'fossil config reset skin' *also* resets the index path to the default. Does anyone have an opinion on this? I'm not going to do a merge without a sign-off... -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─ http://www.cowlark.com ─ │ There does not now, nor will there ever, exist a programming │ language in which it is the least bit hard to write bad programs. --- │ Flon's Axiom signature.asc Description: OpenPGP digital signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] configure reset skin resets too much
On 2/2/15, David Given d...@cowlark.com wrote: On 28/01/15 23:33, David Given wrote: It seems that doing 'fossil config reset skin' *also* resets the index path to the default. Does anyone have an opinion on this? I'm not going to do a merge without a sign-off... I don't have a strong feeling about it either way. I won't object. But do seek out further buy-in. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Old problem not entirely gone?
On Mon, Feb 02, 2015 at 03:35:13PM -0700, Warren Young wrote: On Feb 2, 2015, at 3:28 PM, Joerg Sonnenberger jo...@britannica.bec.de wrote: On Mon, Feb 02, 2015 at 03:23:46PM -0700, Warren Young wrote: Are you seriously asking for Fossil to allow a local clone to be in an inconsistent state after an error? Why does it have to be an inconsistent state? At the very least, it could ask for isatty(stdout) whether it should just retry. SQLite already has retry behavior in its locking. I presume Fossil hasn’t disabled that. Retry on the *client* side, which is completely unrelated to sqlite. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Dear Richard, From: Richard Hipp d...@sqlite.org Sent: Mon, 2 Feb 2015 00:36:25 -0500 To: Fossil SCM user's discussion Subject: Re: [fossil-users] New search features On 2/2/15, jungle Boogie jungleboog...@gmail.com wrote: Hi Dr. Hipp, I go to http://www.fossil-scm.org/index.html/doc/trunk/www/permutedindex.html type in checklist and get this as results: http://www.fossil-scm.org/index.html/docsrch?s=checklist Then when I click on any of the 4 links, I see: Please enable javascript or log in to see this content Might be fixed now. Please try again. Yes, now I can go to above links and click on results without issue without having to be logged in. -- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil watch-face
John Stoume just posted a picture of his watch-face with the Fossil logo: https://plus.google.com/117522340661301291797/posts/6iQhx4uVgyR Not sure what kind of watch - seems to be one of those new-fangled e-watches. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil watch-face
On Mon, Feb 2, 2015 at 3:18 PM, Stephan Beal sgb...@googlemail.com wrote: John Stoume just posted a picture of his watch-face with the Fossil logo: https://plus.google.com/117522340661301291797/posts/6iQhx4uVgyR Not sure what kind of watch - seems to be one of those new-fangled e-watches. This earlier post: https://plus.google.com/117522340661301291797/posts/8z1t7mboEAx contains more technical info, including a link to the tool used to create it: http://www.watchface-generator.de/ -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
The tip of trunk now supports full-text search on Check-in comments, Documentation, Tickets, and Wiki. The https://www.fossil-scm.org/ website is itself running this code, so you can see examples of the search features there: https://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.html https://www.fossil-scm.org/fossil/ticket https://www.fossil-scm.org/fossil/wiki To experiment with this in your own repositories, you have to enable searching in the new /srchsetup page (reachable by clicking on Search under the Admin menu). This code is still under active development. Your suggestions and comments are welcomed. CSS and presentation are areas where community input is especially encouraged. Thanks a lot for the new 'search' feature! That implies removing one more thing from the To Do List... ;-) http://www.fossil-scm.org/fossil/wiki?name=To+Do+List Talking about the 'To Do List' (and the search feature too, actually): a. Question: How to search for strings containing spaces, such as the 'To Do List' Wiki document? Double quotes? To Do List Single quotes? 'To Do List' Plus sign? To+Do+List b. Suggestion: What about adding a 'To_Do' type to the Ticket types? --- Code_Defect Build_Problem Documentation Feature_Request Incident To_Do --- Before using fossil, I basically had a text file with two sections, BUGS and TODO. When something was fixed, I added the word FIXED to the end of that line. Quite primitive, but it worked, for a small amount of bugs and todos. During time, though, this primitive system became not very maintainable. That was one of the reasons why I started to use fossil. My BUGS may now be opened, updated, and closed with a fine granularity, but I am missing managing my TODO list in the way. And, to be honest, it seems that http://www.fossil-scm.org/fossil/wiki?name=To+Do+List is missing it too. :-) Best Regards, Johan Kuuse ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
On 1 February 2015 at 20:48, Richard Hipp d...@sqlite.org wrote: The tip of trunk now supports full-text search on Check-in comments, Documentation, Tickets, and Wiki. The https://www.fossil-scm.org/ website is itself running this code, so you can see examples of the search features there: https://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.html https://www.fossil-scm.org/fossil/ticket https://www.fossil-scm.org/fossil/wiki I doubt this is a regression but just an observation. Ticket search page: http://www.fossil-scm.org/index.html/ticket Ticket UUID: 8a2523b559d0179070b1fef9fa4ccef6d952f3a2 Search results: No matches for: 8a2523b559d0179070b1fef9fa4ccef6d952f3a2 The abbreviate ticket UUID number is 8a2523b559 You search this and there's no results as well. Now of course searching the title SHJS Syntax works but some commits are because of a ticket: http://www.fossil-scm.org/index.html/info/f201cb61a099055a45658b669867e4436962c133 The clickable link to the ticket can be seen on the branch timeline so I may just be too picky: http://www.fossil-scm.org/index.html/timeline?n=100r=fsl_setting_proxy By the way, this branch is super useful when you don't know where the particular code is: http://www.fossil-scm.org/index.html/timeline?n=100r=file-filter just type in the name you think it is and your results will be filtered. I recommend a merge (for whatever my opinion matters)! Best, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] configure reset skin resets too much
Andy Bradford wrote: I don't think it makes much sense for the index-page to be reset with ``fossil config reset skin'' either. Is the index-page considered part of the skin? Likewise, it also seems odd that ``fossil config reset project'' doesn't reset the index-page. Agreed. I'm also of the opinion that this is a good change and I have no objections to it. -- Joe Mistachkin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
On 2/3/15, jungle Boogie jungleboog...@gmail.com wrote: Something recently has changed that doesn't allow the clicked result to be viewed. http://fossil-scm.org/index.html/tktsrch?s=windows The main Fossil repo (and the main SQLite repo) are now running on a full-text index, rather than do a full scan of all documents for each search. This is faster, but considerably trickier to implement. I expect it to be a bountiful source of errors over the next few days. The problem with hyperlinks is now fixed, I think. Please try again. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Dr. Hipp, On 2 February 2015 at 22:11, Richard Hipp d...@sqlite.org wrote: On 2/3/15, jungle Boogie jungleboog...@gmail.com wrote: Something recently has changed that doesn't allow the clicked result to be viewed. http://fossil-scm.org/index.html/tktsrch?s=windows The main Fossil repo (and the main SQLite repo) are now running on a full-text index, rather than do a full scan of all documents for each search. This is faster, but considerably trickier to implement. I expect it to be a bountiful source of errors over the next few days. Not a problem with me, I'll report them as I encounter them! The problem with hyperlinks is now fixed, I think. Please try again. Yes, that corrected it and results are now clickable. -- D. Richard Hipp d...@sqlite.org Thanks! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Awesome! I specifically wanted wiki search! Jonathan Otsuka On Feb 1, 2015, at 10:48 PM, Richard Hipp d...@sqlite.org wrote: The tip of trunk now supports full-text search on Check-in comments, Documentation, Tickets, and Wiki. The https://www.fossil-scm.org/ website is itself running this code, so you can see examples of the search features there: https://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.html https://www.fossil-scm.org/fossil/ticket https://www.fossil-scm.org/fossil/wiki To experiment with this in your own repositories, you have to enable searching in the new /srchsetup page (reachable by clicking on Search under the Admin menu). This code is still under active development. Your suggestions and comments are welcomed. CSS and presentation are areas where community input is especially encouraged. Note that all searching is currently a full text scan. The code does not yet generate a full-text index. Hence, the current implementation will not scale, though it seems to do well enough on a moderately sized repository such as Fossil itself, or SQLite, or even Tcl. Future enhancements will likely add optional full-text index support. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Sun, 1 Feb 2015 23:48:28 -0500 Richard Hipp d...@sqlite.org: To experiment with this in your own repositories, you have to enable searching in the new /srchsetup page (reachable by clicking on Search under the Admin menu). That's extremely awesome. In particular the configuration settings are super handy again. The binary search is also surprisingly quick; probably sufficient already for almost everyone. (Just got rid of my custom search stuff.) This code is still under active development. Your suggestions and comments are welcomed. CSS and presentation are areas where community input is especially encouraged. I'd personally prefer the match snippets to use mark../mark instead of just b tags. It's less pretty with the background highlighting per default, but much easier to match and style later. P.S. Could we get like `dev-1.30.1` tags in between major releases? This is one of those significant new features that might warrant it. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
On 2 February 2015 at 10:32, mario ma...@include-once.org wrote: P.S. Could we get like `dev-1.30.1` tags in between major releases? This is one of those significant new features that might warrant it. I agree with this! Especially since 1.30 was already increased: https://www.fossil-scm.org/index.html/info/09fe92ad728cf5f45bb4a9e1169cfb16a6363510 -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Abort commit on empty message
Dear list, Something I actually like of git is that to abort a commit you just have to leave the editor without saving. It somewhat works with fossil too, but you have to confirm you want to abort the commit. So, I was wondering, it is possible to abort the commit on empty commit message? yours faithfully, Paolo ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] configure reset skin resets too much
Thus said David Given on Mon, 02 Feb 2015 23:51:33 +0100: It seems that doing 'fossil config reset skin' *also* resets the index path to the default. Does anyone have an opinion on this? I'm not going to do a merge without a sign-off... I don't think it makes much sense for the index-page to be reset with ``fossil config reset skin'' either. Is the index-page considered part of the skin? Likewise, it also seems odd that ``fossil config reset project'' doesn't reset the index-page. Andy -- TAI64 timestamp: 400054d04fac ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New search features
Hi Richard, On 1 February 2015 at 20:48, Richard Hipp d...@sqlite.org wrote: he tip of trunk now supports full-text search on Check-in comments, Documentation, Tickets, and Wiki. The https://www.fossil-scm.org/ website is itself running this code, so you can see examples of the search features there: https://www.fossil-scm.org/fossil/doc/trunk/www/permutedindex.html https://www.fossil-scm.org/fossil/ticket https://www.fossil-scm.org/fossil/wiki Something recently has changed that doesn't allow the clicked result to be viewed. http://fossil-scm.org/index.html/tktsrch?s=windows Notice 100+ results now when I click on one: Say the sixth: Ticket [1501b8bf3b229e78] on 2009-02-19 00:11:47 Link: http://fossil-scm.org/tktview/1501b8bf3b229e78b4fc Document Not Found The document /tktview/1501b8bf3b229e78b4fc is not available on this server Looks like adding in /index.html/tktview/UUID works Also appears to be an issue with docs and wiki. I'm not even going to try and guess what recent commit has regression but I bet Dr. Hipp will find it in about 2 minutes. Best, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
