unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: jidanni@jidanni.org
Cc: 4190@emacsbugs.donarmstrong.com
Subject: 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)	[thread overview]
Message-ID: <200908211732.n7LHWCtZ021381@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87skflb61n.fsf@jidanni.org> (jidanni@jidanni.org's message of "Fri, 21 Aug 2009 22:22:28 +0800")

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





  reply	other threads:[~2009-08-21 17:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200908202036.n7KKa06C011983@godzilla.ics.uci.edu>
2009-08-18 10:02 ` bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep jidanni
2009-08-20 20:45   ` bug#4190: marked as done (23.1.50; <prior> and <next> of pc-select.el don't beep) Emacs bug Tracking System
2009-09-12  0:40   ` bug#4190: marked as done (allow beeping in pc-select.el) Emacs bug Tracking System
2009-08-21 11:02 ` bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep jidanni
2009-08-21 11:10   ` Processed (with 5 errors): " Emacs bug Tracking System
2009-08-21 14:10   ` Dan Nicolaescu
2009-08-21 14:22     ` jidanni
2009-08-21 17:32       ` Dan Nicolaescu [this message]
2009-08-22  0:29     ` Juri Linkov

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=200908211732.n7LHWCtZ021381@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=4190@emacsbugs.donarmstrong.com \
    --cc=jidanni@jidanni.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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