Re: Ugly W32 display bug - fontified letters chopped on right
> From: Eric Hanchrow <[EMAIL PROTECTED]> > Date: Sun, 08 Apr 2007 17:35:43 -0700 > > I'm clearly seeing it myself, for what that's worth, using Bitstream > Vera Sans Mono at 12 pixels. Do you have ClearType turned on? If so, does the problem go away if you turn it off? Do you see the problem with the default font selected by Emacs in "emacs -Q"? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Error when creating new frame
I withdraw this report -- found another setting of the after-make-frame-functions hook that did not give the frame as an argument. Apologies ==John ffitch ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Ugly W32 display bug - fontified letters chopped on right
> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes: >> I'm clearly seeing it myself, for what that's worth, using >> Bitstream Vera Sans Mono at 12 pixels. Eli> Do you have ClearType turned on? I did. Eli> If so, does the problem go away if you turn it off? It did indeed. Eli> Do you see the problem with the default font selected by Eli> Emacs in "emacs -Q"? Yes, if ClearType is on. -- Raffarin said he wants to see secure Internet voting in France by 2009, and he said if he had a homosexual son, he would love him ... -- from the Chicago Tribune ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: C-u C-SPC: doc string and behavior if mark = point
> From: "Drew Adams" <[EMAIL PROTECTED]> > Date: Sun, 8 Apr 2007 10:43:55 -0700 > > 1. Doc string for `set-mark-command': Thanks, I implemented some of your suggestions. The new doc string appears at the end of this message. > Get rid of "e.g. C-u C-@". I don't see any reason to get rid of this, as it's a valuable advice to novices who could otherwise do something like M-1, which is much less convenient. > Get rid of "With a double C-u prefix argument, e.g. C-u C-u C-@"; just > say "With `C-u C-u'". Ditto. > Remove quotes around "region". Remove ", which is the closest > thing...". Remove the paragraph about setting the region altogether > (the region is not "set"). Just say "The region is the buffer area > between the mark and the cursor position. Some people call it the > "selection"." Didn't change any of these, since I see nothing wrong with the current wording. - set-mark-command is an interactive compiled Lisp function in `simple.el'. It is bound to C-@, C-SPC. (set-mark-command arg) Set mark where point is, or jump to mark. Setting the mark also sets the "region", which is the closest equivalent in Emacs to what some editors call the "selection". With no prefix argument, set mark and push old mark position on local mark ring. Also, push mark on global mark ring if last mark was set in another buffer. Immediately repeating the command activates `transient-mark-mode' temporarily. With prefix argument (e.g., C-u C-@), jump to mark, and set mark from position popped off the local mark ring (this does not affect the global mark ring). Use C-x C-@ to jump to a mark popped off the global mark ring (see `pop-global-mark'). If `set-mark-command-repeat-pop' is non-nil, repeating the C-@ command with no prefix argument pops the next position off the local (or global) mark ring and jumps there. With a double C-u prefix argument (e.g., C-u C-u C-@), unconditionally set mark where point is, even if `set-mark-command-repeat-pop' is non-nil. Novice Emacs Lisp programmers often try to use the mark for the wrong purposes. See the documentation of `set-mark' for more information. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: A funny bug in Emacs Unicode2/xft branch
On 2007-04-09, Kenichi Handa said: >> In old Emacs 23: >> "←" are shown by: >> normal: dejavu lgc sans >> mono:pixelsize=16:foundry=unknown:weight=medium:slant=r:width=normal (#x563) >> bold: dejavu lgc sans >> mono:pixelsize=16:foundry=unknown:weight=bold:slant=r:width=normal (#x563) > >> In Emacs 23 with new fontset.c: >> "←" are shown by: >> normal: dejavu lgc sans >> mono:pixelsize=16:foundry=unknown:weight=medium:slant=r:width=normal (#x563) >> bold: dejavu lgc sans >> mono:pixelsize=16:foundry=unknown:weight=medium:slant=r:width=normal (#x563) > > Oops, the fontset.c I sent you had a silly bug. Please try > with the new one attached at the tail. It seems I don't have settings to see this bug fix. But I can confirm "←" is now using the same bold font as with old fontset.c. -- Leo (GPG Key: 9283AA3F) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Ugly W32 display bug - fontified letters chopped on right
> Cc: emacs-pretest-bug@gnu.org > From: Eric Hanchrow <[EMAIL PROTECTED]> > Date: Mon, 09 Apr 2007 00:24:24 -0700 > > > "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes: > > >> I'm clearly seeing it myself, for what that's worth, using > >> Bitstream Vera Sans Mono at 12 pixels. > > Eli> Do you have ClearType turned on? > > I did. > > Eli> If so, does the problem go away if you turn it off? > > It did indeed. Thanks. I added an entry to PROBLEMS about issues with ClearType. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [unicode-2] whitespace-auto-cleanup always replaces leading spaces with tabs
>>(defcustom whitespace-check-indent-whitespace indent-tabs-mode >> "Flag to check indentation whitespace. This is the global for the system. > > > That fails to do the right thing if the user changes indent-tabs-mode > mode after whitespace.el is loaded -- which is certainly not unlikely, > especially given that indent-tabs-mode is automatically buffer local, > and traditionally set on a per-buffer basis! I have to admit that I wanted the original poster to describe exactly this sequence of events. > In general, using another variable as the initial value in a > defvar/defcustom is almost never the right thing for exactly this > reason. In particular if the variable comes from another group. > The right thing to do with whitespace.el is probably support a special `auto' > value for such settings. For instance, in `whitespace-cleanup-internal', > instead of just checking the value of `whitespace-check-buffer-indent' (the > "local" version of `whitespace-check-indent-whitespace'), it could do > something like: > >(if (eq whitespace-check-buffer-indent 'auto) >indent-tabs-mode > whitespace-check-buffer-indent) IMHO there's no reasonable way to reconcile a user's settings of `indent-tabs-mode' with those of `whitespace-check-indent-whitespace'. I think `whitespace-indent-cleanup' should be executed iff `indent-tabs-mode' is non-nil in the current buffer. But I'm afraid that anything we change here will break existing customizations. > [Incidentally, whitespace.el seems absurdly overspeced in many ways -- > is it really necessary to have separate names for the global and local > versions of every config variable, and a toggle function for just about > every whitespace option?!?] After the release we should probably distill a simple and robust implementation. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Carbon Emacs won't start when installed in certain paths
Emacs (recent CVS build, Carbon) will not start when installed in directories with certain file names. For example when I install the .app bundle in /Applications/Pour Développement, it refuses to run. When started from a terminal, the error messages I'm getting are lucy:/Applications/Pour DeÌveloppement dr$ Aquamacs\ Emacs\ Yesterday.app/Contents/MacOS/Aqu* Warning: arch-dependent data dir (/usr/local/libexec/emacs/22.0.96/ powerpc-apple-darwin7.9.0/) does not exist. Warning: arch-independent data dir (/usr/local/share/emacs/22.0.96/ etc/) does not exist. Cannot open load file: term/mac-win (Not that the first two warnings are normal.) This error obviously occurs before loading any user-specific settings, so I'm not sending the Emacs debug log. N.B.: This build is compiled on OS X 10.3.9. I am testing on 10.4.9 (PPC). The filesystem is the normal Mac filesystem (Mac OS Extended, Journaled). ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: A funny bug in Emacs Unicode2/xft branch
In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes: > > Oops, the fontset.c I sent you had a silly bug. Please try > > with the new one attached at the tail. > It seems I don't have settings to see this bug fix. But I can confirm > "←" is now using the same bold font as with old fontset.c. Thank you for confirming that. I'll soon commit this new version, and keep on working for the problem with U+2500. --- Kenichi Handa [EMAIL PROTECTED] ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Crash in redisplay_internal -> note_mode_line_or_margin_highlight
This crash occurred with a (slightly modified) CVS version (2007-04-04), Carbon build. I was trying out tabbar.el (providing tabbar-mode) using PNG files for `tabbar-home-button-enabled-image' and the other tabbar buttons. I think I clicked on the "mode" (leftmost) button before this happened, but I'm not sure. Unfortunately I cannot reproduce this crash. I can provide the tabbar code used if necessary - but it's not a recipe for a crash. The stack trace is below. Date/Time: 2007-04-09 08:42:13.677 +0100 OS Version: 10.4.9 (Build 8P135) Report Version: 4 Command: Aquamacs Emacs Path:/Applications/Aquamacs Emacs.app/Contents/MacOS/Aquamacs Emacs Parent: WindowServer [67] Version: Aquamacs 1.0rc2, GNU Emacs 22 (1.2a) PID:882 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x027f5fe0 Thread 0 Crashed: 0 org.gnu.AquamacsEmacs 0x000418d8 note_mode_line_or_margin_highlight + 1364 (xdisp.c:22582) 1 org.gnu.AquamacsEmacs 0x00041c58 note_mouse_highlight + 424 (xdisp.c:22731) 2 org.gnu.AquamacsEmacs 0x00140860 XTframe_up_to_date + 120 (macterm.c:2120) 3 org.gnu.AquamacsEmacs 0x0002d490 redisplay_internal + 4000 (xdisp.c:11372) 4 org.gnu.AquamacsEmacs 0x0002d8c8 redisplay_preserve_echo_area + 100 (xdisp.c:11576) 5 org.gnu.AquamacsEmacs 0x00081fc0 read_char + 1204 (keyboard.c: 2671) 6 org.gnu.AquamacsEmacs 0x0008b048 read_key_sequence + 1888 (keyboard.c:9154) 7 org.gnu.AquamacsEmacs 0x0007fb0c command_loop_1 + 1048 (keyboard.c:1625) 8 org.gnu.AquamacsEmacs 0x000eba1c internal_condition_case + 336 (eval.c:1482) 9 org.gnu.AquamacsEmacs 0x0007f308 command_loop_2 + 64 (keyboard.c:1332) 10 org.gnu.AquamacsEmacs 0x000eb3cc internal_catch + 264 (eval.c: 1222) 11 org.gnu.AquamacsEmacs 0x0007f2a4 command_loop + 216 (keyboard.c:1300) 12 org.gnu.AquamacsEmacs 0x0007ebf8 recursive_edit_1 + 172 (keyboard.c:1010) 13 org.gnu.AquamacsEmacs 0x0007ed94 Frecursive_edit + 224 (keyboard.c:1071) 14 org.gnu.AquamacsEmacs 0x000edec0 Ffuncall + 852 (eval.c:2995) 15 org.gnu.AquamacsEmacs 0x0011ba9c Fbyte_code + 2324 (bytecode.c:680) 16 org.gnu.AquamacsEmacs 0x000ed110 Feval + 1128 (eval.c:2336) 17 org.gnu.AquamacsEmacs 0x000e9de4 Fprogn + 60 (eval.c:447) 18 org.gnu.AquamacsEmacs 0x000503dc Fsave_window_excursion + 100 (window.c:6664) 19 org.gnu.AquamacsEmacs 0x0011c3dc Fbyte_code + 4692 (bytecode.c:841) 20 org.gnu.AquamacsEmacs 0x000ee4d8 funcall_lambda + 632 (eval.c: 3189) 21 org.gnu.AquamacsEmacs 0x000ee05c Ffuncall + 1264 (eval.c:3054) 22 org.gnu.AquamacsEmacs 0x000ed574 Fapply + 588 (eval.c:2486) 23 org.gnu.AquamacsEmacs 0x000ed9a0 apply1 + 104 (eval.c:2751) 24 org.gnu.AquamacsEmacs 0x000e9b28 call_debugger + 372 (eval.c: 304) 25 org.gnu.AquamacsEmacs 0x000ec54c find_handler_clause + 468 (eval.c:1920) 26 org.gnu.AquamacsEmacs 0x000ebf54 Fsignal + 532 (eval.c:1675) 27 org.gnu.AquamacsEmacs 0x000ec094 xsignal + 16 (eval.c:1723) 28 org.gnu.AquamacsEmacs 0x000ec0e8 xsignal2 + 0 (eval.c:1745) 29 org.gnu.AquamacsEmacs 0x000ec730 Fcommandp + 0 (eval.c:2024) 30 org.gnu.AquamacsEmacs 0x000f8a7c Frequire + 732 (fns.c:3602) 31 org.gnu.AquamacsEmacs 0x000ed110 Feval + 1128 (eval.c:2336) 32 org.gnu.AquamacsEmacs 0x000eded4 Ffuncall + 872 (eval.c:2998) 33 org.gnu.AquamacsEmacs 0x0011ba9c Fbyte_code + 2324 (bytecode.c:680) 34 org.gnu.AquamacsEmacs 0x000ee4d8 funcall_lambda + 632 (eval.c: 3189) 35 org.gnu.AquamacsEmacs 0x000ee05c Ffuncall + 1264 (eval.c:3054) 36 org.gnu.AquamacsEmacs 0x0011ba9c Fbyte_code + 2324 (bytecode.c:680) 37 org.gnu.AquamacsEmacs 0x000ee4d8 funcall_lambda + 632 (eval.c: 3189) 38 org.gnu.AquamacsEmacs 0x000ee05c Ffuncall + 1264 (eval.c:3054) 39 org.gnu.AquamacsEmacs 0x000e9448 Fcall_interactively + 4928 (callint.c:860) 40 org.gnu.AquamacsEmacs 0x0008ca0c Fcommand_execute + 644 (keyboard.c:10050) 41 org.gnu.AquamacsEmacs 0x00080838 command_loop_1 + 4420 (keyboard.c:1894) 42 org.gnu.AquamacsEmacs 0x000eba1c internal_condition_case + 336 (eval.c:1482) 43 org.gnu.AquamacsEmacs 0x0007f308 command_loop_2 + 64 (keyboard.c:1332) 44 org.gnu.AquamacsEmacs 0x000eb3cc internal_catch + 264 (eval.c: 1222) 45 org.gnu.AquamacsEmacs 0x0007f260 command_loop + 148 (keyboard.c:1315) 46 org.gnu.AquamacsEmacs 0x0007ebf8 recursive_edit_1 + 172 (keyboard.c:1010) 47 org.gnu.AquamacsEmacs 0x0007ed94 Frecursive_edit + 224 (keyboard.c:1071) 48 org.gnu.AquamacsEmacs 0x0007d864 main + 3232 (emacs.c:1765) 49 org.gnu.AquamacsEmacs 0xa060 _start + 392 (crt.c:267) 50 dyld0x8fe01048 _dyld_start + 60 Thread 1: 0 libSystem.B.dylib 0x9001fa0c select + 12 1 com.apple.CoreFoundation0x907f1
[xft-emacs] XFT font in menu-bar
[GNU Emacs 23.0.0.7 (i686-pc-linux-gnu, X toolkit) of 2007-03-29] The default menu bar in Emacs started with --enable-font-backend is using X core font. Is this a known problem? FWIW, I caught a screen shot in XEmacs list and it seems it is possible to use XFT in Lucid menu-bar. http://people.exactcode.de/~rene/xemacs-beta-xft-off-by-one.png Thanks, -- Leo (GPG Key: 9283AA3F) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: C-u C-SPC: doc string and behavior if mark = point
> > 1. Doc string for `set-mark-command': > > Thanks, I implemented some of your suggestions. The new doc string > appears at the end of this message. > > > Get rid of "e.g. C-u C-@". > > I don't see any reason to get rid of this, as it's a valuable advice > to novices who could otherwise do something like M-1, which is much > less convenient. > > > Get rid of "With a double C-u prefix argument, e.g. C-u C-u C-@"; just > > say "With `C-u C-u'". > > Ditto. > > > Remove quotes around "region". Remove ", which is the closest > > thing...". Remove the paragraph about setting the region altogether > > (the region is not "set"). Just say "The region is the buffer area > > between the mark and the cursor position. Some people call it the > > "selection"." > > Didn't change any of these, since I see nothing wrong with the current > wording. > - > > set-mark-command is an interactive compiled Lisp function in `simple.el'. > It is bound to C-@, C-SPC. > (set-mark-command arg) > > Set mark where point is, or jump to mark. > Setting the mark also sets the "region", which is the closest > equivalent in Emacs to what some editors call the "selection". > > With no prefix argument, set mark and push old mark position on local > mark ring. Also, push mark on global mark ring if last mark was set in > another buffer. Immediately repeating the command activates > `transient-mark-mode' temporarily. > > With prefix argument (e.g., C-u C-@), jump to mark, and set mark from > position popped off the local mark ring (this does not affect the global > mark ring). Use C-x C-@ to jump to a mark popped off the global > mark ring (see `pop-global-mark'). > > If `set-mark-command-repeat-pop' is non-nil, repeating > the C-@ command with no prefix argument pops the next position > off the local (or global) mark ring and jumps there. > > With a double C-u prefix argument (e.g., C-u C-u C-@), unconditionally > set mark where point is, even if `set-mark-command-repeat-pop' is non-nil. > > Novice Emacs Lisp programmers often try to use the mark for the wrong > purposes. See the documentation of `set-mark' for more information. Looks better. Thanks, Eli. You can drop the quote marks around "region", but not around "selection". `C-@' defines (sets, if you like) the region itself, not the word "region". You can drop "e.g.", because `C-u C-u C-@' is not an example of a double prefix arg with C-@; it is the same thing as using a double prefix arg with [EMAIL PROTECTED] If you want, you can use "i.e." or, better, "that is", but neither is needed here. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Crash in redisplay_internal -> note_mode_line_or_margin_highlight
David Reitter <[EMAIL PROTECTED]> writes:
> This crash occurred with a (slightly modified) CVS version
> (2007-04-04), Carbon build.
>
> I was trying out tabbar.el (providing tabbar-mode) using PNG files
> for `tabbar-home-button-enabled-image' and the other tabbar buttons.
> I think I clicked on the "mode" (leftmost) button before this
> happened, but I'm not sure.
I can't reproduce this patch, but I can see how it could conceivably
happen.
Kim, could you study this patch and tell me what you think?
*** emacs/src/xdisp.c.~1.1145.~ 2007-04-09 11:36:15.0 -0400
--- emacs/src/xdisp.c 2007-04-09 12:23:04.0 -0400
***
*** 22437,22443
Lisp_Object mouse_face;
int original_x_pixel = x;
! struct glyph * glyph = NULL;
struct glyph_row *row;
if (area == ON_MODE_LINE || area == ON_HEADER_LINE)
--- 22437,22443
Lisp_Object mouse_face;
int original_x_pixel = x;
! struct glyph * glyph = NULL, * row_start_glyph = NULL;
struct glyph_row *row;
if (area == ON_MODE_LINE || area == ON_HEADER_LINE)
***
*** 22455,22461
/* Find glyph */
if (row->mode_line_p && row->enabled_p)
{
! glyph = row->glyphs[TEXT_AREA];
end = glyph + row->used[TEXT_AREA];
for (x0 = original_x_pixel;
--- 22455,22461
/* Find glyph */
if (row->mode_line_p && row->enabled_p)
{
! glyph = row_start_glyph = row->glyphs[TEXT_AREA];
end = glyph + row->used[TEXT_AREA];
for (x0 = original_x_pixel;
***
*** 22579,22590
is converted to a flatten by emacs lisp interpreter.
The internal string is an element of the structures.
The displayed string is the flatten string. */
! for (tmp_glyph = glyph - 1, gpos = 0;
! tmp_glyph->charpos >= XINT (b);
! tmp_glyph--, gpos++)
{
! if (!EQ (tmp_glyph->object, glyph->object))
! break;
}
/* Calculate the lenght(glyph sequence length: GSEQ_LENGTH) of
--- 22579,22594
is converted to a flatten by emacs lisp interpreter.
The internal string is an element of the structures.
The displayed string is the flatten string. */
! gpos = 0;
! if (glyph != row_start_glyph)
{
! for (tmp_glyph = glyph - 1;
! tmp_glyph->charpos >= XINT (b);
! tmp_glyph--, gpos++)
! {
! if (!EQ (tmp_glyph->object, glyph->object))
! break;
! }
}
/* Calculate the lenght(glyph sequence length: GSEQ_LENGTH) of
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [xft-emacs] XFT font in menu-bar
Leo skrev: [GNU Emacs 23.0.0.7 (i686-pc-linux-gnu, X toolkit) of 2007-03-29] The default menu bar in Emacs started with --enable-font-backend is using X core font. Is this a known problem? It is a known limitation. Since GTK supports XFT-fonts, I am not sure it is worth the trouble to make X/Lucid/Lesstif/Motif widgets use XFT fonts. FWIW, I caught a screen shot in XEmacs list and it seems it is possible to use XFT in Lucid menu-bar. http://people.exactcode.de/~rene/xemacs-beta-xft-off-by-one.png I'm not sure if we can use that code. Can we? Jan D. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Crash in gc_sweep (SIGH!)
Eli Zaretskii <[EMAIL PROTECTED]> writes: >> Following my last bug report on W32 display error, I noticed that >> the image didn't get through. So I tried various stuff to decode >> the base64 stuff in various ways like this: >> >> - copy it to a new file buffer named x.gif, mark it, do >> base64-decode-region, and C-c C-c to view the image (no luck!) > > This works for me, if I invoke image-toggle-display by hand (you may > need to load image-mode before that). It is bound to C-c C-c only in > buffers that visit image files. Works for me too. Could there be something wrong with your gif libraries? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
infloop in python code
In GNU Emacs 22.0.97.2 (sparc-sun-solaris2.8, X toolkit)
of 2007-04-08 on xxx
Windowing system distributor `The Cygwin/X Project', version 11.0.60899901
configured using `configure
'--prefix=/home/ruttbe/.upak-jade/installed/emacs22-pretest''
Important settings:
value of $LC_ALL: C
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: nil
locale-coding-system: nil
default-enable-multibyte-characters: t
Major mode: Python
Minor modes in effect:
show-paren-mode: t
minibuffer-electric-default-mode: t
auto-image-file-mode: t
global-auto-revert-mode: t
recentf-mode: t
display-time-mode: t
iswitchb-mode: t
shell-dirtrack-mode: t
tooltip-mode: t
mouse-wheel-mode: t
menu-bar-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
auto-compression-mode: t
column-number-mode: t
line-number-mode: t
abbrev-mode: t
Emacs infloops when I press the " key at the end of this line (to the right of
the last '(':
matching_dbs = commands.getoutput("""cat
//xx/x/x.xxx | grep "^%s" | grep -v xxx""" %
region).strip().split(
in the full file:
[EMAIL PROTECTED] ruttbe]$ cat bugreport.py
#!/usr/bin/env python
import os, os.path, sys, re, commands, logging, tempfile, datetime
import socket, string, random, time, traceback, shutil, threading, Queue
from subprocess import *
colos = [ "abc","abc",
"abc","abc",
"abc","abc",
"abc","abc",
"abc","abc",
"abc","abc" ]
mains = ["abc","abc"]
print mains+colos
d = '/tmp/-x'
if not os.access(d,os.F_OK):
os.mkdir(d)
from twisted.python.threadpool import *
tp = ThreadPool()
tp.adjustPoolsize(1,1)
q = Queue.Queue()
def handle_region(region):
f = open(os.path.join(d,region), "a")
t1 = time.time()
# pressing " key to the right of the trailing ( on the next line causes
infinite loop
matching_dbs = commands.getoutput("""cat
//xx/x/x.xxx | grep "^%s" | grep -v xxx""" %
region).strip().split(
cmd = """xxx--xx-xxx %s""" % (' '.join(['"%s"' % (x) for x in
matching_dbs]))
print cmd
p = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=STDOUT)
(cout, cin) = (p.stdout, p.stdin)
cin.close()
for line in cout:
f.write(line)
f.flush()
# if line.find('WARNING') != -1:
# print line,
print line,
cout.close()
rc = p.wait()
t2 = time.time()
if rc:
f.write('ERROR: %d calling %s\n' % (rc, cmd))
f.write('--- elapsed seconds: %.1f\n' % (t2-t1))
f.close()
q.put(region)
# tp.dispatch(None, handle_region, region)
for region in mains+colos:
tp.dispatch(None, handle_region, region)
tp.start()
try:
while 1:
region = q.get()
tp.dispatch(None, handle_region, region)
except Exception, ex:
traceback.print_exc()
tp.stop()
[EMAIL PROTECTED] ruttbe]$
Here is a debugging session that shows it (I Ctrl-C after it infloops, then hit
next a bunch of times, hoping it helps):
[EMAIL PROTECTED] ruttbe]$ dbx -c 'runargs bugreport.py; run'
/home/ruttbe/.upak-jade/commons/bin/emacs
Reading emacs
Reading ld.so.1
Reading libXaw.so.5
Reading libXmu.so.4
Reading libXt.so.4
Reading libSM.so.6
Reading libICE.so.6
Reading libXext.so.0
Reading libpng12.so.0
Reading libz.so.1
Reading libm.so.1
Reading libX11.so.4
Reading libsocket.so.1
Reading libnsl.so.1
Reading libkstat.so.1
Reading libcurses.so.1
Reading libc.so.1
Reading libdl.so.1
Reading libucb.so.1
Reading libresolv.so.2
Reading libelf.so.1
Reading libmp.so.2
Reading libc_psr.so.1
Running: emacs bugreport.py
(process id 18604)
Reading nss_files.so.1
Reading nss_dns.so.1
^Cdbx: warning: Interrupt ignored but forwarded to child.
signal INT (Interrupt) in forw_comment at line 1924 in file "syntax.c"
dbx: warning: can't find file
"/var/tmp/upak-tmp-emacs22-pretest-wS1zon/emacs-22.0.97/src/syntax.c"
dbx: warning: see `help finding-files'
(dbx) pathmap /var/tmp/upak-tmp-emacs22-pretest-wS1zon /home/ruttbe/tmp
(dbx) list
1924 c = FETCH_CHAR (from_byte);
1925 syntax = SYNTAX_WITH_FLAGS (c);
1926 code = syntax & 0xff;
1927 if (code == Sendcomment
1928 && SYNTAX_FLAGS_COMMENT_STYLE (syntax) == style
1929 && (SYNTAX_FLAGS_COMMENT_NESTED (syntax) ?
1930 (nesting > 0 && --nesting == 0) : nesting < 0))
1931 /* we have encountered a comment end of the same style
1932 as the comment sequence which began this comment
1933 section */
(dbx) where
=>[1] forw_comment(from = ???, from_byte = ???, stop = ???, nesting = ???, style
= ???, prev_syntax = ???, ch
Re: C-u C-SPC: doc string and behavior if mark = point
> From: "Drew Adams" <[EMAIL PROTECTED]> > Cc: > Date: Mon, 9 Apr 2007 07:48:48 -0700 > > You can drop "e.g.", because `C-u C-u C-@' is not an example of a double > prefix arg Actually, it _is_ an example, since C-u is only one way of supplying an argument of 16 (the code checks if it's more than 4). ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Carbon Emacs won't start when installed in certain paths
> Cannot open load file: term/mac-win [...] > This error obviously occurs before loading any user-specific settings, so > I'm not sending the Emacs debug log. Actually, this is not obvious at all to me. AFAIK the term-specific setup file (such as term/xterm or term/x-win or term/mac-win) is loaded at the very end, after site-start, .emacs, and default.el were loaded. So try it with -Q. This said, I wouldn't be surprised if building (and/or installing) doesn't work correctly in a directory whose complete filename contains spaces and/or non-ascii letters. Among other things, I seem to remember a problem where some hardcoded file names are created at dump time before the utf-8 coding system exists, so when they get used later on, they may suffer some problems. Please try and diagnosticate as much as you can, and we'll then add a note about it in PROBLEMS (at least, if that's the problem I'm thinking of, the solution is not immediate). Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
> Emacs infloops when I press the " key at the end of this line (to the right of
> the last '(':
> matching_dbs = commands.getoutput("""cat
> //xx/x/x.xxx | grep "^%s" | grep -v xxx""" %
> region).strip().split(
I assume this is using Emacs's own python.el, not python-mode.el, right?
> in the full file:
I cannot reproduce it here, sadly.
> Here is a debugging session that shows it (I Ctrl-C after it infloops,
> then hit next a bunch of times, hoping it helps):
`next' will only show tiny steps taken right after the point where
you stopped. Typically the inf-loop is much larger, so instead of `next',
use `cont' and interrupt it several times. Each time, use `xbacktrace' to
get a Lisp backtrace (or just `bt' if the Lisp backtrace seems useless).
By comparing the backtraces, we can see at which level of the callstack
happens the inf-loop.
`xbacktrace' only works under gdb (and only if you loaded
...emacs/src/.gdbinit which happens automatically if you start gdb from the
...emacs/src/ directory).
> Is there anything I can do to make this report more useful? It doesn't
> happen with emacs -q unfortunately.
Try to trim down your customization to the smallest one with which you can
still reproduce the problem.
Stefan
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
Benjamin Rutt osu.edu> writes: > Is there anything I can do to make this report more useful? It doesn't happen > with emacs -q unfortunately. hoorah, I can now dupe it with command line emacs -q --eval '(add-hook (quote python-mode-hook) (lambda () (imenu-add-menubar-index)))' --eval '(setq imenu-auto-rescan t)' bugreport.py so imenu is implicated. can anyone else dupe it now? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Carbon Emacs won't start when installed in certain paths
On 9 Apr 2007, at 20:35, Stefan Monnier wrote: So try it with -Q. OK, same story, see below. This said, I wouldn't be surprised if building (and/or installing) doesn't work correctly in a directory whose complete filename contains spaces and/or non-ascii letters. Spaces are definitely fine. Among other things, I seem to remember a problem where some hardcoded file names are created at dump time before the utf-8 coding system exists, so when they get used later on, they may suffer some problems. Please try and diagnosticate as much as you can, and we'll then add a note about it in PROBLEMS (at least, if that's the problem I'm thinking of, the solution is not immediate). When started with -nw, loading of "encoded-kb" fails, yet Emacs starts up. It is marginally usable - files can be opened (find-file) just fine from the path with the non-ASCII characters. However, calling "load-file" manually won't work (with one of those paths). In a successfully started Emacs (-Q), files from the special path can be opened (find-file) and sourced (load-file) perfectly, even though the *Completions* buffer and the entry in *Messages* will not display the right characters. I've tried this with a directory named "Täst", which shows up in Emacs as in the attached screenshot. lucy:/Applications dr$ mv Emacs.app Pour\ De\314\201veloppement/ lucy:/Applications dr$ cd Pour\ De\314\201veloppement/ lucy:/Applications/Pour DeÌveloppement dr$ ls Aquamacs Emacs Yesterday.app Emacs.app lucy:/Applications/Pour DeÌveloppement dr$ open Emacs.app/ lucy:/Applications/Pour DeÌveloppement dr$ Emacs.app/Contents/MacOS/ Emacs -Q Warning: arch-dependent data dir (/usr/local/libexec/emacs/22.0.96/ powerpc-apple-darwin7.9.0/) does not exist. Warning: arch-independent data dir (/usr/local/share/emacs/22.0.96/ etc/) does not exist. Cannot open load file: term/mac-win Start with -nw: (Emacs.app/Contents/MacOS/Emacs -debug-init) set-keyboard-coding-system: Cannot open load file: encoded-kb ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
Benjamin Rutt <[EMAIL PROTECTED]> writes:
> Emacs infloops when I press the " key at the end of this line (to the right of
> the last '(':
>
> matching_dbs = commands.getoutput("""cat
> //xx/x/x.xxx | grep "^%s" | grep -v xxx""" %
> region).strip().split(
I can't reproduce this at all. Could you try to send a smaller
testcase and give a precise recipe starting from emacs -Q?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
On 4/9/07, Stefan Monnier <[EMAIL PROTECTED]> wrote: I assume this is using Emacs's own python.el, not python-mode.el, right? yes. Try to trim down your customization to the smallest one with which you can still reproduce the problem. thanks, that did the trick, see my other post. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [xft-emacs] XFT font in menu-bar
In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes: > [GNU Emacs 23.0.0.7 (i686-pc-linux-gnu, X toolkit) of 2007-03-29] > The default menu bar in Emacs started with --enable-font-backend is > using X core font. Is this a known problem? --enable-font-backend is just to tell Emacs to use font-backend mechanism (that support both X core fonts and Xft fonts), not to tell Emacs to use only Xft fonts. For the latter, see README.unicode. In addition, as far as I know, the menu bar is impleneted by using some toolkit (gtk, lucid, or ?). I think the font used in the menu bar is decided by which toolkit you compiled Emacs with. --- Kenichi Handa [EMAIL PROTECTED] ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Screen flickers with high CPU usage in Emacs unicode 2 branch
Could someone look at this bug? It has caused hanoi, erc and emacs-w3m etc to act weirdly. -- Leo (GPG Key: 9283AA3F) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [xft-emacs] XFT font in menu-bar
On 2007-04-10, Kenichi Handa said: > In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes: > >> [GNU Emacs 23.0.0.7 (i686-pc-linux-gnu, X toolkit) of 2007-03-29] > >> The default menu bar in Emacs started with --enable-font-backend is >> using X core font. Is this a known problem? > > --enable-font-backend is just to tell Emacs to use font-backend > mechanism (that support both X core fonts and Xft fonts), not to > tell Emacs to use only Xft fonts. For the latter, see > README.unicode. > I was not clear. I mean I am using xft fonts in buffer and modeline but not in menu-bar. This has made the whole Emacs frame looks weird. > > In addition, as far as I know, the menu bar is impleneted by > using some toolkit (gtk, lucid, or ?). I think the font > used in the menu bar is decided by which toolkit you > compiled Emacs with. I am using Lucid toolkit. -- Leo (GPG Key: 9283AA3F) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
Benjamin Rutt <[EMAIL PROTECTED]> writes: > Benjamin Rutt osu.edu> writes: > >> Is there anything I can do to make this report more useful? It >> doesn't happen with emacs -q unfortunately. > > hoorah, I can now dupe it with command line > > emacs -q --eval '(add-hook (quote python-mode-hook) (lambda () > (imenu-add-menubar-index)))' --eval '(setq imenu-auto-rescan t)' > bugreport.py > > so imenu is implicated. can anyone else dupe it now? I still can't reproduce this. Is this with Emacs' built-in python.el or with the external python-mode.el? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
Benjamin Rutt <[EMAIL PROTECTED]> writes:
> Benjamin Rutt osu.edu> writes:
>
>> Is there anything I can do to make this report more useful? It
>> doesn't happen with emacs -q unfortunately.
>
> hoorah, I can now dupe it with command line
>
> emacs -q --eval '(add-hook (quote python-mode-hook) (lambda ()
> (imenu-add-menubar-index)))' --eval '(setq imenu-auto-rescan t)'
> bugreport.py
>
> so imenu is implicated. can anyone else dupe it now?
Ah yes, now I can replicate it. The trouble was that your test
program had long lines that were automatically snipped by Gnus.
Here is a simpler test case:
#!/usr/bin/env python
def foo(bar):
foo = foo("""foo""").bar("
cmd = """foo"""
bar
emacs -q foo.py
M-: (python-imenu-create-index) RET
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Crash in gc_sweep (SIGH!)
Could there be something wrong with your gif libraries? If that turns out to be the explanation, then this is not a bug in Emacs. But we might want to do something to warn people not to use that version of the gif libraries. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: infloop in python code
> Ah yes, now I can replicate it. The trouble was that your test
> program had long lines that were automatically snipped by Gnus.
>
> Here is a simpler test case:
>
> #!/usr/bin/env python
> def foo(bar):
> foo = foo("""foo""").bar("
> cmd = """foo"""
> bar
>
> emacs -q foo.py
> M-: (python-imenu-create-index) RET
This seems to be traceable to the naughty while loop in
python-end-of-block.
(catch 'done
(while (zerop (python-next-statement))
(when (or (and open (<= (current-indentation) ci))
(< (current-indentation) ci))
(python-skip-comments/blanks t)
(beginning-of-line 2)
(throw 'done t
I think something like the following fixes it (someone more
knowledgeable about this code should probably take a look).
*** emacs/lisp/progmodes/python.el.~1.57.~ 2007-04-04 13:05:27.0
-0400
--- emacs/lisp/progmodes/python.el 2007-04-09 22:42:45.0 -0400
***
*** 981,991
(_ (if (python-comment-line-p)
(python-skip-comments/blanks t)))
(ci (current-indentation))
! (open (python-open-block-statement-p)))
(if (and (zerop ci) (not open))
(not (goto-char point))
(catch 'done
! (while (zerop (python-next-statement))
(when (or (and open (<= (current-indentation) ci))
(< (current-indentation) ci))
(python-skip-comments/blanks t)
--- 981,995
(_ (if (python-comment-line-p)
(python-skip-comments/blanks t)))
(ci (current-indentation))
! (open (python-open-block-statement-p))
! opoint)
(if (and (zerop ci) (not open))
(not (goto-char point))
(catch 'done
! (setq opoint (point))
! (while (and (zerop (python-next-statement))
! (not (= opoint (point
! (setq opoint (point))
(when (or (and open (<= (current-indentation) ci))
(< (current-indentation) ci))
(python-skip-comments/blanks t)
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Carbon Emacs won't start when installed in certain paths
> On Mon, 09 Apr 2007 15:35:26 -0400, Stefan Monnier <[EMAIL PROTECTED]>
> said:
> This said, I wouldn't be surprised if building (and/or installing)
> doesn't work correctly in a directory whose complete filename
> contains spaces and/or non-ascii letters.
I think he is using Carbon Emacs with "self-contained" setting which
puts subdirectories for runtime (lisp, etc, libexec, ...) below the
Emacs.app directory so as to make the application bundle relocatable.
I'm not familiar with the self-contained setting at all (it is
designed and coded by Steven Tamm, IIUC). But I think that at least
we need to handle non-ASCII environment variables (encoded with
file-name-coding-system, not emacs-mule) such as EMACSLOADPATH in
order to deal with the case that Emacs.app is located at a non-ASCII
directory.
That requires some changes here and there. Though I just tried that,
it may not be exhaustive and I'm not sure if it is safe to use
ENCODE_FILE in init_callproc. Also, this kind of changes may not be
appropriate at this stage.
YAMAMOTO Mitsuharu
[EMAIL PROTECTED]
Index: src/callproc.c
===
RCS file: /cvsroot/emacs/emacs/src/callproc.c,v
retrieving revision 1.221
diff -c -p -r1.221 callproc.c
*** src/callproc.c 17 Feb 2007 01:59:00 - 1.221
--- src/callproc.c 10 Apr 2007 02:29:20 -
*** init_callproc_1 ()
*** 1522,1533
char *data_dir = egetenv ("EMACSDATA");
char *doc_dir = egetenv ("EMACSDOC");
Vdata_directory
! = Ffile_name_as_directory (build_string (data_dir ? data_dir
!: PATH_DATA));
Vdoc_directory
! = Ffile_name_as_directory (build_string (doc_dir ? doc_dir
!: PATH_DOC));
/* Check the EMACSPATH environment variable, defaulting to the
PATH_EXEC path from epaths.h. */
--- 1522,1541
char *data_dir = egetenv ("EMACSDATA");
char *doc_dir = egetenv ("EMACSDOC");
+ if (!data_dir) data_dir = PATH_DATA;
+ if (!doc_dir) doc_dir = PATH_DOC;
+
+ /* At this moment, we still don't know how to decode the directory
+ name. So, we keep the bytes in multibyte form so that
+ ENCODE_FILE correctly gets the original bytes. */
Vdata_directory
! = Ffile_name_as_directory (string_to_multibyte
! (make_unibyte_string (data_dir,
!strlen (data_dir;
Vdoc_directory
! = Ffile_name_as_directory (string_to_multibyte
! (make_unibyte_string (doc_dir,
!strlen (doc_dir;
/* Check the EMACSPATH environment variable, defaulting to the
PATH_EXEC path from epaths.h. */
*** init_callproc ()
*** 1605,1617
#endif
{
tempdir = Fdirectory_file_name (Vexec_directory);
! if (access (SDATA (tempdir), 0) < 0)
dir_warning ("Warning: arch-dependent data dir (%s) does not exist.\n",
Vexec_directory);
}
tempdir = Fdirectory_file_name (Vdata_directory);
! if (access (SDATA (tempdir), 0) < 0)
dir_warning ("Warning: arch-independent data dir (%s) does not exist.\n",
Vdata_directory);
--- 1613,1625
#endif
{
tempdir = Fdirectory_file_name (Vexec_directory);
! if (access (SDATA (ENCODE_FILE (tempdir)), 0) < 0)
dir_warning ("Warning: arch-dependent data dir (%s) does not exist.\n",
Vexec_directory);
}
tempdir = Fdirectory_file_name (Vdata_directory);
! if (access (SDATA (ENCODE_FILE (tempdir)), 0) < 0)
dir_warning ("Warning: arch-independent data dir (%s) does not exist.\n",
Vdata_directory);
Index: src/emacs.c
===
RCS file: /cvsroot/emacs/emacs/src/emacs.c,v
retrieving revision 1.401
diff -c -p -r1.401 emacs.c
*** src/emacs.c 3 Apr 2007 15:25:28 - 1.401
--- src/emacs.c 10 Apr 2007 02:29:20 -
*** decode_env_path (evarname, defalt)
*** 2379,2385
{
p = index (path, SEPCHAR);
if (!p) p = path + strlen (path);
! element = (p - path ? make_string (path, p - path)
: build_string ("."));
/* Add /: to the front of the name
--- 2379,2389
{
p = index (path, SEPCHAR);
if (!p) p = path + strlen (path);
! /* At this moment, we still don't know how to decode the
!directory name. So, we keep the bytes in multibyte form so
!that ENCODE_FILE correctly gets the original bytes. */
! element = (p - path
!? string_to_multibyte (make_unibyte_string (path, p - path))
: build_string ("."));
/* Add /: to
Re: [xft-emacs] XFT font in menu-bar
In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes: > > In addition, as far as I know, the menu bar is impleneted by > > using some toolkit (gtk, lucid, or ?). I think the font > > used in the menu bar is decided by which toolkit you > > compiled Emacs with. > I am using Lucid toolkit. Then, I think there's no way to make it use Xft fonts. If you like Xft fonts, how about using gtk toolkit? --- Kenichi Handa [EMAIL PROTECTED] ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Why does etags ask me if I want to keep the old TAGS - I do not want to load a new
Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I work on a software project with the source files in quite some directories. I create my TAGS table in k:/ERADIUM_kalle/LD_swmodules_005 and work in another. The first time I use "M-.", I am asked for the tags table to use. After responding to this I am taken to the definition. If I then use "M-." to get to another definition, I am asked "Keep current list of tags tables also?". If I have the *Message*-buffer in another window, I can now see this: k:/ERADIUM_kalle/LD_swmodules_005/TAGS and k:/ERADIUM_kalle/LD_SwModules_005/TAGS are the same file [2 times] If I then answer "n", I get "No tags containing ...". If I instead answer "y", I am taken to the definition. After this the tags functionality works as expected. Well, sometimes I get a file loaded in a buffer with buffername filename<2>. I have not been able to do this reproducibly yet. Confessions: Since I haven't been able to find a way to produce TAGS-tables on windows 2000 recursively, I use "ctags -e" with ctags from "http://ctags.sourceforge.net/";. Thes has worked flawlessly for me for me for years. The problems have started rather recently. k: is where my clearcase mounts are located. If Emacs crashed, and you have the Emacs process in the gdb debugger, please include the output from the following gdb commands: `bt full' and `xbacktrace'. If you would like to further debug the crash, please read the file c:/Download/emacs-070405/etc/DEBUG for instructions. In GNU Emacs 22.0.97.1 (i386-mingw-nt5.0.2195) of 2007-04-05 on E001560B82878 Windowing system distributor `Microsoft Corp.', version 5.0.2195 configured using `configure --with-gcc (3.4)' 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: SVE locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: C/l Minor modes in effect: encoded-kbd-mode: t tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t auto-compression-mode: t line-number-mode: t abbrev-mode: t Recent input: C-v C-v C-s i p M-. s w m o d u l e s _ 0 0 5 \ M-. y M-x r e p o r t SPC SPC SPC Recent messages: For information about the GNU Project and its goals, type C-h C-p. Mark saved where search started Loading etags...done Starting a new list of tags tables Note: file is write protected Mark set k:/ERADIUM_kalle/LD_swmodules_005/TAGS and k:/ERADIUM_kalle/LD_SwModules_005/TAGS are the same file [2 times] Keep current list of tags tables also? (y or n) Mark set Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [xft-emacs] XFT font in menu-bar
Kenichi Handa skrev: In article <[EMAIL PROTECTED]>, Leo <[EMAIL PROTECTED]> writes: In addition, as far as I know, the menu bar is impleneted by using some toolkit (gtk, lucid, or ?). I think the font used in the menu bar is decided by which toolkit you compiled Emacs with. I am using Lucid toolkit. Then, I think there's no way to make it use Xft fonts. If you like Xft fonts, how about using gtk toolkit? Except adding the C code that is. Jan D. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
