From: jasonr (Jason Rumney) @ f2s.com
Subject: Re: w32 mule status
Date: Fri, 30 Jul 2004 08:38:28 +0100 [thread overview]
Message-ID: <uk6wm3pxn.fsf@jasonrumney.net> (raw)
In-Reply-To: 10gjaub84s2os18@corp.supernews.com
"Edward Casey" <ejmn@cpinternet.com> writes:
> Does any of you know where the info reported by Options> Mule > Show all
> of Mule status, is stored between emacs sessions?
It's not stored, unless you explicitly save it to a file with C-x C-w.
> I have a satisfactory setup on one machine that I am not able to
> emulate on another. I have compared all the w32-* variables and they
> are the same on both machines. The problem must have something to
> do with fontsets or extended character mappings. Help!
You haven't described the problem, so I don't know how valid that
assumption is. I assume you wanted to compare the two files to see
what is different?
next prev parent reply other threads:[~2004-07-30 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 2:00 w32 mule status Edward Casey
2004-07-30 7:38 ` Jason Rumney [this message]
2004-08-01 19:14 ` Edward Casey
2004-08-01 20:16 ` Jason Rumney
2004-08-01 22:19 ` Edward Casey
2004-08-02 7:49 ` Jason Rumney
2004-08-02 16:26 ` Edward Casey
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=uk6wm3pxn.fsf@jasonrumney.net \
--to=jasonr@f2s.com \
/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.
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).