unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Steve" <steveneo@21cn.com>
Subject: Re: why emacs 21.3 windows version can't work well?
Date: Sat, 21 Feb 2004 00:12:45 +0800	[thread overview]
Message-ID: <001101c3f7cc$828af640$b1023dda@ndp> (raw)

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

Same problems, in fact, when I extract this version emacs, and startup without any other installation, its calendar won't work either. I also run addpm.exe to install emacs.

Error message:
Loading calendar...done
update-calendar-mode-line: Invalid read syntax: "#"

When I input "M-x calendar" again, error message turn into:
update-calendar-mode-line: Invalid read syntax: "] in a list"




"niDapeng"<steveneo@bogus.example.com> writes:

> I download emacs 21.3.1 Windows version( release date:
> 26-Jan-2004). I meet so many problems. First, it can run up
> calendar, mail, etc. Others, Many lisp programs can't work well too,
> such as screen-lines.el, XAE(for docbook, emacs even can't startup
> if installed XAE)!

What happens if you start Emacs as follows:

        emacs -q -no-site-file

And then type M-x calendar RET?

Does Emacs crash?  Does it print an error message?  What error
message?

Kai

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
Help-gnu-emacs mailing list
Help-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnu-emacs

             reply	other threads:[~2004-02-20 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 16:12 Steve [this message]
     [not found] <mailman.164.1077293682.340.help-gnu-emacs@gnu.org>
2004-02-20 21:00 ` why emacs 21.3 windows version can't work well? Jason Rumney
     [not found] <mailman.141.1077255863.340.help-gnu-emacs@gnu.org>
2004-02-20  8:03 ` Kai Grossjohann
2004-02-20 16:43 ` Cheng Gao
  -- strict thread matches above, loose matches on Subject: below --
2004-02-20  5:38 niDapeng

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='001101c3f7cc$828af640$b1023dda@ndp' \
    --to=steveneo@21cn.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).