From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, Carlos <carlos@cvkm.cz>,
Yuan Fu <casouri@gmail.com>
Cc: 69571@debbugs.gnu.org
Subject: bug#69571: 29.2; csharp-mode indentation: Misaligned closing brace in blocks starting below "new"
Date: Sun, 10 Mar 2024 20:21:32 +0100 [thread overview]
Message-ID: <87zfv5riyr.fsf@thornhill.no> (raw)
In-Reply-To: <86zfv7yf3t.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 5 Mar 2024 22:09:51 +0100
>> From: Carlos <carlos@cvkm.cz>
>>
>> Any block starting on the line immediately below a line having the
>> string "new" will have its closing brace aligned with the opening one.
>>
>> See the following code:
>>
>> public class Foo {
>> void Bar () {
>> var x = new X(); // [1]
>> for (;;) {
>> x();
>> } // [2]
>> }
>> }
>>
>> Line [1] says "new". The closing brace in line [2] is aligned to the
>> opening brace.
>>
>> If you comment out the "new" (or the whole line) the problem persists.
>>
>> If you remove the "new" the problem goes away and [2] is correctly
>> aligned.
>>
>> If you insert a line between line [1] and the one having the opening
>> brace the problem goes away.
>
> Theo and Yuan, could you please look into this?
I have a working patch for this, but I'd like to expand it to cover an
edge case for which I'm unable to find a good solution. Can you suggest
a way around this edge case?
Consider the provided code:
```
public class Foo {
void Bar () {
var x = new X(); // [1]
for (;;) {
x();
} // [2]
}
}
```
Like this, the below patch doesn't work. If you remove the first
comment, the patch works.
```
public class Foo {
void Bar () {
var x = new X();
for (;;) {
x();
} // [2]
}
}
```
The reason is simple, of course. What I'm struggling with here is how to
best handle the case where there is a comment ending the line, possibly
containing a ';' itself. I've tried some variations with save-excursion
along with syntax-ppss to detect whether or not we're in a comment, but
it gets verbose and ugly. Is there some simple way to do this check in
Emacs, or should I just resort to making some best effort judgement call
here?
Thanks,
Theo
diff --git a/lisp/progmodes/csharp-mode.el b/lisp/progmodes/csharp-mode.el
index 7bf57bcbe21..00278e18e51 100644
--- a/lisp/progmodes/csharp-mode.el
+++ b/lisp/progmodes/csharp-mode.el
@@ -495,9 +495,10 @@ csharp-guess-basic-syntax
(unless (eq (char-after) ?{)
(ignore-errors (backward-up-list 1 t t)))
(save-excursion
- ;; 'new' should be part of the line
+ ;; 'new' should be part of the line, but should not trigger if
+ ;; statement has already ended, like for 'var x = new X();'.
(goto-char (c-point 'iopl))
- (looking-at ".*new.*")))
+ (looking-at ".*new.*[^;]$")))
;; Line should not already be terminated
(save-excursion
(goto-char (c-point 'eopl))
next prev parent reply other threads:[~2024-03-10 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 21:09 bug#69571: 29.2; csharp-mode indentation: Misaligned closing brace in blocks starting below "new" Carlos
2024-03-09 8:38 ` Eli Zaretskii
2024-03-09 9:13 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-10 19:21 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-16 11:19 ` Eli Zaretskii
2024-03-16 17:01 ` Dmitry Gutov
2024-03-16 17:25 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 19:45 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 20:11 ` Eli Zaretskii
2024-03-30 12:15 ` Mattias Engdegård
2024-03-30 12:30 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 8:57 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 9:42 ` Mattias Engdegård
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfv5riyr.fsf@thornhill.no \
--to=bug-gnu-emacs@gnu.org \
--cc=69571@debbugs.gnu.org \
--cc=carlos@cvkm.cz \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=theo@thornhill.no \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.