Re: [fossil-users] Timeline pointers patch
Ah, no, not yet. Is this something I can fax or must it be mailed? On Mon, Mar 9, 2015 at 11:32 AM, Richard Hipp d...@sqlite.org wrote: On 3/9/15, Chad Clabaugh chadclaba...@gmail.com wrote: I see what you mean. Modified and tested in Firefox, Chrome, IE. Brilliant. Thanks. The arrows look *really good* on a 300DPI tablet now! Do I already have a Contributor's Agreement on file from you? (https://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html) -- 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] Timeline pointers patch
I see what you mean. Modified and tested in Firefox, Chrome, IE. On Fri, Mar 6, 2015 at 10:14 PM, Richard Hipp d...@sqlite.org wrote: On 3/6/15, Richard Hipp d...@sqlite.org wrote: On 3/6/15, Chad Clabaugh chadclaba...@gmail.com wrote: I would like to offer the attached patch to timeline.c that smooths the timeline arrows while also halving the number of elements required to create them. I tried this (using Firefox Nightly) but it doesn't look right. Legacy: http://www.fossil-scm.org/tmp/ss-legacy.gif New: http://www.fossil-scm.org/tmp/ss-legacy.gif Correct link to new: http://www.fossil-scm.org/tmp/ss-new.gif As you can see, the new code is asymmetric and the arrow tips do not reach the bottom of the boxes. -- D. Richard Hipp d...@sqlite.org -- 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 smoothTimelineArrows.patch Description: Binary data ___ 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] Timeline pointers patch
On 3/9/15, Chad Clabaugh chadclaba...@gmail.com wrote: Ah, no, not yet. Is this something I can fax or must it be mailed? For this, an emailed scan will be sufficient. -- 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] Timeline pointers patch
On 3/9/15, Chad Clabaugh chadclaba...@gmail.com wrote: I see what you mean. Modified and tested in Firefox, Chrome, IE. Brilliant. Thanks. The arrows look *really good* on a 300DPI tablet now! Do I already have a Contributor's Agreement on file from you? (https://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html) -- 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] Justification for two-step mv and rm
Am 09.03.2015 um 10:09 schrieb Jan Nijtmans: Done now: http://www.fossil-scm.org/index.html/info/8cf976d24689ae9e This means that whatever happens with fossil rm|mv|delete, the fossil rename and fossil forget will continue to function as they do now. Hurray and thank you! Will `addremove` become `addforget`? (Sorry, couldn't resist nitpicking.) ___ 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] Working with Windows mapped network drives
This has nothing to do with mapped drives. You'll get not found with any drive root -- C:\, D:\... Fossil cuts off the trailing backslash with the result that stat() resp lstat() returns an error = not found. I'm not shure whether and if yes in which function(s) -- file_canonical_name(), file_isdir(), file_wd_isdir(), file_simplify_name()... -- a 'when-on-windows-and-path-length-is-2-and-starts-with-A..Z-and-ends-with-colon-the-add-slash' correction should be implemented. Until your S:\-problem I didn't even think about putting a whole drive in one repository... -Tontyna Am 01.03.2015 um 10:57 schrieb Milo Rambaldi: Hi, I'm currently trying out fossil and ran into a problem using mapped network drives. In most tutorials I found on the net, the command used to add files to the repository is add . which doesn't work on a network drive: ---snip--- C:\net use s: \\sandbox\htdocs Der Befehl wurde erfolgreich ausgeführt. S:\fossil new d:\test.repo project-id: b0755e4c2a55d06275cc8158d4d10cbe386ff3a7 server-id: 0bedf33b9ddbdaa06d7157ef72c6d242f904979e admin-user: milo (initial password is **) S:\fossil open d:\test.repo project-name: unnamed repository: d:\test.repo local-root: S:/ config-db:C:/Users/milo/AppData/Local/_fossil project-code: b0755e4c2a55d06275cc8158d4d10cbe386ff3a7 checkins: 0 S:\fossil add . not found: S: S:\fossil add s:\ not found: S: S:\fossil add s:/ not found: S: ---snip--- Is there any way to do this? Thanks, m. ___ 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] Timeline graph display options
Thus said Richard Hipp on Mon, 09 Mar 2015 23:06:59 -0400: Which timeline graph do you prefer: (1) https://www.fossil-scm.org/fossil/timeline?y=cinomo=0 (2) https://www.fossil-scm.org/fossil/timeline?y=cinomo=1 (1) because the relationship to the node from which the arrow originates is more clear to me. (1) https://core.tcl.tk/tk/timeline?y=cinomo=0 There appears to be a minor glitch in this timeline (attached as image) with one of the arrows not quite aligned properly. (See, for example, https://www.fossil-scm.org/fossil/timeline?y=cirailpitch=11). I removed railpitch from the above URL and I think I prefer it without. The graph is slightly wider, but I still find the additional arrow lines to be helpful. Maybe this is just habit bias creeping in from having them in the timeline already, but I'm not sure. Perhaps if there were 15--20 rails, where they were taking up a disproportionate amount of space (2) might make a big enough difference. Andy TAI64 timestamp: 400054fe685e ___ 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] Timeline graph display options
On 3/9/15, Andy Bradford amb-fos...@bradfords.org wrote: Perhaps if there were 15--20 rails, where they were taking up a disproportionate amount of space (2) might make a big enough difference. Oh, it does. Try a graph with n=all and you'll see. When you start to get a lot of rails, and the graph gets all scrunched together, then (2) is clearly better. The question is should we go with (2) always, or use (1) for graphs that have more space and save (2) for scrunched up graphs. -- 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] Timeline graph display options
On Mon, Mar 9, 2015 at 11:06 PM, Richard Hipp d...@sqlite.org wrote: Which timeline graph do you prefer: (1) https://www.fossil-scm.org/fossil/timeline?y=cinomo=0 (2) https://www.fossil-scm.org/fossil/timeline?y=cinomo=1 I personally prefer 2. Initially 1 looks more aesthetically pleasing, but when shown the other examples, it simply looks too busy. Also, I think the EE part of me sees the examples in 2 and they remind me of circuit nodes, and therefore they are easily understood. That may not apply to everyone though. To summarize, I prefer 2. - joe ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Timeline graph display options
Which timeline graph do you prefer: (1) https://www.fossil-scm.org/fossil/timeline?y=cinomo=0 (2) https://www.fossil-scm.org/fossil/timeline?y=cinomo=1 The difference is in the merge lines. Other examples: (1) https://core.tcl.tk/tk/timeline?y=cinomo=0 (2) https://core.tcl.tk/tk/timeline?y=cinomo=1 (1) https://www.fossil-scm.org/fossil/timeline?y=cib=2015-02-26nomo=0 (2) https://www.fossil-scm.org/fossil/timeline?y=cib=2015-02-26nomo=1 The current default display is as in (1). When there are many parallel branches in a graph, Fossil reduces the spacing between the vertical lines of the graph (called rails in the code) and when the rails get really close together, Fossil automatically switches to style (2) because that is clearly easier to read when the graph is scrunched together. (See, for example, https://www.fossil-scm.org/fossil/timeline?y=cirailpitch=11). But after making that enhancements, I notice that style (2) seems less cluttered, and so now I'm wondering if it ought to be the default. FWIW: The nomo= and railpitch= query parameters are experimental and will be removed, probably before the next release. So do not become attached to them. -- 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] Fossil 1.31 directory name
On Sat, Mar 7, 2015 at 6:51 PM, Andy Goth andrew.m.g...@gmail.com wrote: Fossil 1.31 has been published to the SlackBuild website. http://slackbuilds.org/repository/14.1/development/fossil/ Very cool. I still didn't get around to making the Haiku packages yet, even though the build recipe has existed since the day 1.31 came out, I think. We don't have an automated builder yet, and well, I haven't gotten around to creating packages for our three main architectures yet. I'm hoping to get that done this weekend. - joe ___ 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] Commit without resolving the new files: a bug or a feature?
On Mon, Mar 9, 2015 at 9:29 AM, Henry Adi Sumarto henry.adisuma...@gmail.com wrote: (either by adding or by ignoring the file). Shouldn't fossil warn me about the extra files? Or is it intended to work that way? The behaviour you are seeing is as expected. Fossil requires that you tell it which files you want it to know about. It's very common to have non-controlled files in a tree - would you want Fossil to warn you every time a new .o files appears or a script creates a temp file? Fossil has an ignore feature so that the extras command can filter such files out, but it does not do anything magical with arbitrary files in your checkout dir - it requires you to tell it (via 'add') what files you care about. -- - 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
[fossil-users] Commit without resolving the new files: a bug or a feature?
Hi, When there is a file change in an existing repository and there is another new file that has not been added into the repository, and then I commit the change without adding the new file (let's say I forget to add!), I notice that fossil lets me commit without resolving what to do with the new file (either by adding or by ignoring the file). Shouldn't fossil warn me about the extra files? Or is it intended to work that way? Thanks. -- Yours truly, Henry ___ 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] Justification for two-step mv and rm
2015-03-06 16:58 GMT+01:00 Jan Danielsson jan.m.daniels...@gmail.com: On 06/03/15 15:10, Jan Nijtmans wrote: Any objections against adding fossil forget as alias to fossil rm If not, I'll be glad to add it, awaiting further discussion. No objection. I'm even going to go so far as to say I'll be cheering you on. Done now: http://www.fossil-scm.org/index.html/info/8cf976d24689ae9e This means that whatever happens with fossil rm|mv|delete, the fossil rename and fossil forget will continue to function as they do now. Regards, Jan Nijtmans ___ 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] need additional padding for the .filelist li
On 3/8/15, Svyatoslav Mishyn j...@openmailbox.org wrote: Hello, for example: padding: 1px 0; see: https://cloud.openmailbox.org/public.php?service=filest=27ee378f8bdc47ebcd06069d907916fc What is that hyperlink suppose to demonstrate? I do not understand why extra padding is needed. -- http://www.juef.tk/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] need additional padding for the .filelist li
(Mon, 09 Mar 06:15) Richard Hipp: On 3/8/15, Svyatoslav Mishyn j...@openmailbox.org wrote: Hello, for example: padding: 1px 0; see: https://cloud.openmailbox.org/public.php?service=filest=27ee378f8bdc47ebcd06069d907916fc What is that hyperlink suppose to demonstrate? I do not understand why extra padding is needed. 'g' (from src/graph.c) and 'i' (from src/import.c) are crossing -- http://www.juef.tk/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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 -- http://www.juef.tk/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
