bug#4190: marked as done (allow beeping in pc-select.el)

[Emacs bug Tracking System]

Your message dated Fri, 11 Sep 2009 20:33:28 -0400
with message-id <87iqfpq9wn.fsf@stupidchicken.com>
and subject line Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el 
don't beep
has caused the Emacs bug report #4190,
regarding allow beeping in pc-select.el
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
4190: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4190
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 23.1.50; <prior> and <next> of pc-select.el don't beep
>
>
>
>
> Date: 
>
> Tue, 18 Aug 2009 18:02:19 +0800
>
>
>
>
> All I know is this doesn't beep/flash when it hits the beginning of the buffer:
>   <prior> runs the command scroll-down-nomark, which is an interactive
>   compiled Lisp function in `pc-select.el'.
>
> Same for <next>.
>
> However C-p and C-n still beep properly.
>
> You may ask "why am I using pc-select.el". I don't know. It must be due
> to http://jidanni.org/comp/configuration/.emacs
>
> In GNU Emacs 23.1.50.1 (i486-pc-linux-gnu, GTK+ Version 2.16.5)
>  of 2009-08-15 on elegiac, modified by Debian
>  (emacs-snapshot package, version 1:20090814-1)
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
>
>
>
>
> Date: 
>
> Fri, 11 Sep 2009 20:33:28 -0400
>
>
>
>
> > The docstrings of <prior> and <next> of pc-select.el should make a note
> > of this variable, as should any others that might bang into the
> > beginning and end of the buffer too.
>
> Fixed, thanks.
>
> --- End Message ---