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

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

[debbugs-tracker] bug#15089: closed (awk-mode indentation of line after


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#15089: closed (awk-mode indentation of line after /= statement with comment)
Date: Sun, 25 Aug 2013 10:21:02 +0000

Your message dated Sun, 25 Aug 2013 10:18:59 +0000
with message-id <address@hidden>
and subject line Re: bug#15089: awk-mode indentation of line after /= statement 
with comment
has caused the debbugs.gnu.org bug report #15089,
regarding awk-mode indentation of line after /= statement with comment
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
15089: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15089
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: awk-mode indentation of line after /= statement with comment Date: Tue, 13 Aug 2013 15:08:18 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Package: emacs,cc-mode
Version: 24.3
Severity: minor

emacs -Q foo.awk

Enter buffer contents:

#!/usr/bin/gawk -f
BEGIN {
   x = 4
   x /= 2    # comment
        y = 3
   print x, y
}

Use TAB to indent each line. The "y =" line is indented too much.
No such problem with +=, -=, etc; only with /=. And only if a comment
after if (actually, only if whitespace after "/= 2", it seems).



--- End Message ---
--- Begin Message --- Subject: Re: bug#15089: awk-mode indentation of line after /= statement with comment Date: Sun, 25 Aug 2013 10:18:59 +0000 User-agent: Mutt/1.5.21 (2010-09-15)
Hi, Glenn.

Bug fixed.

On Tue, Aug 20, 2013 at 02:57:25AM -0400, Glenn Morris wrote:

> It works thank you. It introduces a new compiler warning, if you're
> interested in such things:

>   progmodes/cc-awk.el:1150:1:Warning: the function `c-forward-sws' is not
>   known to be defined

Wierd.  "sws" stands for "syntactic whitespace" and the function is used
all over the place, even though its use is generated from a macro.
Dealing with the compiler warnings is on my (long) TODO list.

-- 
Alan Mackenzie (Nuremberg, Germany).


--- End Message ---

reply via email to

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