Re: (b19) I can't use custom anymore (because of themes)

Thursday, 5 August 1999

        Didier Verna <verna(a)inf.enst.fr&gt; writes:

...
         I'm wrong. It's a bug that I fixed some time ago, but
seems to have
 reappeared with the themes stuff: custom doesn't protect symbols with special
 characters in them when writing the custom file. It's a matter of using
 print1-to-string instead of print1 somewhere. I haven't found out where yet. 
This is just a guess: I think it is more related to the comment stuff.
I rewrote the whole write-out logic so it is actually (more) logic[1],
when I merged it in with the theme stuff.

Jan

Footnotes: 
[1]  It was already ugly before. You addition of yet another case just 
made it cross the annoyance barrier.

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998