[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: calc-dispatch problem

From: Slawomir Nowaczyk
Subject: Re: calc-dispatch problem
Date: Sun, 10 Sep 2006 21:11:22 +0200

On Sun, 10 Sep 2006 20:19:29 +0200
David Kastrup <address@hidden> wrote:

#> Slawomir Nowaczyk <address@hidden> writes:
#> > Hello,
#> >
#> > Start emacs --no-init-file --no-site-file
#> >
#> > Evaluate (global-set-key (kbd "M-`") 'calc-dispatch)
#> >
#> > Press "M-`" twice, *fast*. I get an error "calc-embedded-edit: Expected 
#> >
#> > If I press "M-`" slowly, however (with about 1-2 second pause between
#> > first and second keypress), calc opens properly.
#> >
#> > Strange. Any ideas?
#> Is this on X11 or a tty?
#> If it is the latter, this sounds like a function key sequence.

It's on M$ Windows:

In GNU Emacs (i386-msvc-nt5.1.2600)
 of 2006-09-05 on FIONA
X server distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-msvc (13.10) --cflags 

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENG
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  encoded-kbd-mode: t
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  line-number-mode: t

Recent input:
<return> <S-insert> C-x C-e M-` M-` M-x r e p o r t 
- e m <tab> <return>

Recent messages:
Mark set
Loading edmacro...done
Loading calc...done
Loading calc-embed...done
Loading calc-aent...done
calc-embedded-edit: Expected `)'
Loading emacsbug...
Loading regexp-opt...done
Loading emacsbug...done

 Best wishes,
   Slawomir Nowaczyk
     ( address@hidden )

A little inaccuracy sometimes saves a ton of explanation.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]