Michael Hanke

Tangentially related comment: ``` datalad configuration set some.item= ``` works, and sets an empty string as value.

From the perspective of `diff` it would be easy to add such a feature. It is practically just an alternative "result_renderer", as the results already contain all info. Here is...

Same as #2812

Here is a quick update on what information is available to a renderer implementation with the ability to display diffs with the code in https://github.com/datalad/datalad-revolution/pull/58/commits/cd733da9fe742f4424038ab07a27dd9d7372de71 (which is part of https://github.com/datalad/datalad-revolution/pull/58)...

Looked into multidiff (@yarikoptic mentioned above). Neat. ```python >>> from multidiff import MultidiffModel, Render >>> m = MultidiffModel(['old stuff', 'old stuff with additions']) >>> m.diff_last_pair() >>> Render('utf8', color='html').render(m, m.diffs[0]) "old...

I thought about this again. I think the approach to implement a dedicated result renderer to show "patches" is a nice and also compact way to finally fix this issue....

> in best tradition of "no bool flags" --patch could may be be I had planned to use the value for the diff format. Something like `--patch unified` being the...

I have a draft implementation that uses an API like that of external git-diff drivers. It works reasonably well. However, to be complete, it requires the PRs on type(change)-annotation listed...

The basic framework is done. Conceptually, I arrived at the following: There are five basic cases 1. an addition - the diff is the new file (content), or subdataset description...

I tried to load this in my head again after vacation and failed so far. Maybe it is better to close it, and have another attempt at some point in...