Re: [unicode-2] Chinese characters too small

2007-07-12 Thread Leo
On 2007-07-12 03:55 +0200, Kenichi Handa wrote:
 In article [EMAIL PROTECTED], Leo [EMAIL PROTECTED] writes:

 I configured XTerm and Emacs to use the same font with same size as
 follows:

 in .Xresources:

   XTerm*faceName: xft:monospace:pixelsize=16
   XTerm*faceNameDoublesize: fzsongti
   Emacs.Font: monospace:pixelsize=16

 in .emacs:

 (when window-system
   (set-fontset-font (frame-parameter nil 'font)
  'han '(FZSongTi . unicode-bmp)))

 And then I compared Chinese characters in 'emacs -nw' running in xterm
 and emacs running in X11. It turns out Chinese characters are
 substantially smaller in Emacs running in X11.

 However, C-u C-x = shows that the characters have pixelsize 16. Is this
 a bug?

 I'm not sure.  Is the font size of ASCII characters the same
 in emacs and xterm?

 Could you please check the actual pixel size of a Chinese
 character by, for instance, xmag?

 ---
 Kenichi Handa
 [EMAIL PROTECTED]

It appears that Chinese characters have pixelsize 16 in Emacs 
rxvt-unicode  gnome-terminal but have a larger pixelsize in gedit 
xterm.

I am running Fedora 7.

HTH,
-- 
Leo sdl.web AT gmail.com (GPG Key: 9283AA3F)



___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: Emacs 23.0.0.1 fails parsing gdb output

2007-07-12 Thread Nick Roberts

 In GNU Emacs 23.0.0.1 (i486-pc-linux-gnu, GTK+ Version 2.10.11)
  of 2007-07-06 on helios

I have GNU gdb 6.6-debian and it works fine with GNU Emacs 23.0.0.3
(i686-pc-linux-gnu, GTK+ Version 2.10.11).

  Does it fail with Emacs 22.1?

 I'm having the same or very similar problems on Solaris / Sparc using
 Emacs 22.1 and gdb-6.5.

There might be problems with GDB on Solaris / Sparc.

  then post the value of gdb-debug-log to [EMAIL PROTECTED]

 Attached.  

This log looks OK but it's prior to execution.  Your earlier report,
which I should have looked at more carefully, shows the problem occurs
after execution begins:

  Loading GDB sequences...
  *** Hope you've got /home/appeal/bin or //depot/jrockit/cce/gdbutils in your 
path
  *** I use a few helper scripts nowadays
  Generating isNativeIp and printmodule

What happens if you start your application under GDB without the GDB
scripts?

I think that M-x gdb doesn't work in you start execution from within a script.
In this case you must use M-x gdba.  Does this work?

Since this (or something very similar) is a problem with
 both 22.1 and 23.0.0.1 I'm posting to both bug lists.

Yes, it's taken so long to release 22.1, I forget that bug-gnu-emacs is
the proper mailing list for 22.1.  It's probably sufficient though to keep
the thread on emacs-pretest-bug and just report conclusions (if any) on
bug-gnu-emacs.



-- 
Nick   http://www.inet.net.nz/~nickrob


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: [unicode-2] Chinese characters too small

2007-07-12 Thread Kenichi Handa
In article [EMAIL PROTECTED], Leo [EMAIL PROTECTED] writes:

 It appears that Chinese characters have pixelsize 16 in Emacs 
 rxvt-unicode  gnome-terminal but have a larger pixelsize in gedit 
 xterm.

How did you specify the font pixelsize in gedit?  As far as
I know, what you set via Edit-Preferences-FontColors is
pointsize?

---
Kenichi Handa
[EMAIL PROTECTED]


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: [unicode-2] Chinese characters too small

2007-07-12 Thread Zhang Wei
Leo [EMAIL PROTECTED] writes:

[...]

 (when window-system
   (set-fontset-font (frame-parameter nil 'font)
   'han '(FZSongTi . unicode-bmp)))

The problem is that we can't specify different pixelsize for different
script. If we specify a font in the command line:

emacs --enable-font-backend -fn Bitstream Vera Sans Mono-14

then all script will use 14 pixelsize font. We could specify a different
font for some scripts with `set-fontset-font', such as:

(set-fontset-font (frame-parameter nil 'font)
'han '(SimSun . unicode-bmp))

but we can't change the fontsize:

(set-fontset-font (frame-parameter nil 'font)
'han '(SimSun-16 . unicode-bmp))

won't work. We hope `set-fontset-font' could be used for changing
fontsize also.








___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: Emacs 23.0.0.1 fails parsing gdb output

2007-07-12 Thread Nick Roberts

 I'm attaching a new debug log where I've gone one step further and
 done f in the GDB pane to get the source window to refresh.  That
 did get me a bunch of error messages which might make this log a bit
 more interesting to you.

It still doesn't seem to contain the errors but I don't think they can be
avoided without deffering execution or using M-x gdba anyway.

  What happens if you start your application under GDB without the GDB
  scripts?

 The reason we have the scripts is that what we're debugging is a
 library (libjvm.so), and the scripts run load and run things long
 enough for us to get into our library.  If we don't run the scripts,
 nothing will even get loaded into gdb.

I see, but presumably you can do this after M-x gdb has started up:

  M-x gdb
  Run gdb (like this): gdb -annotate=3 myprog

In GUD buffer:

  Current directory is /home/nickrob/
  GNU gdb 6.6-debian
  ...
  (gdb) source myscript

but, in any case, M-x gdba is probably more convenient.

  I think that M-x gdb doesn't work in you start execution from within a
  script.  In this case you must use M-x gdba.  Does this work?

 Yes!  What's the difference betweeen gdb and gdba?  I wasn't able to
 find anything documenting the difference, according to the docs they
 seem to do roughly the same thing.

M-x gdba assumes that GDB is being run with the --annotate=3 option.  M-x gdb
filters the output to determine whether GDB is being run with --fullname or
--annotate=3.  The former gives the old Emacs 21 functionality (or lack of
it!) and is worth using if all else fails.

So they do indeed do the same thing, in most cases, when --annotate=3 is
used (the default).  There is a problem when GDB commands like run are
included in GDB scripts because these get run _before_ GDB commands that Emacs
uses to set up the mode.  Perhaps I'll add a note in the manual.

-- 
Nick   http://www.inet.net.nz/~nickrob


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: vc-cvs.el:953:42:Error: Lisp nesting exceeds `max-lisp-eval-depth'

2007-07-12 Thread Stefan Monnier
   Compiling /Users/pete/Quellen/Emacs_CVS/emacs/lisp/./vc-bzr.el
   Wrote /Users/pete/Quellen/Emacs_CVS/emacs/lisp/vc-bzr.elc
   Compiling /Users/pete/Quellen/Emacs_CVS/emacs/lisp/./vc-cvs.el

   In toplevel form:
   vc-cvs.el:953:42:Error: Lisp nesting exceeds `max-lisp-eval-depth'
   make[2]: *** [compile] Error 1
   make[2]: Target `bootstrap' not remade because of errors.
   make[1]: *** [bootstrap-build] Error 2
   make: *** [bootstrap] Error 2

Should be fixed now,


Stefan


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug