bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[jidanni]

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)

bug#4190: marked as done (23.1.50; <prior> and <next> of pc-select.el don't beep)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

Your message dated Thu, 20 Aug 2009 13:36:00 -0700 (PDT)
with message-id <200908202036.n7KKa06C011983@godzilla.ics.uci.edu>
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 23.1.50; <prior> and <next> of pc-select.el don't beep
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

[-- Attachment #2: Type: message/rfc822, Size: 2550 bytes --]

From: jidanni@jidanni.org
To: emacs-pretest-bug@gnu.org
Cc: rfrancoise@debian.org
Subject: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Tue, 18 Aug 2009 18:02:19 +0800
Message-ID: <87y6pha190.fsf@jidanni1.jidanni.org>

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)


[-- Attachment #3: Type: message/rfc822, Size: 2810 bytes --]

From: Dan Nicolaescu <dann@ics.uci.edu>
To: jidanni@jidanni.org
Cc: 4190-done@emacsbugs.donarmstrong.com, rfrancoise@debian.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Thu, 20 Aug 2009 13:36:00 -0700 (PDT)
Message-ID: <200908202036.n7KKa06C011983@godzilla.ics.uci.edu>

jidanni@jidanni.org writes:

  > 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>.

Not a bug, pc-select.el  tries to:
;;; pc-select.el --- emulate mark, cut, copy and paste from Motif
;;;                   (or MAC GUI or MS-windoze (bah)) look-and-feel
;;;                            including key bindings.

not beeping is the behavior of prior and next on those platforms.

  > 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)

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

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

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

[-- Attachment #2: Type: message/rfc822, Size: 2550 bytes --]

From: jidanni@jidanni.org
To: emacs-pretest-bug@gnu.org
Cc: rfrancoise@debian.org
Subject: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Tue, 18 Aug 2009 18:02:19 +0800
Message-ID: <87y6pha190.fsf@jidanni1.jidanni.org>

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)


[-- Attachment #3: Type: message/rfc822, Size: 1679 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: jidanni@jidanni.org
Cc: juri@jurta.org, dann@ics.uci.edu, 4190-done@emacsbugs.donarmstrong.com
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
Message-ID: <87iqfpq9wn.fsf@stupidchicken.com>

> 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.

bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[jidanni]

reopen 4190
retitle 4190 allow beeping in pc-select.el
DN> not beeping is the behavior of prior and next on those platforms.
1. Then there should be a way to toggle back on the beeping.
2. especially as I am not willingly using pc-select, but instead it has been
foisted upon me via a side effect of some command in
http://jidanni.org/comp/configuration/.emacs
Indeed it would take hours of debugging to figure out which.

Processed (with 5 errors): Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[Emacs bug Tracking System]

Processing commands for control@emacsbugs.donarmstrong.com:

> reopen 4190
Bug #4190 {Done: Dan Nicolaescu <dann@ics.uci.edu>} [emacs] 23.1.50; <prior> and <next> of pc-select.el don't beep
> retitle 4190 allow beeping in pc-select.el
Bug #4190 [emacs] 23.1.50; <prior> and <next> of pc-select.el don't beep
Changed bug title to 'allow beeping in pc-select.el' from '23.1.50; <prior> and <next> of pc-select.el don't beep'
> DN> not beeping is the behavior of prior and next on those platforms.
Unknown command or malformed arguments to command.

> 1. Then there should be a way to toggle back on the beeping.
Unknown command or malformed arguments to command.

> 2. especially as I am not willingly using pc-select, but instead it has been
Unknown command or malformed arguments to command.

> foisted upon me via a side effect of some command in
Unknown command or malformed arguments to command.

> http://jidanni.org/comp/configuration/.emacs
Unknown command or malformed arguments to command.

Too many unknown commands, stopping here.

Please contact me if you need assistance.

Don Armstrong
(administrator, Emacs bugs database)

bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[Dan Nicolaescu]

notabug 4190
thanks

  > DN> not beeping is the behavior of prior and next on those platforms.
  > 1. Then there should be a way to toggle back on the beeping.

That goal of this package is to be compatible with a platform, we cannot
arbitrarily just turn off features...


  > 2. especially as I am not willingly using pc-select, but instead it has been
  > foisted upon me via a side effect of some command in
  > http://jidanni.org/comp/configuration/.emacs
  > Indeed it would take hours of debugging to figure out which.

That does not seem like a good reason to add an extra customization flag
in emacs, a flag that would be used by a single user.

bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[jidanni]

So please tell me how I can get untangled from pc-select.
I do not want to use pc-select.
I did not intentionally chose to use pc-select.
>> http://jidanni.org/comp/configuration/.emacs

bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[Dan Nicolaescu]

jidanni@jidanni.org writes:

  > So please tell me how I can get untangled from pc-select.
  > I do not want to use pc-select.
  > I did not intentionally chose to use pc-select.

Try to figure out what uses it.
You can do that by doing a binary search in your .emacs: comment out
half of it, see if you still get pc-select, continue the process until
you get the place that requires it.


Or you can add 
(error "pc-select here")
on the first line of pc-select.el, 
byte compile the file

and run 

emacs -Q
M-: (setq debug-on-error t) RET
M-x load-file RET ~/.emacs RET

and look at the debug backtrace and figure out exactly what wants to use
pc-select.
 

  > >> http://jidanni.org/comp/configuration/.emacs

bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep

[Juri Linkov]

>   > DN> not beeping is the behavior of prior and next on those platforms.
>   > 1. Then there should be a way to toggle back on the beeping.
>
> That does not seem like a good reason to add an extra customization flag
> in emacs, a flag that would be used by a single user.

There is such a customizable option already:

(defcustom pc-select-override-scroll-error t
  "*Non-nil means don't generate error on scrolling past edge of buffer.
This variable applies in PC Selection mode only.
The scroll commands normally generate an error if you try to scroll
past the top or bottom of the buffer.  This is annoying when selecting
text with these commands.  If you set this variable to non-nil, these
errors are suppressed."
  :type 'boolean
  :group 'pc-select)

-- 
Juri Linkov
http://www.jurta.org/emacs/