unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: christoph.wedler@sap.com, emacs-devel@gnu.org
Subject: Re: desktop.el problem [Re: X-Symbol 4.0e; Emacs port (fwd)]
Date: Thu, 25 Jul 2002 12:07:10 -0600 (MDT)	[thread overview]
Message-ID: <200207251807.g6PI7A007627@aztec.santafe.edu> (raw)
In-Reply-To: <200207250247.LAA28221@etlken.m17n.org> (message from Kenichi Handa on Thu, 25 Jul 2002 11:47:33 +0900 (JST))

    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.

Could you explain why this fails?  What does the printed representation
of such a string look like, and how does it depend on having the character
set loaded?

Perhaps we should change the printed representation of such strings so
that they can be read back in all circumstances.  If characters in
user-defined character are written as \-sequences, would that do it?

    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.

Could you explain the reason for that?
Are these characters being output literally by prin1,
and then encoded when .emacs.desktop is saved?
If that is so, there are many points in that sequence that we could change.

  parent reply	other threads:[~2002-07-25 18:07 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 ` desktop.el problem [Re: X-Symbol 4.0e; Emacs port (fwd)] Kenichi Handa
2002-07-25  5:18   ` Eli Zaretskii
2002-07-25 18:07   ` Richard Stallman [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207251807.g6PI7A007627@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=christoph.wedler@sap.com \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).