unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: upro <upro@gmx.net>
Subject: Re: one key is beeping - don't know why...
Date: Thu, 07 Aug 2003 15:00:50 +0200	[thread overview]
Message-ID: <87smodipvh.fsf@lux99.home> (raw)
In-Reply-To: 3F310A11.6050707@yahoo.com

Kevin Rodgers <ihs_4664@yahoo.com> writes:

> upro wrote:
>
>  > Kevin Rodgers <ihs_4664@yahoo.com> writes:
>  >>upro wrote:
>  >>
>  >>>Whenever I hit the AltGr key within emacs it beeps. AltGr does not
>  >>>beep in other programs, and it did not beep prior to upgrading to
>  >>>Slackware 9.0 (from 8.1). I have no clue what happened...
>  >>>
>  >>1. What does it do?  Try typing `C-h k AltGr' and note the message in
>  >>    the echo area (or the *Help* buffer, if the key is actually bound);
>  >
>  > THe key apparently is not nbound. The minibuffer says: <key-3> is
>  > undefined.
>  >
>  >>   then type `C-h l' and note the contents of the *Help* buffer.
>  >
>  > Lossage also says <key-3>. I had already tried that.
>
> I think that indicates that your keyboard is sending keysym 3, which is
> not being recognized by XKeysymToString (or your configuration did not
> #define HAVE_WINDOW_SYSTEM); see modify_event_symbol() in src/keyboard.c.
>
>  >>2. What do you want it to do?
>  >
>  > I need t to type parentheses like []{}, or the tilde etc. (I have a
>  > German keyboard layout).
>  >
>  > The beeping bothers enourmously, since it implies an error. The
>  > character is actually produced, but it beeps...
>  >
>  > Do you have any idea how to stop that?
>
> I don't know whether your keyboard is sending the correct keysym, or that
> it needs to be configured differently.  If it is sending the correct keysym,
> perhaps Emacs needs to be configured for its coding system.  You'll need someone
> familiar with your platform and these issues to help you figure that out.

Solved! Apparently I had compiled without leim, abd emacs was trying
to use some language environment that was nonexistsnt. Strange,
thuogh, that everything else worked...

thanks for your help!
-- 
Michael

r-znvy: zvpunry.wryqra  jro.qr (chg gur "@" jurer vg svgf...)
ab fcnz cyrnfr

  reply	other threads:[~2003-08-07 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 17:37 one key is beeping - don't know why upro
2003-08-04 20:19 ` Kevin Rodgers
2003-08-05  9:37   ` upro
2003-08-06 14:00     ` Kevin Rodgers
2003-08-07 13:00       ` upro [this message]
2003-11-07  9:53         ` Clemens Fischer
2003-12-07 16:12           ` Kai Grossjohann
2003-12-07 18:37             ` Eli Zaretskii

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=87smodipvh.fsf@lux99.home \
    --to=upro@gmx.net \
    /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).