From: Peter <cl-isabelle-users@lists.cam.ac.uk>
Hi List,
I've currently two versions of my Isabelle_LLVM theories. In the ROOT
file, they are declared as session with name Isabelle_LLVM.
This leads to isabelle re-building the image each time I start it with a
different version from last time.
This makes it very time-consuming to work with two different versions,
e.g., during updating dependent projects, and working with projects that
depend on different versions.
Is there a way (apart from artificially renaming one of the sessions in
its ROOT file) to manage these separate versions of the same session?
--
Peter
1)
cd A
cat ROOTS
<Refers to Version 1>
isabelle jedit -d . -l Isabelle_LLVM ...
2)
cd B
cat ROOTS
<Refers to Version 2>
isabelle jedit -d . -l Isabelle_LLVM ...
-- this will now always rebuild the image using Version2 files ... and
running 1) again will rebuild again, and so on.
From: "\"Becker, Hanno\"" <cl-isabelle-users@lists.cam.ac.uk>
Hi Peter,
I have this in my etc/settings:
if [ -n "$ISABELLE_HEAP_SUFFIX" ]; then
ISABELLE_HEAPS="$ISABELLE_HEAPS-$ISABELLE_HEAP_SUFFIX"
fi
Then you just set e.g. export ISABELLE_HEAP_SUFFIX=A in your shell, and all heaps go to .isabelle/Isabelle2025-2/heaps-A by default.
Does that help?
Kind regards,
Hanno
From: cl-isabelle-users-request@lists.cam.ac.uk <cl-isabelle-users-request@lists.cam.ac.uk> on behalf of Peter <cl-isabelle-users@lists.cam.ac.uk>
Date: Tuesday, 28 April 2026 at 11:51
To: cl-isabelle-users@lists.cam.ac.uk <cl-isabelle-users@lists.cam.ac.uk>
Subject: [EXTERNAL] [isabelle] Managing heap-images of different versions of same development
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Hi List,
I've currently two versions of my Isabelle_LLVM theories. In the ROOT
file, they are declared as session with name Isabelle_LLVM.
This leads to isabelle re-building the image each time I start it with a
different version from last time.
This makes it very time-consuming to work with two different versions,
e.g., during updating dependent projects, and working with projects that
depend on different versions.
Is there a way (apart from artificially renaming one of the sessions in
its ROOT file) to manage these separate versions of the same session?
--
Peter
1)
cd A
cat ROOTS
<Refers to Version 1>
isabelle jedit -d . -l Isabelle_LLVM ...
2)
cd B
cat ROOTS
<Refers to Version 2>
isabelle jedit -d . -l Isabelle_LLVM ...
-- this will now always rebuild the image using Version2 files ... and
running 1) again will rebuild again, and so on.
From: Fabian Huch <huch@in.tum.de>
Within one Isabelle environment, sessions are unique, so having two
different versions in there doesn't really make sense.
But we do often have multiple Isabelle environments, e.g. devel vs.
releases. You can create distinct Isabelle environments from a
repository copy by setting the ISABELLE_IDENTIFIER, e.g. via the "-I"
option in Admin/init.
Fabian
On 4/28/26 12:50, Peter (via cl-isabelle-users Mailing List) wrote:
Hi List,
I've currently two versions of my Isabelle_LLVM theories. In the ROOT
file, they are declared as session with name Isabelle_LLVM.This leads to isabelle re-building the image each time I start it with
a different version from last time.This makes it very time-consuming to work with two different versions,
e.g., during updating dependent projects, and working with projects
that depend on different versions.Is there a way (apart from artificially renaming one of the sessions
in its ROOT file) to manage these separate versions of the same session?--
Peter
1)
cd A
cat ROOTS
<Refers to Version 1>
isabelle jedit -d . -l Isabelle_LLVM ...
2)
cd B
cat ROOTS
<Refers to Version 2>
isabelle jedit -d . -l Isabelle_LLVM ...
-- this will now always rebuild the image using Version2 files ... and
running 1) again will rebuild again, and so on.
Last updated: May 02 2026 at 13:17 UTC