unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 15465@debbugs.gnu.org
Subject: bug#15465: CC-mode misaligns enums that implement an interface in Java
Date: Mon, 14 Oct 2013 11:19:39 +0200	[thread overview]
Message-ID: <CAG7BpaphD8Hkq=6wEyM6SUY-ozxSqgTfPCurMimSwRkvdUZtwQ@mail.gmail.com> (raw)
In-Reply-To: <20131013213838.GB2498@acm.acm>

[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

Um, it seems to be worse than before. I guess your first patch worked
better, at least for my cases.

E.g. now I have:

public enum X implements Y, Z
{
    A,
        B;
}

On a side note, enum methods (and constructors --- yes, enums can
optionally have those) are fontified as variable names, though that is of
course less important than indentation.

Paul


On 13 October 2013 23:38, Alan Mackenzie <acm@muc.de> wrote:

> Hello, Paul.
>
> On Mon, Sep 30, 2013 at 09:23:53AM +0200, Paul Pogonyshev wrote:
> > Sorry, it doesn't apply.
>
> I don't understand what's gone wrong here.  Anyway, I've just committed
> that patch to the Emacs trunk (revision #114650).  Perhaps you could try
> out this latest fix too, and let me know if there are any more problems
> in this area.  Thanks!
>
> > Paul
>
> --
> Alan Mackenzie (Nuremberg, Germany).
>
>
> > On 29 September 2013 17:03, Alan Mackenzie <acm@muc.de> wrote:
> >
> > > On Sat, Sep 28, 2013 at 09:15:52PM +0200, Paul Pogonyshev wrote:
> > > > > I've committed a fix, revision #114474, to the bzr trunk.  Could
> > > > > you try out the change, please, and either confirm it fixes the
> > > > > bug properly, or tell me what hasn't yet been fixed.
> > >
> > > > Thank you. The case I initially mentioned works properly now, also
> with
> > > > multiple implemented interfaces. However, it seems to not know about
> > > > interfaces with generics:
> > >
> > > > public enum X implements Y <Z>
> > > > {
> > > >     A,
> > > >         B;
> > > > }
> > >
> > > Here's a better patch than the one from last night, which was
> > > demonstrably buggy.  It should apply cleanly to the current trunk.
> > > Please let me know how thoroughly it works.
> > >
> > >
>

[-- Attachment #2: Type: text/html, Size: 2588 bytes --]

  reply	other threads:[~2013-10-14  9:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26  8:31 bug#15465: CC-mode misaligns enums that implement an interface in Java Paul Pogonyshev
2013-09-28 17:33 ` Alan Mackenzie
2013-09-28 19:15   ` Paul Pogonyshev
2013-09-28 21:33     ` Alan Mackenzie
2013-09-29 15:03     ` Alan Mackenzie
2013-09-30  7:23       ` Paul Pogonyshev
2013-10-13 21:38         ` Alan Mackenzie
2013-10-14  9:19           ` Paul Pogonyshev [this message]
2013-10-20 14:37             ` Alan Mackenzie
2013-10-21 11:00               ` Paul Pogonyshev
2013-10-25 20:29                 ` 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='CAG7BpaphD8Hkq=6wEyM6SUY-ozxSqgTfPCurMimSwRkvdUZtwQ@mail.gmail.com' \
    --to=pogonyshev@gmail.com \
    --cc=15465@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).