GNOME Bugzilla – Bug 412587
Syntax highlighting 8085 assembly
Last modified: 2021-07-05 11:02:24 UTC
We have recently changed our 8085 simulator application to use gtksourceview as editor component. (http://sourceforge.net/projects/gnusim8085/)
In this process we have created a .lang file for 8085 assembly and we will be glad if it gets included in gtksourceview official distribution.
I will attach the file to the bug.
Created attachment 83452 [details]
8085 assembly .lang file
# Onkar Says:
June 19th, 2007 at 12:39 pm
I had submitted a .lang file for syntax highlighting. I don’t know if it ever got accepted. I have no objection for using it under LGPL if you want. The tracker bug is http://bugzilla.gnome.org/show_bug.cgi?id=412587
Also let me know if you want the file in new format. gnusim8085 uses gtksourceview1 as editing component. If the .lang file becomes part of gtksourceview it will be helpful.
About new/old format, it's not a problem, we have a converter anyway. I believe the problem is that there is no nice way to know when a file has [insert-vendor-here] assembly format because there are way to many different assemblies, and gtksourceview prefers to have lang files bound to mime types (I think there are other assmbly lang files in bugzilla somewhere).
I think it makes sense to ship mime-type-less lang files if they are going to be used by people. User will have to modify his mime database or something, but at least he won't have to hunt for lang file on internet. Then some nice editors make it possible to specify language right in the file or specify mapping between extension/glob/whatever and lang, so mime isn't needed.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
and create a new ticket at
Thank you for your understanding and your help.