[darcs-users] darcs annotate format obscures the code

Ralph Corderoy ralph at inputplus.co.uk
Mon Mar 21 10:41:34 UTC 2005

Hi Michael,

> > Thus we would give the entire messages at the bottom along with
> > unique identifiers of some sort, and we'd have a very compact and
> > readable representation of the actual code.
> If you mean literally one output stream/file where the code is at the
> front and the log is at the bottom...  Now in order to figure out why
> line 245 was changed I have to jump to another point in the file, read
> that, and jump back.  I can't see the code and the log message at the
> same time. :( 
> There has to be two separate streams of information so I can see the
> code and the reason simultaneously.

(He (I) did mean that.)  Then split the output, e.g. csplit(1), or run
it within an editor with two views on the buffer, or push for an option
to put the history into a separate file rather than tacked on the end.



More information about the darcs-users mailing list