bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#2729: marked as done (23.0.90; file-modes-symbolic-to-number: Parse


From: Emacs bug Tracking System
Subject: bug#2729: marked as done (23.0.90; file-modes-symbolic-to-number: Parse error in modes near `g=')
Date: Sat, 21 Mar 2009 16:00:03 +0000

Your message dated Sat, 21 Mar 2009 11:56:29 -0400
with message-id <87ab7ena36.fsf@cyd.mit.edu>
and subject line Re: 23.0.90; file-modes-symbolic-to-number: Parse error in 
modes near `g='
has caused the Emacs bug report #2729,
regarding 23.0.90; file-modes-symbolic-to-number: Parse error in modes near `g='
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
2729: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2729
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
--- Begin Message --- Subject: 23.0.90; file-modes-symbolic-to-number: Parse error in modes near `g=' Date: Fri, 20 Mar 2009 17:41:00 +0100
When I use dired-do-chmod to change file modes with an argument like
`g=', I get the error message

Parse error in modes near `g='

There is no such error with GNU Emacs 22.2.

In GNU Emacs 23.0.90.1 (i686-pc-linux-gnu, GTK+ Version 2.14.4)
 of 2009-02-23 on regnitz
Windowing system distributor `The X.Org Foundation', version 11.0.10502000



--- End Message ---
--- Begin Message --- Subject: Re: 23.0.90; file-modes-symbolic-to-number: Parse error in modes near `g=' Date: Sat, 21 Mar 2009 11:56:29 -0400
> When I use dired-do-chmod to change file modes with an argument like
> `g=', I get the error message
>
> Parse error in modes near `g='

I've checked in a fix.  Thanks for the report.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]