# What happens in The nest when I unrecorded a patch?

**URL:** <https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474>\
**Category:** Question\
**Created:** [February 25, 2020, 10:29am UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474 "2020-02-25T10:29:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tae](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tae/32/81_2.png) [@tae](https://discourse.pijul.org/u/tae)\
**Post date:** [February 25, 2020, 10:29am UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474/1 "2020-02-25T10:29:20Z")

</div>

Because I use Pijul only for personal stuff I un-record patches a lot (to remove conflicts) and it surprises me that it always work, i.e. if I push the right patch there’s no conflict at all. I guess the reason is that after the un-record operation a revert is issued, am I right?

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [February 25, 2020, 10:44am UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474/2 "2020-02-25T10:44:19Z")

</div>

Good question. The Nest doesn’t have a working copy, it just generates pages on the fly from the internal datastructure. This means that in the (hopefully not too distant) future, the Nest will output conflicts as a meaningful combination HTML+JS rather than using the ugly conflict markers.

---

<div class="post-metadata">

**Author:** ![tae](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tae/32/81_2.png) [@tae](https://discourse.pijul.org/u/tae)\
**Post date:** [February 25, 2020, 12:38pm UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474/3 "2020-02-25T12:38:02Z")

</div>

Thanks for the answer Pierre. Please let me bother you again to be sure I understood.

> The Nest doesn’t have a working copy, it just generates pages on the fly from the internal datastructure.

When I un-record something locally I get back the changes that the unrecorded patch introduced (which is expected) and I can revert them or create one or more new patches with them. The Nest doesn’t have an “area” where to store changes, it only knows about patches, so when I unrecord something there, the changes introduced by the unrecorded patch are lost and no clean-up is needed.

Did I get it?

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [February 25, 2020, 1:15pm UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474/4 "2020-02-25T13:15:00Z")

</div>

There actually three different things:

- patches
- the graph, sort of a “cache” of applied patches.
- the working copy, which is the set of files you see and edit.

The Nest has the patches and the graph, but no working copy.

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [February 25, 2020, 2:02pm UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474/5 "2020-02-25T14:02:57Z")

</div>

(also, just to be even clearer, what I called the “internal datastructure” in my earlier reply is “the graph” in my latest reply).

---

<div class="post-metadata">

**Author:** ![tae](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/tae/32/81_2.png) [@tae](https://discourse.pijul.org/u/tae)\
**Post date:** [February 25, 2020, 2:14pm UTC](https://discourse.pijul.org/t/what-happens-in-the-nest-when-i-unrecorded-a-patch/474/6 "2020-02-25T14:14:05Z")

</div>

Just as I thought. Thanks for all!
