Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Jan Nijtmans
2013/11/26 Andy Bradford amb-sendok-1388038260.iehncdlegomjloead...@bradfords.org: First, if I hide a check-in and rename the branch to mistake, when I view the mistake branch using /timeline?r=mistake those items do not show up; of course this is certainly working as it should, but

Re: [fossil-users] single-column file list output in web UI

2013-11-26 Thread Michai Ramakers
On 26 November 2013 07:55, Joel Bruick j...@joelface.com wrote: Michai Ramakers wrote: is there a simple way to display repo file contents in a single column, instead of 3, in the web UI? (or at least I see 3 columns here) Sorry for being way late to this, but you can get the

Re: [fossil-users] single-column file list output in web UI

2013-11-26 Thread Stephan Beal
On Tue, Nov 26, 2013 at 1:35 PM, Michai Ramakers m.ramak...@gmail.comwrote: That works absolutely fine, thx! Nonetheless, a one-column option is on my TODO list for over the Christmas holidays. i'd like to see something more like conventional ls output (with a few caveats/shortcomings due to

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Martin Gagnon
On Mon, Nov 25, 2013 at 11:11:00PM -0700, Andy Bradford wrote: Thus said Jan Nijtmans on Mon, 25 Nov 2013 17:08:07 +0100: Any objections to this change? At least it's not dangerous at all: It's just as easy to unhide items than to hide them, just by removing the hidden tag

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Andy Bradford
Thus said Jan Nijtmans on Tue, 26 Nov 2013 12:50:52 +0100: At this moment, only single nodes can be hidden, that's intended. I see no problems making it propagating, it would make it easier to hide big parts without anyone noticing. I'm not sure we want to encourage that. Tough choice.

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Matt Welland
Hiding clutter is hugely important in my opinion. If something is marked as irrelevant then hide it regardless of how the final timeline looks. However an obvious button to toggle show-all on the timeline would be equally important. I see the intent as enabling a view of the important and

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Andy Bradford
Thus said Matt Welland on Tue, 26 Nov 2013 12:01:30 -0700: Do you now have: - a - c - OR - a c - What about: - a = c - Where = is a new line style that indicates a hidden line of commits between a and c? Andy -- TAI64 timestamp: 40005294f9ae

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Ron Wilson
On Tue, Nov 26, 2013 at 2:42 PM, Andy Bradford amb-fos...@bradfords.orgwrote: Thus said Matt Welland on Tue, 26 Nov 2013 12:01:30 -0700: Do you now have: - a - c - OR - a c - What about: - a = c - Where = is a new line style that indicates a hidden line of commits

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Matt Welland
b is not a fork, nor is it abandoned. think of it as math. The delta a-c is equal to the sum of a-b and b-c. You can hide b and think in terms of a-c just fine. The only complication is if other branches derive from b. but that is up to the user to think carefully and mean what they say when they

Re: [fossil-users] Hide items from timeline [Was: clone --once and URL user as admin.]

2013-11-26 Thread Andy Bradford
Thus said Ron Wilson on Tue, 26 Nov 2013 15:17:31 -0500: At the same time, I find it strange to hide commits whose content is still being used (unless c is just a reversion of those changes, but then I'd just commit against a, leaving b as an abandoned fork/branch) I too had the