**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:27

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:27

D. Moonfire @dmoonfire

Jun 21, 2018, 21:27

D. Moonfire @dmoonfire

Author Intrusion Show more

Another productive lunch hour on #AuthorIntrusion while working on echo word detection.

I got it to correctly detect the same word used within a given range. With these plugin settings:

- scope: content
select: //token[@l>3]
within: 3
warning: 1
error: 2

And the file:

one two one three four one

It produces a warning on the first and third "one", an error on the second "one".

For xpath, I'll probably change it to `//token[length()>3]` because it's prettier.

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:29

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:29

Jun 21, 2018, 21:29

D. Moonfire @dmoonfire

Author Intrusion Show more

Using C#'s XSLT function overrides and XElement has really simplified the code. I'm also happy that I've gotten rid of a big "reimplemented wheel" that the last iteration had (implementing CSS generically) since I get lost in the stupid details of getting those "right".

And since you can pull in XSLT functions through packages, that means I can easily write a package that provides "soundex()" or "stem()" or "part-of-speech()" to look for more complex items.

**D. Moonfire** @dmoonfire · 2018-06-21T21:31:10Z

D. Moonfire @dmoonfire

Author Intrusion Show more

This also means there is only a few steps left until I can see if this proof-of-concept works. I need a "check" command that will run the echo detection across the entire project and outputs the results in something GCC/Emacs/Atom can use. At that point, I'll have the minimum needed to use Make or a build command and get useful, specific results.

Jun 21, 2018, 21:31 · Web · 0 · 0

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:33

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:33

Jun 21, 2018, 21:33

D. Moonfire @dmoonfire

Author Intrusion Show more

With the previous iterations of AI, I switched to write-novel/update-code look that was really useful. Of course, this was back when I wrote an entire damn text editor with customized keyword highlighting and auto-corrections.

I failed because I was basically trying to write Scrivner.

The more recent iteration is to write a focused tool (ala `git`), and then integrated it into other tools (e.g., Atom, Emacs, VS Code) to handle everything else.

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:35

**D. Moonfire** @dmoonfire · Jun 21, 2018, 21:35

Jun 21, 2018, 21:35

D. Moonfire @dmoonfire

Author Intrusion Show more

Last one. Why I'm doing this. I got into a discussion with a coworker about it.

Grammar checkers are great, but they don't look for stylistic issues. So reducing adverbs, detecting echo words ("she jumped on the jumper, jumping on his knee to shatter the bone"), my personal love affair with gerunds, or pointing out when I accidentally used present tense in my novel.

That's what AI is mainly for. To catch those things that an editor would catch.