all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* 23.0.60; peculiar error: "invalid font property", (:weight . r)
@ 2007-12-19 14:58 Stephen Berman
  2007-12-19 15:24 ` Jason Rumney
  2007-12-20  0:54 ` Kenichi Handa
  0 siblings, 2 replies; 22+ messages in thread
From: Stephen Berman @ 2007-12-19 14:58 UTC (permalink / raw)
  To: emacs-devel

I just did an update from the unicode-2 branch and built with make
bootstrap successfully.  But when I start Emacs with -Q, no frame opens
and the shell returns this message: peculiar error: "invalid font
property", (:weight . r)

That appears to come from Fsignal in font.c, so I ran under gdb and set
a breakpoint there.  Here's the backtrace:

Breakpoint 3, Fsignal (error_symbol=137906873, data=147293965) at eval.c:1622
1622      register struct handler *allhandlers = handlerlist;
(gdb) bt full
#0  Fsignal (error_symbol=137906873, data=147293965) at eval.c:1622
        allhandlers = (struct handler *) 0x83538c9
        conditions = <value optimized out>
        string = <value optimized out>
        real_error_symbol = <value optimized out>
        bp = <value optimized out>
#1  0x081bae58 in font_prop_validate (spec=138760476) at font.c:517
        elt = <value optimized out>
        i = <value optimized out>
        prop = <value optimized out>
        val = 137749905
        extra = <value optimized out>
#2  0x081735b0 in Ffuncall (nargs=11, args=0xbfbfaaa0) at eval.c:3005
        fun = <value optimized out>
        original_fun = 137949513
        funcar = <value optimized out>
        numargs = 10
        val = <value optimized out>
        backtrace = {
  next = 0xbfbfab48,
  function = 0xbfbfaaa0,
  args = 0xbfbfaaa4,
  nargs = 10,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
        internal_args = (Lisp_Object *) 0xbfbfaaa4
        i = <value optimized out>
#3  0x08174a88 in Fapply (nargs=2, args=0xbfbfab88) at eval.c:2512
        ret_ungc_val = 137906873
        i = <value optimized out>
        numargs = <value optimized out>
        spread_arg = 137705673
        funcall_args = (Lisp_Object *) 0xbfbfaaa0
        fun = <value optimized out>
#4  0x081735b0 in Ffuncall (nargs=3, args=0xbfbfab84) at eval.c:3005
        fun = <value optimized out>
        original_fun = 137845937
        funcar = <value optimized out>
        numargs = 2
        val = <value optimized out>
---Type <return> to continue, or q <return> to quit---
        backtrace = {
  next = 0xbfbfac98,
  function = 0xbfbfab84,
  args = 0xbfbfab88,
  nargs = 2,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
        internal_args = (Lisp_Object *) 0xbfbfab88
        i = <value optimized out>
#5  0x0819cd1c in Fbyte_code (bytestr=136855419, vector=136855436,
    maxdepth=<value optimized out>) at bytecode.c:679
        v1 = <value optimized out>
        v2 = <value optimized out>
        op = 147294141
        vectorp = (Lisp_Object *) 0x8283f90
        stack = {
  pc = 0x82a150f "\240\210.\006*\016\036A\211\026\036\204V",
  top = 0xbfbfab8c,
  bottom = 0xbfbfab80,
  byte_string = 136855419,
  byte_string_start = 0x82a1355 "\b\tH\b\nH\b\vH\b\fH\b\rH\b\016\025H\036\026\036\027\036\030\036\031\036\032\036\033\016\032\203*",
  constants = 136855436,
  next = 0xbfbfad20
}
        top = (Lisp_Object *) 0xbfbfab84
        result = <value optimized out>
#6  0x08172ea6 in funcall_lambda (fun=136855372, nargs=2, arg_vector=0xbfbfacd4)
    at eval.c:3211
        val = <value optimized out>
        syms_left = <value optimized out>
        next = <value optimized out>
        i = 2
        optional = 0
        rest = 0
#7  0x081732b1 in Ffuncall (nargs=3, args=0xbfbfacd0) at eval.c:3081
        fun = 136855372
        original_fun = 147810337
        funcar = <value optimized out>
        numargs = 2
---Type <return> to continue, or q <return> to quit---
        val = <value optimized out>
        backtrace = {
  next = 0xbfbfadd8,
  function = 0xbfbfacd0,
  args = 0xbfbfacd4,
  nargs = 2,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
        internal_args = (Lisp_Object *) 0xbfbfacd4
        i = <value optimized out>
#8  0x0819cd1c in Fbyte_code (bytestr=136856579, vector=136856596,
    maxdepth=<value optimized out>) at bytecode.c:679
        v1 = <value optimized out>
        v2 = <value optimized out>
        op = 147294141
        vectorp = (Lisp_Object *) 0x8284418
        stack = {
  pc = 0x82a1124 "\021\327\r\t\237\".\006\207",
  top = 0xbfbfacd8,
  bottom = 0xbfbfacd0,
  byte_string = 136856579,
  byte_string_start = 0x82a109e "\306\307\b\"\204\f",
  constants = 136856596,
  next = 0xbfbfae60
}
        top = (Lisp_Object *) 0xbfbfacd0
        result = <value optimized out>
#9  0x08172ea6 in funcall_lambda (fun=136856516, nargs=3, arg_vector=0xbfbfae14)
    at eval.c:3211
        val = <value optimized out>
        syms_left = <value optimized out>
        next = <value optimized out>
        i = 3
        optional = 1
        rest = 0
#10 0x081732b1 in Ffuncall (nargs=4, args=0xbfbfae10) at eval.c:3081
        fun = 136856516
        original_fun = 147810625
        funcar = <value optimized out>
        numargs = 3
---Type <return> to continue, or q <return> to quit---
        val = <value optimized out>
        backtrace = {
  next = 0xbfbfaf18,
  function = 0xbfbfae10,
  args = 0xbfbfae14,
  nargs = 3,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
        internal_args = (Lisp_Object *) 0xbfbfae14
        i = <value optimized out>
#11 0x0819cd1c in Fbyte_code (bytestr=136857155, vector=136857172,
    maxdepth=<value optimized out>) at bytecode.c:679
        v1 = <value optimized out>
        v2 = <value optimized out>
        op = 147294141
        vectorp = (Lisp_Object *) 0x8284658
        stack = {
  pc = 0x82a0f0f "\210\tT\021\202\004",
  top = 0xbfbfae1c,
  bottom = 0xbfbfae10,
  byte_string = 136857155,
  byte_string_start = 0x82a0ef7 "\302\303\030\031\304\305\306\t\"\305\307\t\"\"\211\020\205\037",
  constants = 136857172,
  next = 0xbfbfafa0
}
        top = (Lisp_Object *) 0xbfbfae10
        result = <value optimized out>
#12 0x08172ea6 in funcall_lambda (fun=136857132, nargs=0, arg_vector=0xbfbfaf54)
    at eval.c:3211
        val = <value optimized out>
        syms_left = <value optimized out>
        next = <value optimized out>
        i = 0
        optional = 1
        rest = 0
#13 0x081732b1 in Ffuncall (nargs=1, args=0xbfbfaf50) at eval.c:3081
        fun = 136857132
        original_fun = 147810817
        funcar = <value optimized out>
---Type <return> to continue, or q <return> to quit---
        numargs = 0
        val = <value optimized out>
        backtrace = {
  next = 0xbfbfb058,
  function = 0xbfbfaf50,
  args = 0xbfbfaf54,
  nargs = 0,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
        internal_args = (Lisp_Object *) 0xbfbfaf54
        i = <value optimized out>
#14 0x0819cd1c in Fbyte_code (bytestr=136879211, vector=136879228,
    maxdepth=<value optimized out>) at bytecode.c:679
        v1 = <value optimized out>
        v2 = <value optimized out>
        op = 147294141
        vectorp = (Lisp_Object *) 0x8289c80
        stack = {
  pc = 0x829e4bf "\210\327\330\331\"\332\232\203W",
  top = 0xbfbfaf50,
  bottom = 0xbfbfaf50,
  byte_string = 136879211,
  byte_string_start = 0x829e477 "\b;\204\034",
  constants = 136879228,
  next = 0xbfbfb0d0
}
        top = (Lisp_Object *) 0xbfbfaf50
        result = <value optimized out>
#15 0x08172ea6 in funcall_lambda (fun=136879180, nargs=0, arg_vector=0xbfbfb094)
    at eval.c:3211
        val = <value optimized out>
        syms_left = <value optimized out>
        next = <value optimized out>
        i = 0
        optional = 0
        rest = 0
#16 0x081732b1 in Ffuncall (nargs=1, args=0xbfbfb090) at eval.c:3081
        fun = 136879180
        original_fun = 147822241
        funcar = <value optimized out>
---Type <return> to continue, or q <return> to quit---
        numargs = 0
        val = <value optimized out>
        backtrace = {
  next = 0xbfbfb150,
  function = 0xbfbfb090,
  args = 0xbfbfb094,
  nargs = 0,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
        internal_args = (Lisp_Object *) 0xbfbfb094
        i = <value optimized out>
#17 0x0819cd1c in Fbyte_code (bytestr=136442355, vector=136442380,
    maxdepth=<value optimized out>) at bytecode.c:679
        v1 = <value optimized out>
        v2 = <value optimized out>
        op = 147294141
        vectorp = (Lisp_Object *) 0x821f210
        stack = {
  pc = 0x82e0ba8 "\210\305\207",
  top = 0xbfbfb090,
  bottom = 0xbfbfb090,
  byte_string = 136442355,
  byte_string_start = 0x82e0b75 "\b\2044",
  constants = 136442380,
  next = 0xbfbfb2e0
}
        top = (Lisp_Object *) 0xbfbfb090
        result = <value optimized out>
#18 0x08172a2e in Feval (form=136442341) at eval.c:2361
        numargs = <value optimized out>
        argvals = {136442355, 136442380, 32, 137297892, -1077956256, 48,
  -1077956152, 135908556}
        args_left = 137705673
        i = 3
        fun = <value optimized out>
        val = <value optimized out>
        original_fun = 137868297
        original_args = 136442349
        funcar = <value optimized out>
        backtrace = {
---Type <return> to continue, or q <return> to quit---
  next = 0xbfbfb398,
  function = 0xbfbfb168,
  args = 0xbfbfb130,
  nargs = 3,
  evalargs = 1 '\001',
  debug_on_exit = 0 '\0'
}
#19 0x08174ebf in internal_lisp_condition_case (var=137749905,
    bodyform=136442341, handlers=136442477) at eval.c:1438
        val = <value optimized out>
        c = {
  tag = 137705673,
  val = 137705673,
  next = 0xbfbfb56c,
  gcpro = 0x0,
  jmp = {{
      __jmpbuf = {137705673, -1077955952, 81, -1077955976, 520638012,
        1324842323},
      __mask_was_saved = 0,
      __saved_mask = {
        __val = {1, 3217011208, 135737023, 64, 137705673, 32, 3217011348,
          136319572, 4, 138219008, 4, 1, 1, 0, 136319572, 142821969, 1,
          3217011320, 135738033, 3217011608, 3217011240, 3217011184, 3, 1,
          136353309, 137868297, 136353288, 136353293, 138002688, 142821968,
          137832370, 137832368}
      }
    }},
  backlist = 0xbfbfb398,
  handlerlist = 0xbfbfb634,
  lisp_eval_depth = 2,
  pdlcount = 4,
  poll_suppress_count = 1,
  interrupt_input_blocked = 0,
  byte_stack = 0xbfbfb2e0
}
        h = {
  handler = 136442477,
  var = 137749905,
  chosen_clause = 137705697,
  tag = 0xbfbfb198,
  next = 0xbfbfb634
---Type <return> to continue, or q <return> to quit---
}
#20 0x0819d660 in Fbyte_code (bytestr=136441235, vector=136441252,
    maxdepth=<value optimized out>) at bytecode.c:869
        handlers = <value optimized out>
        body = 147294141
        op = 0
        vectorp = (Lisp_Object *) 0x821eda8
        stack = {
  pc = 0x82e0c3a "\210\332\314!\210\333\334\016B\335 #\314\036C\211\036D\204|",
  top = 0xbfbfb290,
  bottom = 0xbfbfb290,
  byte_string = 136441235,
  byte_string_start = 0x82e0bdf "\b\021\306\307!\210\306\310!\210\306\311!\210\312\313!\211\032\314=\2046",
  constants = 136441252,
  next = 0xbfbfb420
}
        top = (Lisp_Object *) 0xbfbfb290
        result = <value optimized out>
#21 0x08172ea6 in funcall_lambda (fun=136441212, nargs=0, arg_vector=0xbfbfb3d4)
    at eval.c:3211
        val = <value optimized out>
        syms_left = <value optimized out>
        next = <value optimized out>
        i = 0
        optional = 0
        rest = 0
#22 0x081732b1 in Ffuncall (nargs=1, args=0xbfbfb3d0) at eval.c:3081
        fun = 136441212
        original_fun = 142904217
        funcar = <value optimized out>
        numargs = 0
        val = <value optimized out>
        backtrace = {
  next = 0xbfbfb520,
  function = 0xbfbfb3d0,
  args = 0xbfbfb3d4,
  nargs = 0,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
---Type <return> to continue, or q <return> to quit---
        internal_args = (Lisp_Object *) 0xbfbfb3d4
        i = <value optimized out>
#23 0x0819cd1c in Fbyte_code (bytestr=136437931, vector=136437948,
    maxdepth=<value optimized out>) at bytecode.c:679
        v1 = <value optimized out>
        v2 = <value optimized out>
        op = 147294141
        vectorp = (Lisp_Object *) 0x821e0c0
        stack = {
  pc = 0x82e19d4 "\210*\340\341\342\"\210\343\320\344\"\211\036$;\203\245",
  top = 0xbfbfb3d0,
  bottom = 0xbfbfb3d0,
  byte_string = 136437931,
  byte_string_start = 0x82e194a "\b\203\b",
  constants = 136437948,
  next = 0x0
}
        top = (Lisp_Object *) 0xbfbfb3d0
        result = <value optimized out>
#24 0x08172ea6 in funcall_lambda (fun=136437908, nargs=0, arg_vector=0xbfbfb4a0)
    at eval.c:3211
        val = <value optimized out>
        syms_left = <value optimized out>
        next = <value optimized out>
        i = 0
        optional = -1220110048
        rest = 2
#25 0x081730a0 in apply_lambda (fun=136437908, args=137705673, eval_flag=1)
    at eval.c:3135
        args_left = 136437904
        arg_vector = (Lisp_Object *) 0x0
        i = 0
        tem = 137705673
#26 0x08172764 in Feval (form=138255565) at eval.c:2415
        fun = 0
        val = <value optimized out>
        original_fun = 143071393
        original_args = 137705673
        funcar = 147294141
        backtrace = {
  next = 0x0,
---Type <return> to continue, or q <return> to quit---
  function = 0xbfbfb538,
  args = 0xbfbfb4a0,
  nargs = 0,
  evalargs = 0 '\0',
  debug_on_exit = 0 '\0'
}
#27 0x081100c3 in top_level_2 () at keyboard.c:1390
No locals.
#28 0x08171e00 in internal_condition_case (bfun=0x81100b0 <top_level_2>,
    handlers=137749905, hfun=0x81138f0 <cmd_error>) at eval.c:1493
        val = <value optimized out>
        c = {
  tag = 137705673,
  val = 137705673,
  next = 0xbfbfb680,
  gcpro = 0x0,
  jmp = {{
      __jmpbuf = {0, 138219024, 138219008, -1077955000, 520195644, 1313918291},
      __mask_was_saved = 0,
      __saved_mask = {
        __val = {1, 3077930872, 3086770164, 3068852444, 3217011872, 3217011924,
          3086698543, 3217012232, 3217012288, 3086771824, 134543643, 2822930839,
          0, 0, 2, 3086717961, 134542977, 3217012224, 3217012512, 4294967295,
          3217012360, 135403747, 3217012512, 3217012224, 128, 3074841216,
          3076067328, 0, 4294967295, 3086770164, 3086771824, 134523352}
      }
    }},
  backlist = 0x0,
  handlerlist = 0x0,
  lisp_eval_depth = 0,
  pdlcount = 2,
  poll_suppress_count = 1,
  interrupt_input_blocked = 0,
  byte_stack = 0x0
}
        h = {
  handler = 137749905,
  var = 137705673,
  chosen_clause = 136172684,
  tag = 0xbfbfb56c,
  next = 0x0
---Type <return> to continue, or q <return> to quit---
}
#29 0x08112d10 in top_level_1 () at keyboard.c:1398
No locals.
#30 0x08171eda in internal_catch (tag=137744753, func=0x8112ce0 <top_level_1>,
    arg=137705673) at eval.c:1229
        c = {
  tag = 137744753,
  val = 137705673,
  next = 0x0,
  gcpro = 0x0,
  jmp = {{
      __jmpbuf = {0, 138219024, 138219008, -1077954744, 520597052, 1314313555},
      __mask_was_saved = 0,
      __saved_mask = {
        __val = {0, 145176976, 192, 3076055408, 0, 176, 22, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 3080344625, 137837412, 137837408, 3076055408, 137932906,
          137932904, 137935264, 3217012536, 135674421, 137935265, 137932906,
          137705673, 137731520, 3068680400, 138656040, 137705697}
      }
    }},
  backlist = 0x0,
  handlerlist = 0x0,
  lisp_eval_depth = 0,
  pdlcount = 2,
  poll_suppress_count = 1,
  interrupt_input_blocked = 0,
  byte_stack = 0x0
}
#31 0x08113739 in command_loop () at keyboard.c:1353
No locals.
#32 0x08113abb in recursive_edit_1 () at keyboard.c:969
        val = <value optimized out>
#33 0x08113bf1 in Frecursive_edit () at keyboard.c:1031
        buffer = 137705673
#34 0x081092d2 in main (argc=2, argv=0xbfbfbb54) at emacs.c:1808
        displayname = 0x0
        count_before = <value optimized out>
        dummy = -1077953848
        stack_bottom_variable = 8 '\b'
        do_initial_setlocale = 1
        skip_args = 0
---Type <return> to continue, or q <return> to quit---
        rlim = {
  rlim_cur = 8388608,
  rlim_max = 18446744073709551615
}
        no_loadup = 0
        junk = 0x0

Lisp Backtrace:
"font-spec" (0xbfbfaaa4)
"apply" (0xbfbfab88)
"x-complement-fontset-spec" (0xbfbfacd4)
"create-fontset-from-fontset-spec" (0xbfbfae14)
"create-fontset-from-x-resource" (0xbfbfaf54)
"x-initialize-window-system" (0xbfbfb094)
"byte-code" (0xbfbfb130)
"command-line" (0xbfbfb3d4)
"normal-top-level" (0xbfbfb4a0)



In GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.0)
 of 2007-12-19 on escher
configured using `configure  '--enable-font-backend''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  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: en_US.UTF-8
  value of $XMODIFIERS: @im=local
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-19 14:58 23.0.60; peculiar error: "invalid font property", (:weight . r) Stephen Berman
@ 2007-12-19 15:24 ` Jason Rumney
  2007-12-19 15:32   ` Stephen Berman
  2007-12-20  0:58   ` Kenichi Handa
  2007-12-20  0:54 ` Kenichi Handa
  1 sibling, 2 replies; 22+ messages in thread
From: Jason Rumney @ 2007-12-19 15:24 UTC (permalink / raw)
  To: Stephen Berman; +Cc: emacs-devel

Stephen Berman wrote:
> I just did an update from the unicode-2 branch and built with make
> bootstrap successfully.  But when I start Emacs with -Q, no frame opens
> and the shell returns this message: peculiar error: "invalid font
> property", (:weight . r)
>   

> Lisp Backtrace:
> "font-spec" (0xbfbfaaa4)
> "apply" (0xbfbfab88)
> "x-complement-fontset-spec" (0xbfbfacd4)
> "create-fontset-from-fontset-spec" (0xbfbfae14)
> "create-fontset-from-x-resource" (0xbfbfaf54)
>   

I'm sure there is a bug there, but shouldn't X resources be ignored when
using -Q?

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-19 15:24 ` Jason Rumney
@ 2007-12-19 15:32   ` Stephen Berman
  2007-12-20  0:58   ` Kenichi Handa
  1 sibling, 0 replies; 22+ messages in thread
From: Stephen Berman @ 2007-12-19 15:32 UTC (permalink / raw)
  To: emacs-devel

On Wed, 19 Dec 2007 15:24:55 +0000 Jason Rumney <jasonr@gnu.org> wrote:

> Stephen Berman wrote:
>> I just did an update from the unicode-2 branch and built with make
>> bootstrap successfully.  But when I start Emacs with -Q, no frame opens
>> and the shell returns this message: peculiar error: "invalid font
>> property", (:weight . r)
>>   
>
>> Lisp Backtrace:
>> "font-spec" (0xbfbfaaa4)
>> "apply" (0xbfbfab88)
>> "x-complement-fontset-spec" (0xbfbfacd4)
>> "create-fontset-from-fontset-spec" (0xbfbfae14)
>> "create-fontset-from-x-resource" (0xbfbfaf54)
>>   
>
> I'm sure there is a bug there, but shouldn't X resources be ignored when
> using -Q?

I also get the same message and backtrace when I invoke this Emacs
without -Q. 

Steve Berman

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-19 14:58 23.0.60; peculiar error: "invalid font property", (:weight . r) Stephen Berman
  2007-12-19 15:24 ` Jason Rumney
@ 2007-12-20  0:54 ` Kenichi Handa
  2007-12-20 10:29   ` Stephen Berman
  2007-12-20 10:54   ` 23.0.60; peculiar error: "invalid font property", (:weight . r) KOBAYASHI Yasuhiro
  1 sibling, 2 replies; 22+ messages in thread
From: Kenichi Handa @ 2007-12-20  0:54 UTC (permalink / raw)
  To: Stephen Berman; +Cc: emacs-devel

In article <874peeu3yd.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:

> I just did an update from the unicode-2 branch and built with make
> bootstrap successfully.  But when I start Emacs with -Q, no frame opens
> and the shell returns this message: peculiar error: "invalid font
> property", (:weight . r)

It seems that the parsing of XLFD failed.

[...]
> Lisp Backtrace:
> "font-spec" (0xbfbfaaa4)
> "apply" (0xbfbfab88)
> "x-complement-fontset-spec" (0xbfbfacd4)
> "create-fontset-from-fontset-spec" (0xbfbfae14)
> "create-fontset-from-x-resource" (0xbfbfaf54)

Please show me how you set X resource for fontsets.

---
Kenichi Handa
handa@ni.aist.go.jp

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-19 15:24 ` Jason Rumney
  2007-12-19 15:32   ` Stephen Berman
@ 2007-12-20  0:58   ` Kenichi Handa
  1 sibling, 0 replies; 22+ messages in thread
From: Kenichi Handa @ 2007-12-20  0:58 UTC (permalink / raw)
  To: Jason Rumney; +Cc: Stephen.Berman, emacs-devel

In article <476937C7.3070905@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:

> Stephen Berman wrote:
> > I just did an update from the unicode-2 branch and built with make
> > bootstrap successfully.  But when I start Emacs with -Q, no frame opens
> > and the shell returns this message: peculiar error: "invalid font
> > property", (:weight . r)
> >   

> > Lisp Backtrace:
> > "font-spec" (0xbfbfaaa4)
> > "apply" (0xbfbfab88)
> > "x-complement-fontset-spec" (0xbfbfacd4)
> > "create-fontset-from-fontset-spec" (0xbfbfae14)
> > "create-fontset-from-x-resource" (0xbfbfaf54)
> >   

> I'm sure there is a bug there, but shouldn't X resources be ignored when
> using -Q?

It seems that several X resources (e.g. ReverseVideo) are
not ignored even with -Q.  See the function
x-initialize-window-system of lisp/term/x-win.el.

---
Kenichi Handa
handa@ni.aist.go.jp

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20  0:54 ` Kenichi Handa
@ 2007-12-20 10:29   ` Stephen Berman
  2007-12-20 11:21     ` Andreas Schwab
  2007-12-20 10:54   ` 23.0.60; peculiar error: "invalid font property", (:weight . r) KOBAYASHI Yasuhiro
  1 sibling, 1 reply; 22+ messages in thread
From: Stephen Berman @ 2007-12-20 10:29 UTC (permalink / raw)
  To: emacs-devel

On Thu, 20 Dec 2007 09:54:07 +0900 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <874peeu3yd.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> I just did an update from the unicode-2 branch and built with make
>> bootstrap successfully.  But when I start Emacs with -Q, no frame opens
>> and the shell returns this message: peculiar error: "invalid font
>> property", (:weight . r)
>
> It seems that the parsing of XLFD failed.
>
> [...]
>> Lisp Backtrace:
>> "font-spec" (0xbfbfaaa4)
>> "apply" (0xbfbfab88)
>> "x-complement-fontset-spec" (0xbfbfacd4)
>> "create-fontset-from-fontset-spec" (0xbfbfae14)
>> "create-fontset-from-x-resource" (0xbfbfaf54)
>
> Please show me how you set X resource for fontsets.

I don't have set X resources in my home directory.  I'm running KDE
using the gtk-qt engine for GTK apps, and in my personal settings for
this engine I have the option "Use my KDE fonts in GTK applications"
set, but I'm afraid I don't know how they are set.  As a test I created
~/.Xresources with a setting for Emacs.font, ran xrdb on it and then
invoked unicode Emacs, but it still just returned the peculiar error
message (Emacs from CVS trunk did use that font, so I know it is valid).
Can you tell me what I should do to make sure a certain font is set for
unicode Emacs from outside of Emacs?

Steve Berman

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20  0:54 ` Kenichi Handa
  2007-12-20 10:29   ` Stephen Berman
@ 2007-12-20 10:54   ` KOBAYASHI Yasuhiro
  2007-12-20 12:42     ` Kenichi Handa
  1 sibling, 1 reply; 22+ messages in thread
From: KOBAYASHI Yasuhiro @ 2007-12-20 10:54 UTC (permalink / raw)
  To: Kenichi Handa; +Cc: emacs-devel

In message Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
 on Thu, 20 Dec 2007 09:54:07 +0900
 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <874peeu3yd.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:

> > I just did an update from the unicode-2 branch and built with make
> > bootstrap successfully.  But when I start Emacs with -Q, no frame opens
> > and the shell returns this message: peculiar error: "invalid font
> > property", (:weight . r)

I also see the same error message on
GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600).

-- Msg in minibuffer --
"peculiar error: "invalid font property", (:weight . arial)"
--

And I get the other message with --disable-font-backend.

-- Msg in minibuffer --
"Font `fontset-test' is not defined"
--

.emacs.el is the following:
-------->8-------->8-------
(create-fontset-from-fontset-spec
 "-*-arial-normal-r-*-*-12-*-*-*-c-*-fontset-test,
 latin-iso8859-1:-*-Arial-*-*-*-*-*-*-*-*-*-*-iso8859-1" t)

(setq default-frame-alist
      (append '((font . "fontset-test"))
              default-frame-alist))
-------->8-------->8-------

-- 
KOBAYASHI Yasuhiro <kobayays@gmail.com>

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20 10:29   ` Stephen Berman
@ 2007-12-20 11:21     ` Andreas Schwab
  2007-12-20 14:14       ` Stephen Berman
  0 siblings, 1 reply; 22+ messages in thread
From: Andreas Schwab @ 2007-12-20 11:21 UTC (permalink / raw)
  To: Stephen Berman; +Cc: emacs-devel

Stephen Berman <Stephen.Berman@gmx.net> writes:

> I don't have set X resources in my home directory.  I'm running KDE
> using the gtk-qt engine for GTK apps, and in my personal settings for
> this engine I have the option "Use my KDE fonts in GTK applications"
> set, but I'm afraid I don't know how they are set.

xrdb -q will list them.

> As a test I created ~/.Xresources with a setting for Emacs.font, ran
> xrdb on it and then invoked unicode Emacs, but it still just returned
> the peculiar error message (Emacs from CVS trunk did use that font, so
> I know it is valid).

There are also the app-defaults, probably in
/usr/share/X11/app-defaults/Emacs.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20 10:54   ` 23.0.60; peculiar error: "invalid font property", (:weight . r) KOBAYASHI Yasuhiro
@ 2007-12-20 12:42     ` Kenichi Handa
  2007-12-20 14:14       ` Stephen Berman
  2007-12-21 16:27       ` KOBAYASHI Yasuhiro
  0 siblings, 2 replies; 22+ messages in thread
From: Kenichi Handa @ 2007-12-20 12:42 UTC (permalink / raw)
  To: KOBAYASHI Yasuhiro; +Cc: Stephen.Berman, emacs-devel

In article <uwsr94ovx.fsf@otsukakj.co.jp>, KOBAYASHI Yasuhiro <kobayays@gmail.com> writes:

> -- Msg in minibuffer --
> "peculiar error: "invalid font property", (:weight . arial)"
> --

Ah, I found what's wrong.  I've just installed a fix.

Stephen, I think you problem was caused by the same bug.

Please try again with the latest code.

---
Kenichi Handa
handa@ni.aist.go.jp

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20 11:21     ` Andreas Schwab
@ 2007-12-20 14:14       ` Stephen Berman
  2007-12-21  0:47         ` Kenichi Handa
  0 siblings, 1 reply; 22+ messages in thread
From: Stephen Berman @ 2007-12-20 14:14 UTC (permalink / raw)
  To: emacs-devel

On Thu, 20 Dec 2007 12:21:22 +0100 Andreas Schwab <schwab@suse.de> wrote:

> Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> I don't have set X resources in my home directory.  I'm running KDE
>> using the gtk-qt engine for GTK apps, and in my personal settings for
>> this engine I have the option "Use my KDE fonts in GTK applications"
>> set, but I'm afraid I don't know how they are set.
>
> xrdb -q will list them.

This lists only what I put in ~/.Xresources.

>> As a test I created ~/.Xresources with a setting for Emacs.font, ran
>> xrdb on it and then invoked unicode Emacs, but it still just returned
>> the peculiar error message (Emacs from CVS trunk did use that font, so
>> I know it is valid).
>
> There are also the app-defaults, probably in
> /usr/share/X11/app-defaults/Emacs.

Yes, this has settings for Emacs.Font and Emacs*Fontset-0 through
Emacs*Fontset-8 

Steve Berman

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20 12:42     ` Kenichi Handa
@ 2007-12-20 14:14       ` Stephen Berman
  2007-12-21 16:27       ` KOBAYASHI Yasuhiro
  1 sibling, 0 replies; 22+ messages in thread
From: Stephen Berman @ 2007-12-20 14:14 UTC (permalink / raw)
  To: emacs-devel

On Thu, 20 Dec 2007 21:42:38 +0900 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <uwsr94ovx.fsf@otsukakj.co.jp>, KOBAYASHI Yasuhiro <kobayays@gmail.com> writes:
>
>> -- Msg in minibuffer --
>> "peculiar error: "invalid font property", (:weight . arial)"
>> --
>
> Ah, I found what's wrong.  I've just installed a fix.
>
> Stephen, I think you problem was caused by the same bug.
>
> Please try again with the latest code.

I updated again and rebuilt and recompiled the Lisp files, but still
Emacs fails to open a frame, and now the message is this:
peculiar error: "invalid font property", (:spacing . iso8859)

This is both with and without -Q, and also after make bootstrap.

Steve Berman

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20 14:14       ` Stephen Berman
@ 2007-12-21  0:47         ` Kenichi Handa
  2007-12-21 16:40           ` Stephen Berman
  0 siblings, 1 reply; 22+ messages in thread
From: Kenichi Handa @ 2007-12-21  0:47 UTC (permalink / raw)
  To: Stephen Berman; +Cc: emacs-devel

In article <87bq8lpi64.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:

> I updated again and rebuilt and recompiled the Lisp files, but still
> Emacs fails to open a frame, and now the message is this:
> peculiar error: "invalid font property", (:spacing . iso8859)

Hmmm, it seems that there still is a bug in parsing font
name.  I want to know which font name causes that problem.

> > There are also the app-defaults, probably in
> > /usr/share/X11/app-defaults/Emacs.

> Yes, this has settings for Emacs.Font and Emacs*Fontset-0 through
> Emacs*Fontset-8 

Then please show me them.

---
Kenichi Handa
handa@ni.aist.go.jp

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-20 12:42     ` Kenichi Handa
  2007-12-20 14:14       ` Stephen Berman
@ 2007-12-21 16:27       ` KOBAYASHI Yasuhiro
  2007-12-26  1:56         ` Kenichi Handa
  1 sibling, 1 reply; 22+ messages in thread
From: KOBAYASHI Yasuhiro @ 2007-12-21 16:27 UTC (permalink / raw)
  To: Kenichi Handa; +Cc: emacs-devel

In message Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
 on Thu, 20 Dec 2007 21:42:38 +0900
 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <uwsr94ovx.fsf@otsukakj.co.jp>, KOBAYASHI Yasuhiro <kobayays@gmail.com> writes:

> > -- Msg in minibuffer --
> > "peculiar error: "invalid font property", (:weight . arial)"
> > --

> Ah, I found what's wrong.  I've just installed a fix.

> Stephen, I think you problem was caused by the same bug.

> Please try again with the latest code.

The error messages were disappeared, but the font size is
too large.

I set it as 12 point, but it is 18 point.
-- 
KOBAYASHI Yasuhiro <kobayays@gmail.com>

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-21  0:47         ` Kenichi Handa
@ 2007-12-21 16:40           ` Stephen Berman
  2007-12-23 18:40             ` hcz
  2007-12-26  0:57             ` Kenichi Handa
  0 siblings, 2 replies; 22+ messages in thread
From: Stephen Berman @ 2007-12-21 16:40 UTC (permalink / raw)
  To: emacs-devel

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

On Fri, 21 Dec 2007 09:47:01 +0900 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <87bq8lpi64.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> I updated again and rebuilt and recompiled the Lisp files, but still
>> Emacs fails to open a frame, and now the message is this:
>> peculiar error: "invalid font property", (:spacing . iso8859)
>
> Hmmm, it seems that there still is a bug in parsing font
> name.  I want to know which font name causes that problem.
>
>> > There are also the app-defaults, probably in
>> > /usr/share/X11/app-defaults/Emacs.
>
>> Yes, this has settings for Emacs.Font and Emacs*Fontset-0 through
>> Emacs*Fontset-8 
>
> Then please show me them.

Attached.

Steve Berman


[-- Attachment #2: Emacs fontsets --]
[-- Type: text/plain, Size: 8199 bytes --]

! ==========================================================================
!				Emacs
! ==========================================================================

Emacs.Font:			fontset-16
Emacs.pane.menubar.font:	-*-helvetica-bold-r-normal--12-*-*-*-p-*-iso8859-*
Emacs.menu*.font:		-*-helvetica-bold-r-normal--12-*-*-*-p-*-iso8859-*
Emacs*Fontset-0:\
	-*-fixed-medium-r-*--16-*-*-*-*-*-fontset-16,\
	latin-iso8859-1:-*-fixed-medium-r-*--16-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--16-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--16-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--16-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--16-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--16-*-iso8859-7,\
	hebrew-iso8859-8:-*-fixed-medium-r-*--16-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--16-*-iso8859-9,\
	latin-iso8859-15:-*-fixed-medium-r-*--16-*-iso8859-15,\
	arabic-digit:-*-fixed-medium-r-*--16-*-mulearabic-0,\
	arabic-1-column:-*-fixed-medium-r-*--16-*-mulearabic-1,\
	arabic-2-column:-*-fixed-medium-r-*--16-*-mulearabic-2,\
	katakana-jisx0201:-*-fixed-medium-r-*--16-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-fixed-medium-r-*--16-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--16-*-ksc5601*-*,\
	chinese-big5-1:-*-fixed-medium-r-*--16-*-big5*-0,\
	chinese-gb2312:-*-medium-r-normal-*-16-*-gb2312*-*,\
	chinese-cns11643-1:-*-medium-r-normal-*-16-*-cns11643*-1,\
	chinese-cns11643-2:-*-medium-r-normal-*-16-*-cns11643*-2,\
	chinese-cns11643-3:-*-medium-r-normal-*-16-*-cns11643*-3,\
	chinese-cns11643-4:-*-medium-r-normal-*-16-*-cns11643*-4,\
	chinese-cns11643-5:-*-medium-r-normal-*-16-*-cns11643*-5,\
	chinese-cns11643-6:-*-medium-r-normal-*-16-*-cns11643*-6,\
	chinese-cns11643-7:-*-medium-r-normal-*-16-*-cns11643*-7, \
	thai-tis620:-*-fixed-medium-r-*--16-*-tis620.2529-1,\
	vietnamese-viscii-lower:-*-fixed-medium-r-*--16-*-viscii1.1-1,\
	lao:-*-fixed-medium-r-*--16-*-mulelao-1,\
	tibetan:-*-fixed-medium-r-*--16-*-muletibetan-0,\
	tibetan-1-column:-*-fixed-medium-r-*--16-*-muletibetan-1
Emacs*Fontset-1:\
	-*-fixed-medium-r-*--24-*-*-*-*-*-fontset-24,\
	latin-iso8859-1:-*-fixed-medium-r-*--24-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--24-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--24-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--24-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--24-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--24-*-iso8859-7,\
	hebrew-iso8859-8:-*-fixed-medium-r-*--24-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--24-*-iso8859-9,\
	latin-iso8859-15:-*-fixed-medium-r-*--24-*-iso8859-15,\
	arabic-digit:-*-fixed-medium-r-*--24-*-mulearabic-0,\
	arabic-1-column:-*-fixed-medium-r-*--24-*-mulearabic-1,\
	arabic-2-column:-*-fixed-medium-r-*--24-*-mulearabic-2,\
	katakana-jisx0201:-*-fixed-medium-r-*--24-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-fixed-medium-r-*--24-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--24-*-ksc5601*-*,\
	chinese-big5-1:-*-fixed-medium-r-*--24-*-big5*-0,\
	chinese-gb2312:-*-medium-r-normal-*-24-*-gb2312*-*,\
	chinese-cns11643-1:-*-medium-r-normal-*-24-*-cns11643*-1,\
	chinese-cns11643-2:-*-medium-r-normal-*-24-*-cns11643*-2,\
	chinese-cns11643-3:-*-medium-r-normal-*-24-*-cns11643*-3,\
	chinese-cns11643-4:-*-medium-r-normal-*-24-*-cns11643*-4,\
	chinese-cns11643-5:-*-medium-r-normal-*-24-*-cns11643*-5,\
	chinese-cns11643-6:-*-medium-r-normal-*-24-*-cns11643*-6,\
	chinese-cns11643-7:-*-medium-r-normal-*-24-*-cns11643*-7,\
	thai-tis620:-*-fixed-medium-r-*--24-*-tis620.2529-1,\
	vietnamese-viscii-lower:-*-fixed-medium-r-*--24-*-viscii1.1-1,\
	lao:-*-fixed-medium-r-*--24-*-mulelao-1,\
	indian-is13194:-*-fixed-medium-r-*--24-*-is13194-devanagari,\
	indian-1-column:-*-fixed-medium-r-*--24-*-muleindian-1,\
	indian-2-column:-*-fixed-medium-r-*--24-*-muleindian-2,\
	tibetan:-*-fixed-medium-r-*--24-*-muletibetan-0,\
	tibetan-1-column:-*-fixed-medium-r-*--24-*-muletibetan-1
Emacs*Fontset-2:\
	-*-fixed-medium-r-*--20-*-*-*-*-*-fontset-20,\
	latin-iso8859-1:-*-fixed-medium-r-*--20-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--20-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--20-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--20-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--20-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--20-*-iso8859-7,\
	hebrew-iso8859-8:-*-fixed-medium-r-*--20-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--20-*-iso8859-9,\
	latin-iso8859-15:-*-fixed-medium-r-*--20-*-iso8859-15,\
	katakana-jisx0201:-*-fixed-medium-r-*--20-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-fixed-medium-r-*--20-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--20-*-ksc5601*-*
Emacs*Fontset-3:\
	-*-fixed-medium-r-*--18-*-*-*-*-*-fontset-18,\
	latin-iso8859-1:-*-fixed-medium-r-*--18-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--18-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--18-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--18-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--18-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--18-*-iso8859-7,\
	hebrew-iso8859-8:-*-fixed-medium-r-*--18-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--18-*-iso8859-9,\
	latin-iso8859-15:-*-fixed-medium-r-*--18-*-iso8859-15,\
	katakana-jisx0201:-*-*-medium-r-*--18-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-*-medium-r-*--18-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--18-*-ksc5601*-*
Emacs*Fontset-4:\
	-*-fixed-medium-r-*--14-*-*-*-*-*-fontset-14,\
	latin-iso8859-1:-*-fixed-medium-r-*--14-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--14-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--14-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--14-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--14-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--14-*-iso8859-7,\
	hebrew-iso8859-8:-*-fixed-medium-r-*--14-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--14-*-iso8859-9,\
	latin-iso8859-15:-*-fixed-medium-r-*--14-*-iso8859-15,\
	katakana-jisx0201:-*-fixed-medium-r-*--14-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-fixed-medium-r-*--14-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--14-*-ksc5601*-*,\
	thai-tis620:-*-fixed-medium-r-*--14-*-tis620.2529-1,\
	lao:-*-fixed-medium-r-*--14-*-mulelao-1
Emacs*Fontset-5:\
	-*-fixed-medium-r-*--12-*-*-*-*-*-fontset-12,\
	latin-iso8859-1:-*-fixed-medium-r-*--12-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--12-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--12-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--12-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--12-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--12-*-iso8859-7,\
	latin-iso8859-15:-*-fixed-medium-r-*--12-*-iso8859-15 \
	hebrew-iso8859-8:-*-fixed-medium-r-*--12-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--12-*-iso8859-9,\
	katakana-jisx0201:-*-fixed-medium-r-*--12-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-fixed-medium-r-*--12-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--12-*-ksc5601.1987-0
Emacs*Fontset-6:\
	-*-fixed-medium-r-*--10-*-*-*-*-*-fontset-10,\
	latin-iso8859-1:-*-fixed-medium-r-*--10-*-iso8859-1,\
	latin-iso8859-2:-*-fixed-medium-r-*--10-*-iso8859-2,\
	latin-iso8859-3:-*-fixed-medium-r-*--10-*-iso8859-3,\
	latin-iso8859-4:-*-fixed-medium-r-*--10-*-iso8859-4,\
	cyrillic-iso8859-5:-*-fixed-medium-r-*--10-*-iso8859-5,\
	greek-iso8859-7:-*-fixed-medium-r-*--10-*-iso8859-7,\
	hebrew-iso8859-8:-*-fixed-medium-r-*--10-*-iso8859-8,\
	latin-iso8859-9:-*-fixed-medium-r-*--10-*-iso8859-9,\
	latin-iso8859-15:-*-fixed-medium-r-*--10-*-iso8859-15,\
	katakana-jisx0201:-*-fixed-medium-r-*--10-*-jisx0201.1976-0,\
	japanese-jisx0208:-*-fixed-medium-r-*--10-*-jisx0208*-0,\
	korean-ksc5601:-*-fixed-medium-r-*--10-*-ksc5601*-*
Emacs*Fontset-7:\
	-*-fixed-medium-r-*--8-*-*-*-*-*-fontset-8,\
	latin-iso8859-1:-*-fixed-medium-r-*--8-*-iso8859-1,\
	greek-iso8859-7:-*-fixed-medium-r-*--8-*-iso8859-7,\
	latin-iso8859-15:-*-fixed-medium-r-*--8-*-iso8859-15
Emacs*Fontset-8:\
	-*-fixed-medium-r-*--7-*-*-*-*-*-fontset-7,\
	latin-iso8859-1:-*-fixed-medium-r-*--7-*-iso8859-1,\
	greek-iso8859-7:-*-fixed-medium-r-*--7-*-iso8859-7,\
	latin-iso8859-15:-*-fixed-medium-r-*--7-*-iso8859-15

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-21 16:40           ` Stephen Berman
@ 2007-12-23 18:40             ` hcz
  2007-12-26  0:57             ` Kenichi Handa
  1 sibling, 0 replies; 22+ messages in thread
From: hcz @ 2007-12-23 18:40 UTC (permalink / raw)
  To: Emacs-devel


[-- Attachment #1.1: Type: text/plain, Size: 569 bytes --]


HI
   I have same bug as you.
   After I:
   1. uninstall emacs 23;
   2. /usr/share/X11/app-defaults/Emacs
   3. delete /usr/bin/emacs, /usr/bin/emacs-23.0.60, /usr/local/bin/emacs,
/usr/local/emacs-23.0.60 and so on
   Last, install emacs 23 again
  
   so I think it is because I have install old version before I install
emacs 23.

Good Luck!
-- 
View this message in context: http://www.nabble.com/23.0.60--peculiar-error%3A-%22invalid-font-property%22%2C-%28%3Aweight-.-r%29-tp14418566p14480712.html
Sent from the Emacs - Dev mailing list archive at Nabble.com.

[-- Attachment #1.2: Type: text/html, Size: 748 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-21 16:40           ` Stephen Berman
  2007-12-23 18:40             ` hcz
@ 2007-12-26  0:57             ` Kenichi Handa
  2008-01-03 20:18               ` Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)) Stephen Berman
  1 sibling, 1 reply; 22+ messages in thread
From: Kenichi Handa @ 2007-12-26  0:57 UTC (permalink / raw)
  To: Stephen Berman; +Cc: emacs-devel

In article <874pec3ss3.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:

> [2 Emacs fontsets <text/plain (7bit)>]
> ! ==========================================================================
> !				Emacs
> ! ==========================================================================
[...]
> Emacs*Fontset-5:\
> 	-*-fixed-medium-r-*--12-*-*-*-*-*-fontset-12,\
> 	latin-iso8859-1:-*-fixed-medium-r-*--12-*-iso8859-1,\
> 	latin-iso8859-2:-*-fixed-medium-r-*--12-*-iso8859-2,\
> 	latin-iso8859-3:-*-fixed-medium-r-*--12-*-iso8859-3,\
> 	latin-iso8859-4:-*-fixed-medium-r-*--12-*-iso8859-4,\
> 	cyrillic-iso8859-5:-*-fixed-medium-r-*--12-*-iso8859-5,\
> 	greek-iso8859-7:-*-fixed-medium-r-*--12-*-iso8859-7,\
> 	latin-iso8859-15:-*-fixed-medium-r-*--12-*-iso8859-15 \
> 	hebrew-iso8859-8:-*-fixed-medium-r-*--12-*-iso8859-8,\
> 	latin-iso8859-9:-*-fixed-medium-r-*--12-*-iso8859-9,\
> 	katakana-jisx0201:-*-fixed-medium-r-*--12-*-jisx0201.1976-0,\
> 	japanese-jisx0208:-*-fixed-medium-r-*--12-*-jisx0208*-0,\
> 	korean-ksc5601:-*-fixed-medium-r-*--12-*-ksc5601.1987-0

This entry has a bug.  The specifications for
latin-iso8859-15 and hebrew-iso8859-8 are not separated by
",".  Previously Emacs silently ignored such specifications,
but the new code doesn't.

By the way, as this error message:

peculiar error: "invalid font property", (:spacing . iso8859)

is too cryptic, I'll try to improve it.

---
Kenichi Handa
handa@ni.aist.go.jp

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-21 16:27       ` KOBAYASHI Yasuhiro
@ 2007-12-26  1:56         ` Kenichi Handa
  2007-12-26 15:47           ` KOBAYASHI Yasuhiro
  0 siblings, 1 reply; 22+ messages in thread
From: Kenichi Handa @ 2007-12-26  1:56 UTC (permalink / raw)
  To: KOBAYASHI Yasuhiro; +Cc: emacs-devel

In article <uve6s57z3.fsf@otsukakj.co.jp>, KOBAYASHI Yasuhiro <kobayays@gmail.com> writes:

> The error messages were disappeared, but the font size is
> too large.

> I set it as 12 point, but it is 18 point.

I've just installed a fix.

---
Kenichi Handa
handa@ni.aist.go.jp

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-26  1:56         ` Kenichi Handa
@ 2007-12-26 15:47           ` KOBAYASHI Yasuhiro
  2008-01-17  5:16             ` KOBAYASHI Yasuhiro
  0 siblings, 1 reply; 22+ messages in thread
From: KOBAYASHI Yasuhiro @ 2007-12-26 15:47 UTC (permalink / raw)
  To: Kenichi Handa; +Cc: emacs-devel

In message Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
 on Wed, 26 Dec 2007 10:56:37 +0900
 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <uve6s57z3.fsf@otsukakj.co.jp>, KOBAYASHI Yasuhiro <kobayays@gmail.com> writes:

> > The error messages were disappeared, but the font size is
> > too large.

> > I set it as 12 point, but it is 18 point.

> I've just installed a fix.

I tried to recompile but it is not improved.
-- 
KOBAYASHI Yasuhiro <kobayays@gmail.com>

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r))
  2007-12-26  0:57             ` Kenichi Handa
@ 2008-01-03 20:18               ` Stephen Berman
  2008-01-03 22:07                 ` Andreas Schwab
  0 siblings, 1 reply; 22+ messages in thread
From: Stephen Berman @ 2008-01-03 20:18 UTC (permalink / raw)
  To: emacs-devel

On Wed, 26 Dec 2007 09:57:52 +0900 Kenichi Handa <handa@ni.aist.go.jp> wrote:

> In article <874pec3ss3.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> [2 Emacs fontsets <text/plain (7bit)>]
>> ! ==========================================================================
>> !				Emacs
>> ! ==========================================================================
> [...]
>> Emacs*Fontset-5:\
>> 	-*-fixed-medium-r-*--12-*-*-*-*-*-fontset-12,\
>> 	latin-iso8859-1:-*-fixed-medium-r-*--12-*-iso8859-1,\
>> 	latin-iso8859-2:-*-fixed-medium-r-*--12-*-iso8859-2,\
>> 	latin-iso8859-3:-*-fixed-medium-r-*--12-*-iso8859-3,\
>> 	latin-iso8859-4:-*-fixed-medium-r-*--12-*-iso8859-4,\
>> 	cyrillic-iso8859-5:-*-fixed-medium-r-*--12-*-iso8859-5,\
>> 	greek-iso8859-7:-*-fixed-medium-r-*--12-*-iso8859-7,\
>> 	latin-iso8859-15:-*-fixed-medium-r-*--12-*-iso8859-15 \
>> 	hebrew-iso8859-8:-*-fixed-medium-r-*--12-*-iso8859-8,\
>> 	latin-iso8859-9:-*-fixed-medium-r-*--12-*-iso8859-9,\
>> 	katakana-jisx0201:-*-fixed-medium-r-*--12-*-jisx0201.1976-0,\
>> 	japanese-jisx0208:-*-fixed-medium-r-*--12-*-jisx0208*-0,\
>> 	korean-ksc5601:-*-fixed-medium-r-*--12-*-ksc5601.1987-0
>
> This entry has a bug.  The specifications for
> latin-iso8859-15 and hebrew-iso8859-8 are not separated by
> ",".  Previously Emacs silently ignored such specifications,
> but the new code doesn't.

Thank you for spotting this.  Inserting the comma eliminates the "peculiar
error" message and Emacs starts fine.

Now I have a question for Andreas Schwab: should I report this broken
file (dated Feb 26 2003!) on the openSUSE bugzilla or can you just fix
it or forward this to whoever is responsible for fixing it; and can this
file be fixed in openSUSE 10.3 or only in Factory?

Steve Berman

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r))
  2008-01-03 20:18               ` Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)) Stephen Berman
@ 2008-01-03 22:07                 ` Andreas Schwab
  2008-01-03 23:03                   ` Attn. Andreas Schwab Stephen Berman
  0 siblings, 1 reply; 22+ messages in thread
From: Andreas Schwab @ 2008-01-03 22:07 UTC (permalink / raw)
  To: Stephen Berman; +Cc: emacs-devel

Stephen Berman <Stephen.Berman@gmx.net> writes:

> Now I have a question for Andreas Schwab: should I report this broken
> file (dated Feb 26 2003!) on the openSUSE bugzilla or can you just fix
> it or forward this to whoever is responsible for fixing it; and can this
> file be fixed in openSUSE 10.3 or only in Factory?

If you want a fix for 10.3 you should report it to bugzilla.  For
factory I'll do it after my vacation if nobody beats me.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: Attn. Andreas Schwab
  2008-01-03 22:07                 ` Andreas Schwab
@ 2008-01-03 23:03                   ` Stephen Berman
  0 siblings, 0 replies; 22+ messages in thread
From: Stephen Berman @ 2008-01-03 23:03 UTC (permalink / raw)
  To: emacs-devel

On Thu, 03 Jan 2008 23:07:07 +0100 Andreas Schwab <schwab@suse.de> wrote:

> Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> Now I have a question for Andreas Schwab: should I report this broken
>> file (dated Feb 26 2003!) on the openSUSE bugzilla or can you just fix
>> it or forward this to whoever is responsible for fixing it; and can this
>> file be fixed in openSUSE 10.3 or only in Factory?
>
> If you want a fix for 10.3 you should report it to bugzilla.  For
> factory I'll do it after my vacation if nobody beats me.

Thanks.  (I submitted a bug, 351537.)

Steve Berman

^ permalink raw reply	[flat|nested] 22+ messages in thread

* Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
  2007-12-26 15:47           ` KOBAYASHI Yasuhiro
@ 2008-01-17  5:16             ` KOBAYASHI Yasuhiro
  0 siblings, 0 replies; 22+ messages in thread
From: KOBAYASHI Yasuhiro @ 2008-01-17  5:16 UTC (permalink / raw)
  To: Kenichi Handa; +Cc: emacs-devel

In message Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
 on Thu, 27 Dec 2007 00:47:26 +0900
 KOBAYASHI Yasuhiro <kobayays@gmail.com> wrote:

> > I've just installed a fix.

> I tried to recompile but it is not improved.

It has been fixed on 2008-01-14. Thank you.
-- 
KOBAYASHI Yasuhiro <kobayays@gmail.com>

^ permalink raw reply	[flat|nested] 22+ messages in thread

end of thread, other threads:[~2008-01-17  5:16 UTC | newest]

Thread overview: 22+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-19 14:58 23.0.60; peculiar error: "invalid font property", (:weight . r) Stephen Berman
2007-12-19 15:24 ` Jason Rumney
2007-12-19 15:32   ` Stephen Berman
2007-12-20  0:58   ` Kenichi Handa
2007-12-20  0:54 ` Kenichi Handa
2007-12-20 10:29   ` Stephen Berman
2007-12-20 11:21     ` Andreas Schwab
2007-12-20 14:14       ` Stephen Berman
2007-12-21  0:47         ` Kenichi Handa
2007-12-21 16:40           ` Stephen Berman
2007-12-23 18:40             ` hcz
2007-12-26  0:57             ` Kenichi Handa
2008-01-03 20:18               ` Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)) Stephen Berman
2008-01-03 22:07                 ` Andreas Schwab
2008-01-03 23:03                   ` Attn. Andreas Schwab Stephen Berman
2007-12-20 10:54   ` 23.0.60; peculiar error: "invalid font property", (:weight . r) KOBAYASHI Yasuhiro
2007-12-20 12:42     ` Kenichi Handa
2007-12-20 14:14       ` Stephen Berman
2007-12-21 16:27       ` KOBAYASHI Yasuhiro
2007-12-26  1:56         ` Kenichi Handa
2007-12-26 15:47           ` KOBAYASHI Yasuhiro
2008-01-17  5:16             ` KOBAYASHI Yasuhiro

Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.