unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Aaron Meurer <asmeurer@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: First character beeps screen sometimes
Date: Fri, 9 Mar 2012 15:03:34 -0700	[thread overview]
Message-ID: <CAKgW=6LFuAy9X7GeY3va_9-oL27+S60g7Cy0sXoaEXf_rUsURw@mail.gmail.com> (raw)
In-Reply-To: <EB5D32AFC1E2481F97F991F481C4B213@us.oracle.com>

On Fri, Mar 9, 2012 at 2:23 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> I could use some help debugging an annoying problem.  Sometimes when I
>> start emacs,
>
> When you start or later?  Further on you seem to suggest it happens well after
> startup.

Ah, what I mean is, when I start emacsclient, i.e., when I open a
file.  If I could figure out how to reproduce this consistently, I
could check if it happens with regular emacs or not.

>
>> the first character I type is not inserted, but rather,
>> causes the screen to flash....
>> it happens almost every time I edit a commit message after making a
>> commit in a git repository (but not every time).
>
> This probably won't help, but have you checked that Emacs is not expecting you
> to answer something like `y-or-n-p'? If you type something it doesn't want that
> will result in a beep (visible or audible).
>

I never notice any.  I usually only notice this because I start typing
and the first character is not entered (hence why this is so
annoying).  But I don't think there's anything like that, or at least
not visible.  I've noticed that emacsclient doesn't always show
everything (for example, if there's a problem in my init file, regular
emacs will tell me about the problem, but emacsclient, even with the
first start of the daemon, will not).

Aaron Meurer



  reply	other threads:[~2012-03-09 22:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 21:14 First character beeps screen sometimes Aaron Meurer
2012-03-09 21:23 ` Drew Adams
2012-03-09 22:03   ` Aaron Meurer [this message]
2012-03-10  7:26 ` XeCycle
2012-03-10 20:47   ` Aaron Meurer
2012-03-10 20:50     ` Aaron Meurer
2012-03-11  3:40       ` Aaron Meurer
2012-03-11  9:02         ` Peter Dyballa
2012-03-11 17:53           ` Matt McClure
2012-03-11 20:56             ` Peter Dyballa
2012-03-11 21:33               ` Aaron Meurer
2012-03-11 21:43                 ` Matt McClure
2012-03-11 22:39                   ` Aaron Meurer
2012-03-11 23:47                     ` Drew Adams
2012-03-12  0:11                       ` Aaron Meurer
2012-03-12  0:31                         ` Peter Dyballa
2012-03-12  2:15                           ` Aaron Meurer
2012-03-11 23:45                 ` Peter Dyballa
2012-03-13  3:01                 ` XeCycle
2012-03-13  3:58                   ` Aaron Meurer
2012-03-13  4:15                   ` Yaoyuan
2012-03-14 11:29                     ` XeCycle
2012-03-11 21:09             ` Aaron Meurer

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='CAKgW=6LFuAy9X7GeY3va_9-oL27+S60g7Cy0sXoaEXf_rUsURw@mail.gmail.com' \
    --to=asmeurer@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).