From: FCC <fccaner@REMOVEMEgmail.com>
Subject: Re: why does .emacs.desktop fail?
Date: Thu, 14 Jul 2005 14:22:43 +0200 [thread overview]
Message-ID: <db5led$2pc$1@defalla.upc.es> (raw)
In-Reply-To: <1121291999.117201.135360@o13g2000cwo.googlegroups.com>
rgb articulated on 07/14/05 00:02:
>>On both systems I use GNU Emacs 21.3.50.1.
>
>
> If this is true then you are using a highly unstable version to which
> many months of updates have since been applied. You might first try
> using the latest CVS which reports a version number of 22.0.50.1.
> Your problem may still exist but upgrading would be a very big step
> to try first.
>
No luck. I have installed
GNU Emacs 22.0.50.1 (i386-pc-Linux-gnu, X toolkit, Xaw3d scroll bars) of
2005-07-12 on malambruno, modified by Debian
and the behavior described in the original post persists.
Thanks,
--
FCC.
===
The taller the bamboo grows, the lower it bends.
-Chinese saying.
next prev parent reply other threads:[~2005-07-14 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 11:04 why does .emacs.desktop fail? FCC
2005-07-13 22:02 ` rgb
2005-07-14 12:22 ` FCC [this message]
2005-07-14 2:49 ` Stefan Monnier
2005-07-14 12:42 ` FCC
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='db5led$2pc$1@defalla.upc.es' \
--to=fccaner@removemegmail.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).