Kim F. Storm wrote:
(gdb) r -q -xrm 'Emacs*fontSet: -*-helvetica-medium-r-*--*-120-*-*-*-*,*'
Starting program: /home/kfs/fsf/latest/src/emacs -q -xrm 'Emacs*fontSet:
-*-helvetica-medium-r-*--*-120-*-*-*-*,*'
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert strin
Trying to set up nxml-mode I was bitten by `magic-mode-alist'. The
installation instructions of the mode tell you to change
`auto-mode-alist' in order to load the mode for the specified file
endings. This works fine with new files but fails on some existing
files I have. The problem is that `aut
I am not sure it is due to my change nor have any idea on what could
cause it. Maybe a guru of the custom/widget internals could help?
I hope we have one. I don't know any more about this code than you
do; probably less, since I have had more time to forget.
The experience of Custom has
> So I think it would be better to document that define-minor-mode
> and easy-mmode-define-global-mode default the group based
> solely on the mode name.
Ok, that was the actual behavior up till now anyway. For
define-minor-mode and easy-mmode-define-global-mode, it doesn't ma
Richard Stallman wrote:
The use of custom-current-group seems like a bad practice to me.
It is unreliable to make one defun depend on whatever was lying around
from a previous defun in this way. It has the result that moving
code from one place in a file to another changes its meaning
> This seems like a good change, but wouldn't it be cleaner to do the
> add-to-list call be done where next-error-overlay-arrow is defined?
It is not good to always have next-error-overlay-arrow in
overlay-arrow-variable-list even when no compilation was started.
This may slow down redisplay and i
> It looks good now. In compilation-sentinel you might like to add:
>
>;; buffer killed
>(set-process-buffer proc nil)
> + (delq 'next-error-overlay-arrow-position overlay-arrow-variable-list)
>
> although I don't know what the performance penalty is, if any, if you don't.
This is not the
> There could be a problem at the lisp level though as
> overlay-arrow-string is nil unless it has been set explicitly by some
> package. Perhaps it would make sense to initialize the global value
> of overlay-arrow-string to "=>" which most packages want?
>
> Can you produce a simple, self-contai
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> Can you try this:
>> % emacs -xrm 'Emacs*fontSet: -*-helvetica-medium-r-*--*-120-*-*-*-*-*-*,*'
>
> and then try again
>
> % emacs -xrm 'Emacs*fontSet: -*-helvetica-medium-r-*--*-120-*-*-*-*,*'
>
> to see if the "-*-*" makes a difference.
It doesn't..
> Hm, it now was surprisingly hard for me to reproduce it. Surprising
> because when I wrote the bug report I was annoyed by it happening so
> often. It seems to happen only when there is an active selection,
> e.g. a part of the buffer marked by dragging with mouse-1. (I
> normally have transie
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-medium-r-*--*-120-*-*-*-*,*" to type FontSet
BTW: the above -*-helvetica-medium-r-*--*-120-*-*-*-* should have two more
"-*" to be complete. Maybe that was the problem.
> I final
"Jan D." <[EMAIL PROTECTED]> writes:
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-medium-r-*--*-120-*-*-*-*,*" to type FontSet
>
>
> I finally got time to change this. Now, the old font resource is used
> by default.
Good.
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-medium-r-*--*-120-*-*-*-*,*" to type FontSet
BTW: the above -*-helvetica-medium-r-*--*-120-*-*-*-* should have two
more
"-*" to be complete. Maybe that was the problem.
It might have been. I st
* Stefan Monnier (2005-04-01) writes:
>> If you have flyspell-mode enabled, click with mouse-2 on a highlighted
>> word not in the dictionary and choose "Save word". After that, text
>> currently in the kill ring will be yanked into the buffer.
>
>> This was probably introduced by changing mouse-
"Jan D." <[EMAIL PROTECTED]> writes:
>> Just some ordinary operations in Gnus, nothing particularly
>> challenging.
>>
>> (gdb) where
>> #0 0x002b47e2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
>> #1 0x003a2a0e in __lll_mutex_lock_wait () from /lib/tls/libc.so.6
>> #2 0x003392a2 in _L_mute
> If you have flyspell-mode enabled, click with mouse-2 on a highlighted
> word not in the dictionary and choose "Save word". After that, text
> currently in the kill ring will be yanked into the buffer.
> This was probably introduced by changing mouse-2 to down-mouse-2 in
> `flyspell-mode-map' b
Just some ordinary operations in Gnus, nothing particularly
challenging.
(gdb) where
#0 0x002b47e2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x003a2a0e in __lll_mutex_lock_wait () from /lib/tls/libc.so.6
#2 0x003392a2 in _L_mutex_lock_15166 () from /lib/tls/libc.so.6
#3 0x003efff4 in ?
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-medium-r-*--*-120-*-*-*-*,*" to type FontSet
I finally got time to change this. Now, the old font resource is used
by default. The fontset handling is only enabled if you specify a
fontset, e
> Cc: emacs-pretest-bug@gnu.org
> From: Reiner Steib <[EMAIL PROTECTED]>
> Date: Fri, 01 Apr 2005 13:21:02 +0200
>
> On Fri, Apr 01 2005, Eli Zaretskii wrote:
>
> >> From: Reiner Steib <[EMAIL PROTECTED]>
> [...]
> >> #0 abort () at [...]/emacs/src/emacs.c:456
> >> #1 0x00539245 in Fgar
If you have flyspell-mode enabled, click with mouse-2 on a highlighted
word not in the dictionary and choose "Save word". After that, text
currently in the kill ring will be yanked into the buffer.
This was probably introduced by changing mouse-2 to down-mouse-2 in
`flyspell-mode-map' because the
On Fri, Apr 01 2005, Eli Zaretskii wrote:
>> From: Reiner Steib <[EMAIL PROTECTED]>
[...]
>> #0 abort () at [...]/emacs/src/emacs.c:456
>> #1 0x00539245 in Fgarbage_collect ()
>> at [...]/emacs/src/alloc.c:4742
>> #2 0x0057a1d4 in Fbyte_code (bytestr=9727377, vector=Variable
Richard Stallman <[EMAIL PROTECTED]> writes:
> The use of custom-current-group seems like a bad practice to me.
> It is unreliable to make one defun depend on whatever was lying around
> from a previous defun in this way. It has the result that moving
> code from one place in a file to another ch
> There are two different arrows related to compilation and grep:
> one is displayed in the compilation buffer, and another indicates
> the line found by `next-error' in the source buffer.
>
> The latter can be displayed in any buffer and so should be
> added to overlay-arrow-variable-list to
[CC'd this msg again to the devel ML for help]
Hello,
> I made the following patch which seems to work better. WDYT?
>
> You changed the code quite a bit, so I can't quickly see what the
> user-level behavior is. Would you please describe what has changed
> at that level?
I redid the patch
Oops! here is the correct change log. Sorry!
2005-04-01 David Ponce <[EMAIL PROTECTED]>
* cus-edit.el (face): Derive from symbol widget. Display sample
of the current face on the fly.
(widget-face-sample-face-get, widget-face-notify): New functions.
(widget-face
> From: Reiner Steib <[EMAIL PROTECTED]>
> Date: Thu, 31 Mar 2005 21:48:03 +0200
>
> #0 abort () at [...]/emacs/src/emacs.c:456
> #1 0x00539245 in Fgarbage_collect ()
> at [...]/emacs/src/alloc.c:4742
> #2 0x0057a1d4 in Fbyte_code (bytestr=9727377, vector=Variable
> "vector
26 matches
Mail list logo