unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: emacs 22.1 hogging CPU
Date: Tue, 24 Jul 2007 09:47:01 +0530	[thread overview]
Message-ID: <e3f230850707232117h665d1727p9e13dbc61e9d28c1@mail.gmail.com> (raw)
In-Reply-To: <E1ID2J1-00088K-4I@fencepost.gnu.org>

Hi,

On 7/23/07, Richard Stallman <rms@gnu.org> wrote:
> Maybe the feature could involve an alist whose elements look like
> (FILE VARIABLE REGEXP ERROR).  It could be initialized to
>
> (("semantic.el" semantic-version "2.0pre3"
>   "Version %s of %s won't run in Emacs 22"))

IMHO, since this data keeps changing (often or not), this should be
seperated from the general Emacs distribution. Also, this could be a
seperate package which can be loaded if the user wants. The error or
warning could be configured. At times, I may be evaluating a package
and would want to continue with a warning instead of an error which
prevents it from even getting loaded. The data file to drive such
checks could be hosted in the emacs wiki page (or some other place).
The distribution could carry the latest along with it.

Personally, I feel this will be very useful for users and also emacs
developer community in resolving issues. The data file can be a first
check to find out if it is a known issue.

-dky

-- 
Dhruva Krishnamurthy
Contents reflect my personal views only!

  reply	other threads:[~2007-07-24  4:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAY144-F34A23709898886E12A3C1984120@phx.gbl>
2007-06-20 13:28 ` emacs 22.1 hogging CPU Richard Stallman
2007-07-23 18:06 ` Richard Stallman
2007-07-24  4:17   ` dhruva [this message]
2007-07-24 22:17     ` Richard Stallman
2007-07-24  5:10   ` Dan Nicolaescu
2007-07-24 13:12     ` Stefan Monnier
2007-07-24 22:17     ` Richard Stallman

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=e3f230850707232117h665d1727p9e13dbc61e9d28c1@mail.gmail.com \
    --to=dhruvakm@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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).