On 2022-09-14 06:28, Thomas Passin wrote: > I wondered about that message. I saw it after pulling the latest > changeset. I haven't set any uAs of any variety, myself. Maybe some > plugin? > > On Wednesday, September 14, 2022 at 4:53:20 AM UTC-4 Edward K. Ream wrote: > >> On Wednesday, September 14, 2022 at 3:38:40 AM UTC-5 Edward K. Ream wrote: >> >> P.S. I did not sufficiently consider compatibility issues when approving >>> PR #2818 <https://github.com/leo-editor/leo-editor/pull/2818>, which >>> says: >>> >>> "Older versions of Leo will not be able to read files that use this >>> feature. Files not using this feature are not affected." >>> >> >> I've just taken a look at the relevant read code: FastRead.resolveUa*.* >> In fact, older version of Leo *will* be able to read files with _json uAs. >> >> As I read the code, Leo will issue the warning: f"can not unhexlify >> {attr}={val}" for _json uAs, but almost-never-issued warnings shouldn't >> disqualify the PR. >> >> Edward >> > User attributes are used by several plugins in Leo. I asked for JSON support because the only options were 'plain string' and 'pickle'. The former is too limiting and the latter isn't text, which can be a problem when you need to examine or edit a .leo file by hand. Debugging user icons was needlessly troublesome because of it.
-- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/e5a2a556-fbd4-3ea1-f66b-593bb8802db7%40runbox.com.
