Re: emacs-unicode-2 fontset bug
In article <[EMAIL PROTECTED]>, Leon <[EMAIL PROTECTED]> writes: > I'm running Fedora 5. I have checked the emacs-unicode-2 branch to > make sure I also have the latest version. I've just installed the terminus fonts and the latest emacs-unicode-2 on Fedora 5, but I still can't reproduce the bug. Very strange. Aren't there anyone else who can reproduce that bug? --- Kenichi Handa [EMAIL PROTECTED] ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Segmentation fault in best_matching_font()
I made a change yesterday; does that fix this? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: forward-comment, C-M-a and C-M-e problems in bibtex-mode
Stefan Monnier <[EMAIL PROTECTED]> writes:
> >> >> >> Oh, and I forgot another problem: doing C-c C-c inside a comment
> >> >> >> throws a Wrong type argument: number-or-marker-p error.
> >>
> >> Hmmm... wrong type argument, you say?
> >>
> >> >> Given the context, you hopefully understand that "inside a comment" is
> >> >> a meaningless description of the circumstance.
> >> >> Please give a concrete example.
> >>
> >> > Create a new .bib file
> >> > Then type in it:
> >> > M-; blah blah C-c C-c
> >> > This is the original situation that I encountered.
> >> > But also the same thing happens if you type in a new file:
> >> > % blah blah C-c C-c
> >> > If you type in a new file:
> >> > @Comment {blah blah} C-c C-c
> >>
> >> > the error is "Search failed [snip a humongous regexp]"
> >>
> >> That's not a wrong type argument error any more. It's just complaining
that
> >> it can't find the BibTeX entry you're asking to format.
> >> The same happens without the "%" or the "@Comment".
>
> > Do you have some local changes?
>
> I was partly commenting on your bug-report, not just on the behavior I saw.
>
> > I still get the same errors with a freshly updated and bootstrapped
Emacs...
>
> Which error? The wrong type argument or the search failed?
Note "errors", so both of them.
> Does the patch below "help"?
It does, the wrong type argument error is replaced with a much nicer
"Not inside a bibtex entry" (but you probably knew that).
The "search failed" error is still present.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Segmentation fault in best_matching_font()
if (needs_overstrike) at xfaces.c:6681
shoud probably be if (best && needs_overstrike)
(gdb) bt full
#0 best_matching_font (f=0x865bd50, attrs=0x85805d0, fonts=0x8580550,
nfonts=1, width_ratio=2,
needs_overstrike=0xbfffdc68) at xfaces.c:6684
want_weight = XLFD_WEIGHT_MEDIUM
got_weight = 140138052
non_scalable_has_exact_height_p = 0
font_name = 0x85805d0 "\210"
best = (struct font_name *) 0x0
i = 0
pt = 157
specified = {5, 157, 5, 1, 140885328}
exact_p = 0
avgwidth = 200
#1 0x080bb330 in choose_face_font (f=0x865bd50, attrs=0x88a4730,
fontset=20, c=12,
needs_overstrike=0xbfffdc68) at xfaces.c:6910
pattern = 140138052
fonts = (struct font_name *) 0x8580550
nfonts = 0
width_ratio = 140138052
#2 0x080b3d83 in load_face_font (f=0x865bd50, face=0x88a46e8,
c=49152) at xfaces.c:1257
font_info = (struct font_info *) 0xc000
font_name = 0x88da6e8 "\201g2\b[8\215\bŠä2\bč\004"
needs_overstrike = 0
#3 0x080bbad3 in realize_face (cache=0x0, attrs=0x88da6e8, c=49152,
base_face=0x88da6a0,
former_face_id=140138052) at xfaces.c:7166
face = (struct face *) 0x88a46e8
#4 0x080b9a09 in lookup_face (f=0x865bd50, attr=0x88da6e8, c=49152,
base_face=0x88da6a0)
at xfaces.c:5687
cache = (struct face_cache *) 0x865c400
hash = 17221816
face = (struct face *) 0x0
#5 0x080d8f92 in face_for_char (f=0x865bd50, face=0x88da6a0, c=49152)
at fontset.c:548
fontset = 143501132
elt = 5
face_id = 143500960
...
In GNU Emacs 22.0.50.7 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2006-05-20 on wildebeest
X server distributor `The X.Org Foundation', version 11.0.60802000
configured using `configure '--prefix=/usr/local''
Important settings:
value of $LC_ALL: pl_PL
value of $LC_COLLATE: C
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: pl_PL
locale-coding-system: iso-latin-2
default-enable-multibyte-characters: t
Minor modes in effect:
display-time-mode: t
iswitchb-mode: t
show-paren-mode: t
tooltip-mode: t
auto-compression-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
unify-8859-on-encoding-mode: t
utf-translate-cjk-mode: t
column-number-mode: t
line-number-mode: t
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: forward-comment, C-M-a and C-M-e problems in bibtex-mode
>> >> >> Oh, and I forgot another problem: doing C-c C-c inside a comment
>> >> >> throws a Wrong type argument: number-or-marker-p error.
>>
>> Hmmm... wrong type argument, you say?
>>
>> >> Given the context, you hopefully understand that "inside a comment" is
>> >> a meaningless description of the circumstance.
>> >> Please give a concrete example.
>>
>> > Create a new .bib file
>> > Then type in it:
>> > M-; blah blah C-c C-c
>> > This is the original situation that I encountered.
>> > But also the same thing happens if you type in a new file:
>> > % blah blah C-c C-c
>> > If you type in a new file:
>> > @Comment {blah blah} C-c C-c
>>
>> > the error is "Search failed [snip a humongous regexp]"
>>
>> That's not a wrong type argument error any more. It's just complaining that
>> it can't find the BibTeX entry you're asking to format.
>> The same happens without the "%" or the "@Comment".
> Do you have some local changes?
I was partly commenting on your bug-report, not just on the behavior I saw.
> I still get the same errors with a freshly updated and bootstrapped Emacs...
Which error? The wrong type argument or the search failed?
Does the patch below "help"?
Stefan
*** bibtex.el 22 May 2006 13:59:55 -0400 1.118
--- bibtex.el 22 May 2006 14:32:33 -0400
***
*** 3879,3885
(interactive "P")
(let ((case-fold-search t)
(start (bibtex-beginning-of-entry))
! (_ (looking-at bibtex-any-entry-maybe-empty-head))
(entry-type (bibtex-type-in-head))
(key (bibtex-key-in-head)))
;; formatting
--- 3879,3886
(interactive "P")
(let ((case-fold-search t)
(start (bibtex-beginning-of-entry))
! (_ (or (looking-at bibtex-any-entry-maybe-empty-head)
! (error "Not inside a BibTeX entry")))
(entry-type (bibtex-type-in-head))
(key (bibtex-key-in-head)))
;; formatting
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: completing include files with complete.el not working (and also a read-file-name-function issue)
> Do emacs -q > M-x partial-completion-mode RET > C-x C-f this will print "No Match" > in emacs-21.4 it used to give as completions the files in /usr/include/sys/ Thanks. It seems the patch below fixes it, Stefan --- complete.el 24 Apr 2006 09:04:07 -0400 1.52 +++ complete.el 22 May 2006 14:06:49 -0400 @@ -369,7 +369,7 @@ (str (buffer-substring beg end)) (incname (and filename (string-match "<\\([^\"<>]*\\)>?$" str))) (ambig nil) -basestr +basestr origstr env-on regex p offset @@ -415,7 +415,7 @@ (file-name-nondirectory dir)) "*/" file)) (setq dir (file-name-directory dir))) - (setq str (concat dir file + (setq origstr str str (concat dir file ;; Look for wildcard expansions in directory name (and filename @@ -443,7 +443,14 @@ (setq str (concat dir (file-name-nondirectory str))) (insert str) (setq end (+ beg (length str) - (setq filename nil table nil pred nil + (if origstr + ;; If the wildcards were introduced by us, it's possible + ;; that read-file-name-internal (especially our + ;; PC-include-file advice) can still find matches for the + ;; original string even if we couldn't, so remove the + ;; added wildcards. + (setq str origstr) +(setq filename nil table nil pred nil) ;; Strip directory name if appropriate (if filename ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: forward-comment, C-M-a and C-M-e problems in bibtex-mode
Stefan Monnier <[EMAIL PROTECTED]> writes:
> >> >> Oh, and I forgot another problem: doing C-c C-c inside a comment
> >> >> throws a Wrong type argument: number-or-marker-p error.
>
> Hmmm... wrong type argument, you say?
>
> >> Given the context, you hopefully understand that "inside a comment" is
> >> a meaningless description of the circumstance.
> >> Please give a concrete example.
>
> > Create a new .bib file
> > Then type in it:
> > M-; blah blah C-c C-c
> > This is the original situation that I encountered.
> > But also the same thing happens if you type in a new file:
> > % blah blah C-c C-c
> > If you type in a new file:
> > @Comment {blah blah} C-c C-c
>
> > the error is "Search failed [snip a humongous regexp]"
>
> That's not a wrong type argument error any more. It's just complaining that
> it can't find the BibTeX entry you're asking to format.
> The same happens without the "%" or the "@Comment".
Do you have some local changes?
I still get the same errors with a freshly updated and bootstrapped
emacs...
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: forward-comment, C-M-a and C-M-e problems in bibtex-mode
>> >> Oh, and I forgot another problem: doing C-c C-c inside a comment
>> >> throws a Wrong type argument: number-or-marker-p error.
Hmmm... wrong type argument, you say?
>> Given the context, you hopefully understand that "inside a comment" is
>> a meaningless description of the circumstance.
>> Please give a concrete example.
> Create a new .bib file
> Then type in it:
> M-; blah blah C-c C-c
> This is the original situation that I encountered.
> But also the same thing happens if you type in a new file:
> % blah blah C-c C-c
> If you type in a new file:
> @Comment {blah blah} C-c C-c
> the error is "Search failed [snip a humongous regexp]"
That's not a wrong type argument error any more. It's just complaining that
it can't find the BibTeX entry you're asking to format.
The same happens without the "%" or the "@Comment".
Stefan
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs-unicode-2 fontset bug
Kenichi Handa <[EMAIL PROTECTED]> writes: > In article <[EMAIL PROTECTED]>, Leon <[EMAIL PROTECTED]> writes: > >> After many trials, I think I found another bug of emacs-unicode-2 >> branch. I have the following settings in ~/.Xresources: > >> ,[ ~/.Xresources ] >> | Emacs.Fontset-0: -*-*-medium-r-*-*-16-*-*-*-*-*-fontset-unicode,\ >> | ascii:-*-terminus-medium-r-*-*-16-*-*-*-*-iso8859-1,\ >> | mule-unicode-2500-33ff:-gnu-unifont-medium-r-*-*-16-*-*-*-*-*-iso10646-1,\ >> | mule-unicode-e000-:-gnu-unifont-medium-r-*-*-16-*-*-*-*-*-iso10646-1,\ >> | mule-unicode-0100-24ff:-gnu-unifont-medium-r-*-*-16-*-*-*-*-*-iso10646-1 >> | Emacs.Font: fontset-unicode >> ` > >> In emacs-unicode-2, the font for ascii will be a font that matches >> "-*-*-medium-r-*-*-16-*-*-*-*-*" instead of >> "-*-terminus-medium-r-*-*-16-*-*-*-*-iso8859-1". > >> However, emacs 21.3 will correctly pick up the font matches >> "-*-terminus-medium-r-*-*-16-*-*-*-*-iso8859-1". > > I can't reproduce that bug here (Debian+XFree86) with the > latest emacs-unicode-2. With the above setting, Emacs > starts up using a terminus font, and C-u C-x = on various > characters tells that terminus fonts are being used. > > Have you tested it by starting Emacs with "-q"? > > What is the output of M-x describe-face RET default RET? > > --- > Kenichi Handa > [EMAIL PROTECTED] I'm running Fedora 5. I have checked the emacs-unicode-2 branch to make sure I also have the latest version. Start emacs with -q option: Emacs 23 ,[ M-x describe-face RET default RET ] | Face: default (customize this face) | Documentation: Basic default face. | Defined in `faces.el'. | | Family: etl-fixed | Width: normal | Height: 121 | Weight: normal | Slant: normal | Foreground: black | Background: white | Underline: nil | Overline: nil | Strike-through: nil |Box: nil |Inverse: nil |Stipple: nil | Font: -ETL-Fixed-Medium-R-Normal--16-160-72-72-C-80-ISO8859-1 |Fontset: -*-*-medium-r-*-*-16-*-*-*-*-*-fontset-unicode |Inherit: unspecified ` In emacs 21.3: ,[ M-x describe-face RET default RET ] | Family: xos4-terminus | Width: normal | Height: 121 | Weight: normal | Slant: normal | Foreground: black | Background: white | Underline: nil |Overline: nil | Strike-through: nil | Box: nil | Inverse: nil | Stipple: nil | Font or fontset: fontset-unicode | Inherit: unspecified | | Documentation: | | Basic default face. | | You can customize this face. ` -- Leon ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
