GNU bug report logs - #4190
allow beeping in pc-select.el

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 4190 in the body.
You can then email your comments to 4190 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: jidanni <at> jidanni.org
To: emacs-pretest-bug <at> gnu.org
Cc: rfrancoise <at> 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

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)

Message #10 received at 4190-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: jidanni <at> jidanni.org
Cc: 4190-done <at> debbugs.gnu.org, rfrancoise <at> 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)

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

Message #15 received at 4190 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: jidanni <at> jidanni.org
To: dann <at> ics.uci.edu
Cc: 4190 <at> debbugs.gnu.org, control <at> debbugs.gnu.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Fri, 21 Aug 2009 19:02:18 +0800

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.

Message #22 received at 4190 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: jidanni <at> jidanni.org
Cc: 4190 <at> debbugs.gnu.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Fri, 21 Aug 2009 07:10:43 -0700 (PDT)

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.

Message #27 received at 4190 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: jidanni <at> jidanni.org
To: dann <at> ics.uci.edu
Cc: 4190 <at> debbugs.gnu.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Fri, 21 Aug 2009 22:22:28 +0800

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

Message #30 received at 4190 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: jidanni <at> jidanni.org
Cc: 4190 <at> debbugs.gnu.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Fri, 21 Aug 2009 10:32:12 -0700 (PDT)

jidanni <at> 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

Message #35 received at 4190 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Juri Linkov <juri <at> jurta.org>
To: Dan Nicolaescu <dann <at> ics.uci.edu>
Cc: 4190 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Sat, 22 Aug 2009 03:29:51 +0300

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

Message #40 received at 4190 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: jidanni <at> jidanni.org
To: juri <at> jurta.org
Cc: dann <at> ics.uci.edu, 4190 <at> debbugs.gnu.org
Subject: Re: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Sat, 22 Aug 2009 08:48:25 +0800

>>>>> "JL" == Juri Linkov <juri <at> jurta.org> writes:
JL> There is such a customizable option already:
JL> (defcustom pc-select-override-scroll-error t
Phew... thank you for telling me this just in time before I embarked on
the debugging adventure recommended.

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.

By the way, the simple.el commands

 beginning-of-buffer
 end-of-buffer

don't beep when already at the beginning and ends of the buffer too!

They should, just like C-p and C-n, C-f etc.

Message #45 received at 4190-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: jidanni <at> jidanni.org
Cc: juri <at> jurta.org, dann <at> ics.uci.edu, 4190-done <at> debbugs.gnu.org
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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.