Re: First character beeps screen sometimes

[Aaron Meurer <asmeurer@gmail.com>]

Good to know it's not just me then :)

I'm not surprised that it's a bug with emacsclient.  emacsclient has a
bunch of little quirky bugs where one client will interfere with
another and things like that.

I can say that this has nothing to do with X.  I compiled emacs with
--with-x=no, and use it entirely in the terminal.

Is there an existing emacs issue about this, or should I report it?
Where is the emacs issue tracker even located?

I just discovered how to reproduce this consistantly.  If I close
emacs using M-x save-buffers-kill-emacs and restart emacs client (I
use emacsclient -a "" -nw file), it always does this with the file I
open.  It does it in cases other than this too, but assuming it's all
the same bug, I should be able to help debug it using this fact.

There is no text printed in the info buffer, except for the standard
"When done with a buffer, type C-x #" before I start typing.

Finally, is there a way to consistently work-around this?  Or maybe
someone industrious can just fix the bug and get it over with.

Aaron Meurer

On Sat, Mar 10, 2012 at 12:26 AM, XeCycle <XeCycle@gmail.com> wrote:
> Aaron Meurer <asmeurer@gmail.com> writes:
>
> [...]
>
>> Final note: I use emacsclient with emacs daemon, if that might make a
>> difference.  As far as version goes, I am using a very recent build
>> from the development repo of emacs.
>
> "emacsclient" is the cause.  I can reproduce this, by doing
> `emacsclient -c -e '(gnus)'`, when I have no X frames open at the
> time.  Sometimes can also be reproduced even when an X frame is
> already there, though not always.
>
> I think this is an ancient bug.  Noticed this at the time I began
> using emacsclient.
>
> --
> Carl Lei (XeCycle)
> Department of Physics, Shanghai Jiao Tong University
> OpenPGP public key: 7795E591
> Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591