emacs-unicode-2: `read-file-name' doesn't complete chinese dir names

2006-11-10 Thread Zhang Wei
Make some chinese directory names in /tmp, eval: (read-file-name "input" "/tmp/" "/tmp/") and press , the chinese directory names are listed with out any problem. but eval: (read-file-name "input" "/tmp/" "/tmp/" nil nil 'file-directory-p) and press , this time the chinese directory names a

Re: Crash with mouse-avoidance-mode

2006-11-10 Thread Klaus Zeitler
> "Kim" == Kim F Storm <[EMAIL PROTECTED]> writes: Kim> Kim> Did we ever look at this bug? Kim> Kim> Does it still happen? IIRC that was fixed by Chong and it did work in September. I gave up on using mouse-avoidance-mode a few weeks ago, since it was more often a nuisance th

Re: comint.el: EMACS environment variable

2006-11-10 Thread Chong Yidong
Richard Stallman <[EMAIL PROTECTED]> writes: > So we should simply tell whichever programs look for EMACS=t to change? > > I think that is the right thing to do. > > Another possibility is to switch to a different envvar name, but I > think that would make an even bigger transient. OK. I'll

Re: comint.el: EMACS environment variable

2006-11-10 Thread Stefan Monnier
> So we should simply tell whichever programs look for EMACS=t to change? > I think that is the right thing to do. > Another possibility is to switch to a different envvar name, but I > think that would make an even bigger transient. I don't think it'll be much bigger. And it has the benefit

Re: Lisp backtrace

2006-11-10 Thread Stefan Monnier
> When debug-on-error is enabled and an error occurs, a backtrace is > generated. Clicking on a function in the stack opens a buffer with the > cursor at the start of the function. It would be more useful to place the > cursor at the point of execution within that function. Patch welcome for thi

Re: Lisp backtrace

2006-11-10 Thread Lennart Borgman
Stefan Monnier wrote: When debug-on-error is enabled and an error occurs, a backtrace is generated. Clicking on a function in the stack opens a buffer with the cursor at the start of the function. It would be more useful to place the cursor at the point of execution within that function.

Re: Lisp backtrace

2006-11-10 Thread Richard Stallman
When debug-on-error is enabled and an error occurs, a backtrace is generated. Clicking on a function in the stack opens a buffer with the cursor at the start of the function. It would be more useful to place the cursor at the point of execution within that function. There is no

Re: Slow operations on buffers of tens of megabytes

2006-11-10 Thread Richard Stallman
It works in that it does speed up entering in new folders. However, it breaks mail splitting in that, at the time buffers are to be saved, vc-before-save ends up trying to require vc-RCS, so newly-split e-mail is not saved, remaining in open modified buffers until I override vc

Re: comint.el: EMACS environment variable

2006-11-10 Thread Chong Yidong
Stefan Monnier <[EMAIL PROTECTED]> writes: > Otherwise you get problem that when SWI-Prolog is run from a > Makefile that sets EMACS to "emacs" (or somesuch) it'll think it's > running inside Emacs. Such circumstances are probably negligibly rare: interactive programs (which should be the only on

[emacs-unicode-2] Tutorial bug

2006-11-10 Thread Leo
Hi there, 'C-h t' won't be able to open anything in Emacs unicode-2 branch. It seems most of the functions regarding tutorial have been moved to tutorial.el. This is tested in: GNU Emacs 23.0.0.8 (i686-pc-linux-gnu, GTK+ Version 2.8.20) of 2006-11-08 Regards, -- Leo _

Re: Lisp backtrace

2006-11-10 Thread Nick Roberts
> When debug-on-error is enabled and an error occurs, a backtrace is > generated. Clicking on a function in the stack opens a buffer with the > cursor at the start of the function. It would be more useful to place > the cursor at the point of execution within that function. >

Re: comint.el: EMACS environment variable

2006-11-10 Thread Stefan Monnier
>> Otherwise you get problem that when SWI-Prolog is run from a >> Makefile that sets EMACS to "emacs" (or somesuch) it'll think it's >> running inside Emacs. > Such circumstances are probably negligibly rare: interactive programs > (which should be the only ones that care about the EMACS envvar)

Re: [emacs-unicode-2] Tutorial bug

2006-11-10 Thread Lennart Borgman
Leo wrote: Hi there, 'C-h t' won't be able to open anything in Emacs unicode-2 branch. It seems most of the functions regarding tutorial have been moved to tutorial.el. This is tested in: GNU Emacs 23.0.0.8 (i686-pc-linux-gnu, GTK+ Version 2.8.20) of 2006-11-08 Regards, Can you please tel

Re: problems building on OSF1

2006-11-10 Thread Anselm Helbig
Sorry for the delay and for messing up the threading, I'm afraid my spamfilter ate your last mail, Eli. > Oops, sorry, my faulty memory tricked me. You are right, the > configure script doesn't test for the IPv6 support, it assumes that > any system that has AF_INET6 defined in its system header

Re: Slow operations on buffers of tens of megabytes

2006-11-10 Thread Reiner Steib
On Fri, Nov 10 2006, Richard Stallman wrote: > It works in that it does speed up entering in new folders. > > However, it breaks mail splitting [...] > > That is a bad bug; was this patch installed? No, I didn't install this patch. I don't use the nnfolder back end of Gnus, so I can't re

Re: comint.el: EMACS environment variable

2006-11-10 Thread Richard Stallman
OK. I'll email the SWI Prolog people to get them to make that change, and remove this item from FOR-RELEASE. Could you please add an item about this in etc/PROBLEMS? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu

Re: comint.el: EMACS environment variable

2006-11-10 Thread Richard Stallman
> Another possibility is to switch to a different envvar name, but I > think that would make an even bigger transient. I don't think it'll be much bigger. And it has the benefit of being cleaner. Let's set another envvar now, and suggest that other programs switch to it gradually