From: Kenichi Handa <handa@etl.go.jp>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: desktop.el problem [Re: X-Symbol 4.0e; Emacs port (fwd)]
Date: Thu, 25 Jul 2002 11:47:33 +0900 (JST) [thread overview]
Message-ID: <200207250247.LAA28221@etlken.m17n.org> (raw)
In-Reply-To: <67B8CED503F3D511BB9F0008C75DAD660212AE84@dbwdfx17.wdf.sap-ag.de> (christoph.wedler@sap.com)
In article <67B8CED503F3D511BB9F0008C75DAD660212AE84@dbwdfx17.wdf.sap-ag.de>, "Wedler, Christoph" <christoph.wedler@sap.com> writes:
> Desktop also writes the contents of `kill-ring' and `register-alist',
> and probably some history variables which could contain such
> characters.
Oops...
Then, it's a general problem of desktop. If a user define a
new charset in a session, and there's a string containing
that charset in kill-ring, he always fails in the next
session while recovering the previous session.
It seems that the only way to solve it is to save also those
charset definitions. But, saving it in .emacs.desktop is
useless. We must save it in a file that is loaded before
.emacs.desktop is loaded.
Another workaround is not to save such strings that contains
a characters of newly defined charsets.
What do people think? I prefer the latter method because
the former method is not robust. It won't be able to deal
with the situation that a user defines a charset in his
.emacs before .emacs.desktop is loaded.
By the way, emacs-unicode won't have this problem.
---
Ken'ichi HANDA
handa@etl.go.jp
next parent reply other threads:[~2002-07-25 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67B8CED503F3D511BB9F0008C75DAD660212AE84@dbwdfx17.wdf.sap-ag.de>
2002-07-25 2:47 ` Kenichi Handa [this message]
2002-07-25 5:18 ` desktop.el problem [Re: X-Symbol 4.0e; Emacs port (fwd)] Eli Zaretskii
2002-07-25 18:07 ` Richard Stallman
2002-07-26 1:57 ` Kenichi Handa
2002-07-27 18:52 ` Richard Stallman
2002-07-30 6:32 ` Kenichi Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207250247.LAA28221@etlken.m17n.org \
--to=handa@etl.go.jp \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.