Same here. I like the colorful diff.
But I would like to know (sorry if I missed) what's th eproblem with color sbs
and what are we getting with retro sbs?
- Altu
- Original Message -
From: Weber, Martin S
Sent: 02/03/12 11:03 PM
To: Fossil SCM user's discussion
Subject: Re:
On Fri, 3 Feb 2012 09:57:47 -0700 Matt Welland wrote:
If I do:
fossil rm some/file.txt
rm some/file.txt
fossil commit
People often prefer to commit when their work has reached some level
of completion or readiness and partially done commits can cause
unnecessary breakage
On Sat, Feb 4, 2012 at 5:08 AM, altufa...@mail.com wrote:
Same here. I like the colorful diff.
But I would like to know (sorry if I missed) what's the problem with color
sbs and what are we getting with retro sbs?
Here is an example, two different websites showing the same Fossil project
On 02/04/12 11:08, altufa...@mail.com wrote:
Same here. I like the colorful diff.
But I would like to know (sorry if I missed) what's th eproblem with color
sbs and what are we getting with retro sbs?
The reason is that we have two different places in the code which do
the same thing
On Mon, Jan 30, 2012 at 12:18:28PM +0100, Dmitry Chestnykh wrote:
On Mon, 30 Jan 2012 09:11:03 +0100 Lluís Batlle i Rossell wrote:
On Mon, Jan 30, 2012 at 04:27:07AM +0100, Dmitry Chestnykh wrote:
Yeah, static linking is not actually that static nowadays. When
linking, GCC warns about
For me, much better with the colors. Maybe taking out the violet of the
hidden lines.
It helps a lot to focus the attention to the correct place.
RR
El 04/02/2012 13:24, Richard Hipp d...@sqlite.org escribió:
On Sat, Feb 4, 2012 at 5:08 AM, altufa...@mail.com wrote:
Same here. I like the
The problem here is the violet for skipped lines that is more outstanding than
the diff itself. I'm sure the colorful version can be tweaked to have the best
of both world.
In my case, 80% of the case, I prefer unified (with color via JS even more).
Especially when there's not a lot of changes
Seconded. The hidden lines receive more emphasis than the change. Do a
tkdiff on the same change and it is immediately obvious what the change is.
I checked meld, tkdiff and xxdiff and in all of them the actual character
that was removed is also highlighted making it immediately obvious what
Fully agree, the colored one suffers from being cluttered. If the
retro one grayed
the changed line to slightly highlight it, it would help a lot.
Shameless plug: Diff tool with built in Fossil support:
http://eskil.tcl.tk/index.html/doc/trunk/htdocs/fossil.wiki
/Peter
On Sat, Feb 4, 2012 at
On Fri, Feb 3, 2012 at 8:26 PM, frantisek holop min...@obiit.org wrote:
hi there,
reading through the documentation i thought some sentences
would be easier to read with some minor changes, and i also
removed end of line whitespace.
the other item from the subject concerns the future
On Sat, Feb 4, 2012 at 07:24, Richard Hipp d...@sqlite.org wrote:
Here is an example, two different websites showing the same Fossil project
(TCL), one with the traditional colorful diff and the other with the new
retro diff:
(1) http://core.tcl.tk/tcl/ci/4ebc3a8e1e?sbs=1
(2)
On Sat, Feb 4, 2012 at 10:24 AM, Leo Razoumov slonik...@gmail.com wrote:
On Sat, Feb 4, 2012 at 07:24, Richard Hipp d...@sqlite.org wrote:
Here is an example, two different websites showing the same Fossil
project
(TCL), one with the traditional colorful diff and the other with the new
On Sat, Feb 4, 2012 at 10:36, Richard Hipp d...@sqlite.org wrote:
Here is an example, two different websites showing the same Fossil
project
(TCL), one with the traditional colorful diff and the other with the new
retro diff:
(1) http://core.tcl.tk/tcl/ci/4ebc3a8e1e?sbs=1
(2)
hi there,
i tried to use gvimdiff as the gdiff-command
but i always kept getting empty file where
the temporary ~0 file should have been. then
i realized that gvim returns to the shell
right away, and fossil probably takes that
as a signal to removes the temp file.
i solved this with gvim's -f
Most of gui Editor work in frontground already.. GVim have this option because
it spawn it in background by default and have a kind of client/server model
(you can edit a file inside a specific instance that is already running).
fossil can't do nothing about that.. (I mean something
On Fri, Feb 3, 2012 at 10:54 PM, Jay Weisskopf jayschwa+fos...@gmail.comwrote:
I created a patch (available below) for the makedeb.sh script that
Hi, Jay!
Thanks for that - i haven't touched that script for some time, since i
don't use Nexenta any more. i'll get your fixes applied sometime
Nice.. Same kind of coloring on unified diff would be nice too..
--
Martin G.
Le 2012-02-04 à 14:14, Richard Hipp d...@sqlite.org a écrit :
A colorized version of the retro-sbsdiff branch is now on the main website.
An example:
http://www.sqlite.org/src/info/21695c3476
On Sat, Feb 4, 2012 at 2:26 PM, Martin Gagnon eme...@gmail.com wrote:
Nice.. Same kind of coloring on unified diff would be nice too..
Implemented before you even asked. See,
http://www.fossil-scm.org/fossil/ci/b57b035654?sbs=0 for example. Chrome
users, the CSS has changed again so be sure
+2
Liked both the diffs.
Are colors configurable from skin?
I used following CSS for bsdiff (I find bluish color better than yellow for
changed lines):
table.sbsdiff tr td.added {
background-color: rgb(220, 244, 220);
}
table.sbsdiff tr td.removed {
background-color: rgb(244, 220, 220);
}
19 matches
Mail list logo
