From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24671@debbugs.gnu.org
Subject: bug#24671: java-mode confused by non-trivial generics
Date: 27 Jul 2019 14:14:24 -0000 [thread overview]
Message-ID: <20190727141424.74896.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.2400.1564236126.2688.bug-gnu-emacs@gnu.org>
Hello, Lars
In article <mailman.2400.1564236126.2688.bug-gnu-emacs@gnu.org> you wrote:
> Daniel Colascione <dancol@dancol.org> writes:
>> For the following code
>>
>> class Foo {
>> public List<Class<? extends Bar<? extends Qux>>> getBars() {
>> return null;
>> }
>> }
>>
>> I expect the `<' and `>' to be assigned paren syntax, but they are not. Emacs
>> is latest master.
> When I try this in Emacs 27, the < and > characters are fontied the same
> way as the parentheses in the example, so I'm guessing that this has
> been fixed and is closing this bug report. If you're still seeing this
> problem, please reopen.
I think the bug should be reopened: it was about the syntax on < and >
rather than the fontification.
If you put point in front of any of the <s, you should be able to
execute C-M-f, moving to the matching >.
This doesn't happen in the current scenario because the closing >s,
written without intervening spaces, get confused with the Java shift
right operator ">>>". If you insert a space into that triplet, the
syntax comes back again.
This will be easy to fix.
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-07-27 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 0:23 bug#24671: java-mode confused by non-trivial generics Daniel Colascione
2019-07-27 14:01 ` Lars Ingebrigtsen
[not found] ` <mailman.2400.1564236126.2688.bug-gnu-emacs@gnu.org>
2019-07-27 14:14 ` Alan Mackenzie [this message]
2019-07-27 15:11 ` Lars Ingebrigtsen
2019-07-27 16:36 ` Alan Mackenzie
2019-07-28 9:43 ` Lars Ingebrigtsen
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=20190727141424.74896.qmail@mail.muc.de \
--to=acm@muc.de \
--cc=24671@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).