| 1 |
On 07/06/15 22:22, Michał Górny wrote: |
| 2 |
> Dnia 2015-06-07, o godz. 22:16:18 |
| 3 |
> "Justin Lecher (jlec)" <jlec@g.o> napisał(a): |
| 4 |
> |
| 5 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
| 6 |
>> Hash: SHA512 |
| 7 |
>> |
| 8 |
>> On 07/06/15 14:48, Andrew Udvare wrote: |
| 9 |
>>> On 07/06/15 05:12, Alexis Ballier wrote: |
| 10 |
>>>> On Sat, 6 Jun 2015 22:00:14 -0400 Mike Gilbert |
| 11 |
>>>> <floppym@g.o> wrote: |
| 12 |
>>>> |
| 13 |
>>>>> Compatibility with sed scripts is not something I care about. |
| 14 |
>> ... |
| 15 |
>>> However, I do not disagree an XML parser is better than sed for |
| 16 |
>>> the purpose. There are plenty of XML pretty printers. |
| 17 |
>>> |
| 18 |
>> |
| 19 |
>> So you guys think I am using sed for this? Really? |
| 20 |
>> |
| 21 |
>> Still you need to tell a XML formatter what indention style to use. |
| 22 |
> |
| 23 |
> Not exactly. You can write a tool that tries hard to recognize |
| 24 |
> indentation style and repeat it. Like the one I wrote to replace |
| 25 |
> <herd/> with <maintainer/> elements. It was pretty good in figuring out |
| 26 |
> developer fancies, including multiple different indentation levels. |
| 27 |
> |
| 28 |
|
| 29 |
I am trying to detect what ever they already is for indention. How did you |
| 30 |
implement this? |
| 31 |
|
| 32 |
Justin |
Archives