Re: file-attributes returns wrong info on Windows

2006-07-18 Thread Chris Britton
Eli Zaretskii writes: From: Chris Britton [EMAIL PROTECTED] Date: Mon, 17 Jul 2006 00:47:24 -0500 Cc: emacs-pretest-bug@gnu.org How do you know which one of these is wrong? What does DIR say about that file's times? ls (both cygwin and mingw) and Windows XP

Same frame-positioning bug as before: negative top/left values on Windows

2006-07-18 Thread Drew Adams
This is an old bug. I thought this was going to be fixed by Fran's bug fix, but I see that it is not. See my bug report of May 3, 2005, below. emacs -q In scratch buffer evaluate: (make-frame '((top . -1) (left . -1))) The new frame does not have its bottom at the display bottom. The frame

[Fwd: Re: [Fwd: Re: beginning-of-defun]]

2006-07-18 Thread Andreas Roehler
---BeginMessage--- Richard Stallman schrieb: Have you had experience with a lot of beginners that got confused about this? No. Just a kind of active remembering. I am not yet convinced that we should change it. Our use of the term defun for editing commands has 30 years of history behind

Re: C-M-a

2006-07-18 Thread Lennart Borgman
Andreas Roehler wrote: Emacs -q Did you try emacs -Q? Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. It works for me on w32 from 2006-07-02.

Re: tumme does not show image buffer

2006-07-18 Thread Mathias Dahl
Dieter Wilhelm [EMAIL PROTECTED] writes: emacs -D -Q --fullscreen M-x tumme dir and tumme doesn't show the *tumme* buffer only a dired buffer inhabits the screen! Strange, it does for me. But I am testing it in a terminal now. the tumme documentation string says Make a preview buffer for

RE: Same frame-positioning bug as before: negative top/left values on Windows

2006-07-18 Thread Drew Adams
You are seeing this bug because my patch to fix frame positioning with negative X/Y values on Windows has not been applied. Now that the FSF has my copyright assignment papers, they should be able to apply my patch (below). Thanks Fran. Good to hear. I thought it had already been

Re: bad syntax highlighting in shell-script mode

2006-07-18 Thread Stefan Monnier
Since $(...$(...)...) can be nested, does it mean that there's no way of highlighting it correctly using regular expressions? It's not highlighted with regular expressions (only the initial $( is matched with a regexp, the rest is handled with elisp code doing manual parsing). Stefan

Re: bad syntax highlighting in shell-script mode

2006-07-18 Thread Chris Moore
On Tue, 2006-07-18 at 10:26 -0400, Stefan Monnier wrote: It's not highlighted with regular expressions (only the initial $( is matched with a regexp, the rest is handled with elisp code doing manual parsing). Oh, good. That gives me more hope that it's possible to get this working right at

Re: bad syntax highlighting in shell-script mode

2006-07-18 Thread Chris Moore
On Tue, 2006-07-18 at 15:37 +0100, Vivek Dasmohapatra wrote: I'll see about extending the manual parser to cope with multiline-ness if you think it's worth it. I recently discovered that I rely on syntax highlighting more than I previously realised. Due to this \` problem, a large section of

Re: C-M-a

2006-07-18 Thread Stefan Monnier
Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. Probably caught by the window manager or something like that, Stefan

Re: C-M-a

2006-07-18 Thread Richard Stallman
Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. It does not fail for me, so you need to tell us how to reproduce this. Please read the Bugs section in the Emacs

Re: C-M-a

2006-07-18 Thread Andreas Roehler
Stefan Monnier schrieb: Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. Probably caught by the window manager or something like that, Stefan Of course,

sh-mode font-lock error

2006-07-18 Thread Glenn Morris
The (unintended?) change to sh-font-lock-keywords-1 in rev 1.182 of sh-script.el breaks font-locking, eg of bash scripts: emacs -q --no-site-file M-x sh-mode then type export - Error during redisplay: (error No match 4 in highlight (4 font-lock-builtin-face)) Reverting from (4

Re: C-M-a

2006-07-18 Thread Dieter Wilhelm
Andreas Roehler [EMAIL PROTECTED] writes: Emacs -q Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. With yesterdays CVS update it works for me emacs -q C-h k C-M-a GNU

Re: bad syntax highlighting in shell-script mode

2006-07-18 Thread Stefan Monnier
Since $(...$(...)...) can be nested, does it mean that there's no way of highlighting it correctly using regular expressions? It's not highlighted with regular expressions (only the initial $( is matched with a regexp, the rest is handled with elisp code doing manual parsing). I'll see

Re: sh-mode font-lock error

2006-07-18 Thread Glenn Morris
Stefan Monnier wrote: Thanks. I've reverted it. It's actually a patch I had suggested (mistakenly as I know see) and was waiting for confirmation that it fixes another bug. So, back to that other bug, Thanks. I get the impression (catching up on emacs mailing lists) you are trying to fix

Re: sh-mode font-lock error

2006-07-18 Thread Stefan Monnier
Thanks. I get the impression (catching up on emacs mailing lists) you are trying to fix font-locking of quoted and nested things. FYI, the following (not uncommon, I would have thought) construct currently does not fontify correctly. I'm pretty sure it used to... #!/bin/bash echo the time

Re: C-M-a

2006-07-18 Thread Andreas Roehler
Dieter Wilhelm schrieb: Andreas Roehler [EMAIL PROTECTED] writes: Emacs -q Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. With yesterdays CVS update it works for