- Update SGML tag list
- Allow custom specification of line length (-L)
- Performance improvements in various areas
- Add various commonly misspelled words
- Add the igor(1) manual page
- Allow custom specification of line ranges to check (-C)
- while here... drop bsd.port.pre.mk uncessary inclusion in favor of bpm
PR: ports/165286
Submitted by: gjb
This package includes the full libyaml C library version 0.1.2 by Kirill
Simonov in the package so you don't need to worry about any non-Haskell
dependencies.
WWW: http://github.com/snoyberg/yaml/
Obtained from: FreeBSD Haskell
based on the datatypes found in the xml-types package. This package is
broken up into the following modules:
* Text.XML: DOM-based parsing and rendering. This is the most commonly
used module.
* Text.XML.Cursor: A wrapper around Text.XML which allows bidirectional
traversing of the DOM, similar to XPath.
* Text.XML.Unresolved: A slight modification to Text.XML which does not
require all entities to be resolved at parsing. The datatypes are
slightly more complicated here, and therefore this module is only
recommended when you need to deal directly with raw entities.
* Text.XML.Stream.Parse: Streaming parser, including some streaming
parser combinators.
* Text.XML.Stream.Render: Streaming renderer.
WWW: http://github.com/snoyberg/xml
Obtained from: FreeBSD Haskell
Apply rejected patches and perform word-wise diffs.
The main function of wiggle is to apply a patch to a file in a similar
manner to the patch(1) program.
The distinctive difference of wiggle is that it will attempt to apply a
patch even if the before part of the patch doesn't match the target
file perfectly. This is achieved by breaking the file and patch into
words and finding the best alignment of words in the file with words in
the patch. Once this alignment has been found, any differences (word-
wise) in the patch are applied to the file as best as possible.
manner to the patch(1) program.
The distinctive difference of wiggle is that it will attempt to apply a
patch even if the before part of the patch doesn't match the target
file perfectly. This is achieved by breaking the file and patch into
words and finding the best alignment of words in the file with words in
the patch. Once this alignment has been found, any differences (word-
wise) in the patch are applied to the file as best as possible.
- No PORTREVISION bump because the port has been broken with NOPORTDOCS set
PR: ports/164945
Submitted by: scheidell (me)
Approved by: skv (maintainer, via private mail), gabor (mentor)
