On Fri, Aug 24, 2018 at 05:53:17PM -0400, Bill Ricker wrote:
> *DISCUSSION*
> Since we primarily position Ack as a programmer's code search / spelunking
> tool, I'm not confident we'll accept a feature request to enable
> UTF-16/UCS-2 and auto-detection via BOM of 8/16/32 and BE/LE ... but I'm
> tempted to try anyway; no promises!
FWIW while I do mostly use ack for grovelling over code, I also use it
for grovelling over documentation and config data, both of which can
contain non-ASCII code points. Thankfully *I* only have to work (at
least currently) with utf8 and ascii documentation and data, but I can
imagine that there are poor souls out there working with other
encodings.
I'd love to see ack spawn something like an --encoding=utf-16 tentacle,
with maybe an --encoding=automatic that could be stuffed into a .ackrc.
--
David Cantrell | Cake Smuggler Extraordinaire
Immigration: making Britain great since AD43
--
You received this message because you are subscribed to the Google Groups "ack
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/ack-users.
For more options, visit https://groups.google.com/d/optout.
