On Fri, 2017-09-08 at 17:51 +0200, Johan Vromans wrote: > On Fri, 08 Sep 2017 15:13:23 +0100, Richard Shann <rich...@rshann.plus.com> > wrote: > > > (I notice that your diff command was comparing files of that form > > > > % diff .denemo-2.1.3-280c7c0/denemorc .denemo-2.2.1-8561e23/denemorc > > > > but I don't see how that could have been your problem). > > It does seem to be. > > I removed all rubbish and renamed .denemo-2.1.3-280c7c0 to .denemo-2.1.3. > > % ls -ld ~/.denemo* > drwxr-x--- 4 jv jv 4096 Sep 7 22:40 .denemo-2.1.3/ > > Starting denemo offers to import the old settings, and it works as it > should. > > I removed the new .denemo-2.2.1-a7a7d37, moved .denemo-2.1.3 back to > .denemo-2.1.3-280c7c0 and tried again. > > % ls -ld .denemo* > drwxr-x--- 4 jv jv 4096 Sep 7 22:40 .denemo-2.1.3-280c7c0/ > > Denemo offers to import the old settings, but ends up with mostly (all?) > default values.
Ah, right I see. What happens is that Denemo recognizes .denemo-2.1.3-280c7c0 as if it was .denemo-2.1.3 but when it tries to read the file it tries to read .denemo-2.1.3 - it doesn't retain a record of what the file was actually called, but reconstructs it. Question: should Denemo support directories with names other than the ones it generates? That is, Denemo creates .denemo.x.y.z and on the face of it should reject .denemo.x.y.z?* Is that ok, or is something appending those characters to the directory name (e.g. is something changing the Denemo version from .denemo-2.1.3 of the source code as we release it to denemo-2.1.3-280c7c0 for example?) Richard _______________________________________________ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
