Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43077 - [highlight] doesn't work for haskell

Attached to Project: Community Packages
Opened by Collin J. Doering (rekahsoft) - Thursday, 11 December 2014, 12:21 GMT
Last edited by Florian Pritz (bluewind) - Friday, 12 December 2014, 10:22 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When using the highlight binary included with the highlight package on any haskell file (or atleast the bunch I tried) it fails with various errors. Mostly of the form (just on various line numbers): highlight: Lua error ( /usr/share/highlight/langDefs/haskell.lang:54: unfinished string near '"' ) in haskell.lang

I include a patch for /usr/share/highlight/langDefs/haskell.lang which rectifys the problem.

Additional info:
* package version(s)
3.19-1
* config and/or log files etc.
Happens with default configuration

Steps to reproduce:
1. Install highlight from community.
2. Use the highlight binary to highlight a haskell file (outputing to any format)
   haskell.lang.patch (0.5 KiB)
This task depends upon

Closed by  Florian Pritz (bluewind)
Friday, 12 December 2014, 10:22 GMT
Reason for closing:  Upstream
Comment by Florian Pritz (bluewind) - Thursday, 11 December 2014, 15:46 GMT
Please contact upstream via <http://sourceforge.net/p/syntaxhighlight/bugs/?source=navbar>.
Comment by Florian Pritz (bluewind) - Thursday, 11 December 2014, 15:56 GMT
I should probably clarify this a little more: We (Arch Linux package maintainers) try to change software as little as possible and we normally only fix bugs related to the way we package things. Since this is a bug in the software rather than our package it should be fixed upstream in order to minimize our work and the possibility that we cause other bugs because we don't know the software we would patch. Also if it's fixed upstream other distros will benefit from the fix as well.

Loading...