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

Bug#651871: marked as done (Syntax highlighting missed end of comments: /* **/)

Your message dated Fri, 15 Jan 2021 20:23:25 -0500
with message-id <87sg71ptde.fsf@DigitalMercury.dynalias.net>
and subject line Re: scala-mode-el: Syntax highlighting missed end of comments: /* **/
has caused the Debian Bug report #651871,
regarding Syntax highlighting missed end of comments: /* **/
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@bugs.debian.org
immediately.)


-- 
651871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651871
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: scala-mode-el
Version: 20111005-1
Severity: minor
Tags: upstream

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I've encountered this issue with the file project/Sbt.scala in sbt. The syntax
highlighting misses the end of comments of the form /* **/ so that the rest of
the file is highlighted as comment.

This can be reproduced with a two liner scala file:
/* **/
val hello="world"

Regards, Thomas Koch

- -- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages scala-mode-el depends on:
ii  emacs [emacsen]    23.3+1-4
ii  emacs23 [emacsen]  23.3+1-4

scala-mode-el recommends no packages.

scala-mode-el suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJO5lBEAAoJEAf8SJEEK6ZaBtIQAMaUXWol+kAjKACceSzi0tnM
/vyIiopxH+OapCZYRmrsYxXPwemeoLXKp02WJov9oxhqtkjq/JT79bNrayuTNwhN
s2qGEagQchCRf2j+A3ZbHkU9t6eoDbLllZ4gVuwNSgXqi5aqqLIawK63fdL46J54
FCD3KuZwhFkc88reMZuRYWz2W/spTvjQ7ZvOs87AUUvRaUsFd4NZCt516PX3yf4S
gCz+1yPSYpqNgnATj06sLy6F/J4JzilpJuiT62EOfkeGWwihXMr/kVOCuyt6iqzU
fIo3T/hfeV2pQdb2esd77kwx3iS0/5aZIKbFE8F3SneFx9Su15YWJ80IVdFv27xY
OnRiTh5NC3/SnBNx3lGSAAxuATdkVYc5HOGpHkLT9XJb7M6DKY8/DHrF7Q9VbAPa
O4eY6tK7ZyQoGjg2nuRW4d+rNnweltswvSDoaj2/rT6RFq4TQy6xIRutZBdHMiL8
GDsMwuDOGAkEAs8uwlDa4xgge9u2B7lIPpa6wYWtFF+cGZvYNKt3L2Q6ZPr1rYGC
7BZdkoNxJpPn6jqfXb5OQ4KtEoSTbmNewtEWtzsZlj8ZMNy9VeY9Tlm//8w/6JjJ
0F27Eef6MZ6p2YZ5OpPmdyWWIDPCyCGA7SdSTJ1HwnL28rFxdOTeQE27YUDqJgQf
NMVik1uYeccIlOjzWI1J
=bcC6
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 1:1.1.0-1

Hi Thomas,

This bug doesn't exist in the current release, so I'm marking it as
fixed and am closing it.

Regards,
Nicholas

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: