unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: OFFICE ZERO <hi-oh230@air.ocn.ne.jp>
To: "Chong Yidong" <cyd@stupidchicken.com>, <636@emacsbugs.donarmstrong.com>
Subject: bug#636: Please fix before the release of 23.1
Date: Mon, 11 Aug 2008 09:50:33 +0900	[thread overview]
Message-ID: <003801c8fb4c$5f91b510$0100a8c0@yourhigxg9gyo4> (raw)
In-Reply-To: 87ljz45xfj.fsf@stupidchicken.com

Do not send any mail1!
no thank you



----- Original Message ----- 
From: "Chong Yidong" <cyd@stupidchicken.com>
To: "Ulrich Mueller" <ulm@gentoo.org>
Cc: "Michael Olson" <mwolson@gnu.org>; <636@emacsbugs.donarmstrong.com>; 
"Alan Mackenzie" <acm@muc.de>; <emacs-devel@gnu.org>
Sent: Monday, August 11, 2008 7:15 AM
Subject: bug#636: Please fix before the release of 23.1


> Ulrich Mueller <ulm@gentoo.org> writes:
>
>>>>>>> On Sun, 10 Aug 2008, I wrote:
>>
>>> ,----[ test.el ]
>>> | (progn
>>> |   (require 'cc-mode))
>>> `----
>>
>>> $ emacs -Q test.el
>>> M-x eval-buffer
>>
>>> This will result in an error: Invalid read syntax: ")"
>>
>> The problem goes away if I revert the following change:
>>
>> 2008-06-27  Alan Mackenzie  <acm@muc.de>
>>
>> * progmodes/cc-defs.el (c-emacs-features): New feature
>> 'argumentative-bod-function.
>
> Thanks for pinpointing this.
>
> In fact, it's apparently not a problem with cc-mode, but with Emacs.
> Here's a stripped-down recipe:
>
> 1. Create a file foo.el in your lisp path with the following contents:
>
> (defconst foo
>  (let ((beginning-of-defun-function
> (lambda (&optional arg)
>    (not (eq arg nil)))))
>    (progn
>      (beginning-of-defun 1))))
>
> (provide 'foo)
>
> 2. Byte-compile it (M-x byte-compile-file RET).
>
> 3. Create a file test.el with the following contents:
>
> (progn
>  (require 'foo))
>
> 4. emacs test.el
>
> 5. M-x eval-buffer
>
> Debugger entered--Lisp error: (invalid-read-syntax ")")
>  eval-buffer()  ; Reading at buffer position 25
>  call-interactively(eval-buffer t nil)
>  execute-extended-command(nil)
>  call-interactively(execute-extended-command nil nil)
>
>
> I don't know what causes this bug, though.  Anyone?
>
>
>
> 







  parent reply	other threads:[~2008-08-11  0:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877ibp4hh3.fsf@vorlon.ganneff.de>
     [not found] ` <871w1xfmsb.fsf@grepfind.mwolson.org>
     [not found]   ` <87ljzj3oad.fsf_-_@grepfind.mwolson.org>
     [not found]     ` <mkiqu9g039.fsf@fencepost.gnu.org>
     [not found]       ` <18590.45488.891078.545308@a1ihome1.kph.uni-mainz.de>
     [not found]         ` <18590.47471.82980.734389@a1ihome1.kph.uni-mainz.de>
2008-08-10 18:55           ` bug#636: Please fix before the release of 23.1 Glenn Morris
2008-08-11  1:06             ` OFFICE ZERO
2008-08-10 22:15           ` Chong Yidong
     [not found]           ` <87ljz45xfj.fsf@stupidchicken.com>
2008-08-10 22:18             ` Chong Yidong
     [not found]             ` <87abfkv7ix.fsf@stupidchicken.com>
2008-08-11  0:50               ` OFFICE ZERO
     [not found]                 ` <handler.636.B636.121841588021215.ackinfo@emacsbugs.donarmstrong.com>
2008-08-11  1:16                   ` bug#636: Info received (bug#636: Please fix before the release of 23.1) OFFICE ZERO
2008-08-11  0:50             ` OFFICE ZERO [this message]
     [not found]               ` <handler.636.B636.121841588221220.ackinfo@emacsbugs.donarmstrong.com>
2008-08-11  1:16                 ` OFFICE ZERO
2008-08-11  7:18             ` bug#636: Please fix before the release of 23.1 Ulrich Mueller
     [not found]             ` <18591.59359.40969.641357@a1ihome1.kph.uni-mainz.de>
2008-08-11  8:47               ` Alan Mackenzie
     [not found]               ` <20080811084708.GA3219@muc.de>
2008-08-11  8:54                 ` Andreas Schwab
     [not found]                 ` <jed4kgc4nw.fsf@sykes.suse.de>
2008-08-11 18:50                   ` Alan Mackenzie
2008-08-11 15:26               ` Michael Olson
2008-08-11 16:30               ` Chong Yidong
     [not found]               ` <87fxpb5xbn.fsf@stupidchicken.com>
2008-08-11 19:01                 ` Alan Mackenzie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003801c8fb4c$5f91b510$0100a8c0@yourhigxg9gyo4' \
    --to=hi-oh230@air.ocn.ne.jp \
    --cc=636@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).