In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes:
> It happens usually when there are many links in a buffer such as in ERC
> or W3M. I can move around mouse in a w3m buffer with tons of links (such
> as www.6park.com) to catch a crash, which usually happens within a few
> minutes. I
>> But isn't globalbind already a copy of the global map?
Nope.
>> I see no function assq-remove-all. Is this in Emacs 23?
> My guess is, it's (another) one of Stefan's local changes... :)
No. I don't have such a thing here either. But the name should make the
intended behavior clear enough.
Nick Roberts wrote:
> But isn't globalbind already a copy of the global map?
>
> (setq globalbind (cdr (global-key-binding keyseq)))
By experiment, no, eg:
(define-key lisp-interaction-mode-map [menu-bar edit] 'undefined)
M-x tmm-menubar
will delete the Edit menu from _all_ buffers. Add
Stefan Monnier writes:
> >> ! (setq globalbind (assq-delete-all (car-safe item)
> >> globalbind
>
> If I read the code correctly, this is dangerous because it may modify the
> global map. I.e. it should use assq-remove-all or copy-sequence.
But isn't globalbind already a
Richard Stallman <[EMAIL PROTECTED]> writes:
> How can I be sure that the change "only takes action in the bug case" ?
>
> You could add code inside a conditional which tests for that case.
> Then you know it won't affect any other cases.
I don't have a clue to how to write the "conditional w
How can I be sure that the change "only takes action in the bug case" ?
You could add code inside a conditional which tests for that case.
Then you know it won't affect any other cases.
___
emacs-pretest-bug mailing list
[EMAIL PROTECTED]
http://li
> I have a workaround there for this. I call top-level after such
> changes (in this case after changing major mode in a timer).
That is a very bad practice. If there is any case where no other
method is available, we should consider that a serious problem
and implement what is needed so
Lennart Borgman (gmail) wrote:
Another little question: On w32 I failed to apply this patch with the
patch program from gnuwin32 (version 2.5.9). I wonder if this is a
problem with that patch program or something else. How do I continue
when patch fails?
Most of the patch where applied. The p
Chong Yidong wrote:
Richard Stallman <[EMAIL PROTECTED]> writes:
At this stage of the release cycle, a grave bug is one that makes Emacs
crash, or causes really bad redisplay behaviour.
I think redisplay bugs are serious bugs.
In this case, I know what the fix is (see attached patch)
Richard Stallman <[EMAIL PROTECTED]> writes:
> At this stage of the release cycle, a grave bug is one that makes Emacs
> crash, or causes really bad redisplay behaviour.
>
> I think redisplay bugs are serious bugs.
In this case, I know what the fix is (see attached patch). The
trouble is
Where it says this, it would be good to add a cross reference to node
Replace Regexp: "`C-M-%' performs regexp search and replace
(`query-replace-regexp'). It works like `replace-regexp' except that
it queries like `query-replace'." Otherwise, readers might not know
where to find info about `repl
Stefan Monnier writes:
>
> It would probably be good to delay it, but this is not very high priority.
> I've added it to the TODO list.
Thank you.
Lennart Borgman writes:
> If you think it is possible to do it now it would be good. I need this for
> mumamo too. (Mumamo is here: http://www.emacs
Stefan Monnier wrote:
selecting a keymap (e.g. when changing minor-mode, creating 'keymap
overlays, setting overriding-local-map, use-local-map) in a
run-with-timer or run-with-idle-timer event doesn't take immediate
effect.
Consider the following example:
(run-with-timer 3 nil '(lambda ()
> selecting a keymap (e.g. when changing minor-mode, creating 'keymap
> overlays, setting overriding-local-map, use-local-map) in a
> run-with-timer or run-with-idle-timer event doesn't take immediate
> effect.
> Consider the following example:
> (run-with-timer 3 nil '(lambda ()
>
>> ! (setq globalbind (assq-delete-all (car-safe item)
>> globalbind
If I read the code correctly, this is dangerous because it may modify the
global map. I.e. it should use assq-remove-all or copy-sequence.
Stefan
___
ema
> Here is the code that does this:
> (define-key org-mode-map [menu-bar headings] 'undefined)
> (define-key org-mode-map [menu-bar hide] 'undefined)
> (define-key org-mode-map [menu-bar show] 'undefined))
If org-mode-map inherits from outline-mode-map, then it should be OK,
although binding them
Dear Kenichi,
- Kenichi Handa (2007-04-13) wrote:-
>> Here is a backtrace of an Emacs crash. One can encounter this often
>> by moving cursor over links etc. It only happens when using xft font.
>
>> Software: GNU Emacs 23.0.0.11 (i686-pc-linux-gnu, X toolkit) of
>> 2007-04-11
>
>> [2 xft
In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes:
> Here is a backtrace of an Emacs crash. One can encounter this often by
> moving cursor over links etc. It only happens when using xft font.
> Software: GNU Emacs 23.0.0.11 (i686-pc-linux-gnu, X toolkit) of
> 2007-04-11
> [2 xft_cr
Konrad, please see below - can you help?
Begin forwarded message:
From: [EMAIL PROTECTED] (Kim F. Storm)
Date: 13 April 2007 12:25:48 BDT
To: David Reitter <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: crash in Fgarbage_collect -> mem_find
David Reitter <[EMAIL PROTECTED]> writes:
I
David Reitter <[EMAIL PROTECTED]> writes:
> I can't reproduce this. As you might know, this is a Mac/Carbon CVS
> build (April 4) with patches , none of which should affect garbage
> collection.
> I don't have more information, but maybe the stack trace provided is
> helpful enough.
It is only us
Glenn Morris <[EMAIL PROTECTED]> writes:
> Kim F. Storm wrote:
>
>> Should we add quack.el to the list of packages which we recommend people
>> to upgrade when using Emacs 22.1 ? (The list is in etc/NEWS).
>
> I don't think this was a quack + emacs 22 problem, it was just a
> problem in older ve
Richard Stallman <[EMAIL PROTECTED]> writes:
> At this stage of the release cycle, a grave bug is one that makes Emacs
> crash, or causes really bad redisplay behaviour.
>
> I think redisplay bugs are serious bugs.
As you say yourself, what someone _think_ is not a useful argument.
--
K
Richard Stallman <[EMAIL PROTECTED]> writes:
> > Can you track down the bug report(s) which lead up to the fix I
> > installed, so you can confirm that your change also fixes the old
> bug(s).
> > It must be close to the date in the ChangeLog.
>
> IIRC, there were quite a lot of t
I can't reproduce this. As you might know, this is a Mac/Carbon CVS
build (April 4) with patches , none of which should affect garbage
collection.
I don't have more information, but maybe the stack trace provided is
helpful enough.
Begin forwarded message:
From: Konrad Podczeck <[EMAIL PR
- Jan Djärv (2007-04-13) wrote:-
>> Software: GNU Emacs 23.0.0.11 (i686-pc-linux-gnu, X toolkit) of
>> 2007-04-11
>>
>> Here is a backtrace of an Emacs crash. One can encounter this often by
>> moving cursor over links etc. It only happens when using xft font.
>>
>
> If you are using the u
If slime is up and running and M-x slime is called again you are asked if
you
want to start an addtional inferior lisp. If this question is answered with
n
Emacs will crash. The action that triggers the crash is (kill-buffer "
*cl-connection*")
Can you reproduce the bug with the attached (100% u
Hello,
selecting a keymap (e.g. when changing minor-mode, creating 'keymap
overlays, setting overriding-local-map, use-local-map) in a
run-with-timer or run-with-idle-timer event doesn't take immediate
effect.
Consider the following example:
(run-with-timer 3 nil '(lambda ()
Leo skrev:
Hello,
Software: GNU Emacs 23.0.0.11 (i686-pc-linux-gnu, X toolkit) of
2007-04-11
Here is a backtrace of an Emacs crash. One can encounter this often by
moving cursor over links etc. It only happens when using xft font.
If you are using the unicode2 branch, please put that in th
28 matches
Mail list logo
