/tech/ - Technology★

>>1009468 (OP)

mac os

>>1009468 (OP)

Gentoo

There is none for english, at least independent of a word processor like aspell is for spelling.

>>1009468 (OP)

https://youtu.be/FtieBc3KptU

>>1009523

I forgot about LanguageTool which is actually good for non-spelling needs. I strongly suggest you look into that.

>>1009490

>the best way I can explain it to you is by first explaining how I came to emacs

talks are the worst the possible way of receiving information

>>1009525

>The core app itself is free and open-source, and can be downloaded for offline use. However, it is massive and requires considerable processing power and I/O speed. As such, LanguageTool is also offered as a freemium web service.

Do you still think bloatware isn't proprietary?

>>1009583

>Do you still think bloatware isn't proprietary?

Unfortunately this isn't the type of thing that can be done both easily and robustly. Natural language processing and especially incorrect natural language processing is exceedingly difficult. LanguageTool is the most functional option, GNU diction is perhaps the most free option beyond not using a grammar checker at all. So use what works for you.

>linux

Use Microsoft Word 2018 on Windows 10: Professional edition

>>1009468 (OP)

vim's own spellcheck, you could you just write as is and get away with it

>>1009602

Microsoft Word's grammar checker actually isn't particularly good, people mostly just assume it's correct: http://www.serenity-software.com/pages/comparisons.html

>>1009701

OP is looking for much more unfortunately, he wants a grammar checker which is orders of magnitude more difficult to create, and orders of magnitude more difficult beyond that to create well. Personally this is more or less what I do as well though.

>>1009525

>LangaugeTool

How in the fuck do you compile this shit? Even after installing the 1000 java dependencies, it still fails to compile.

>>1009714

I'd just use the build script (probably on the latest release version) personally.

To install or build using a script, simply type:

curl -L https://raw.githubusercontent.com/languagetool-org/languagetool/master/install.sh | sudo bash <options>
sudo bash install.sh <options>

Usage: install.sh <option> <package>
Options:
   -h --help                   Show help
   -b --build                  Builds packages from the bleeding edge development copy of LanguageTool
   -c --command <command>      Specifies post-installation command to run (default gui when screen is detected)
   -q --quiet                  Shut up LanguageTool installer! Only tell me important stuff!
   -t --text <file>            Specifies what text to be spellchecked by LanguageTool command line (default spellcheck.txt)
   -d --depth <value>          Specifies the depth to clone when building LanguageTool yourself (default 1).
   -p --package <package>      Specifies package to install when building (default all)
   -o --override <OS>          Override automatic OS detection with <OS>
   -a --accept                 Accept the oracle license at http://java.com/license. Only run this if you have seen the license and agree to its terms!
   -r --remove <all/partial>   Removes LanguageTool install. <all> uninstalls the dependencies that were auto-installed. (default partial)

Packages(only if -b is specified):
   standalone                  Installs standalone package
   wikipedia                   Installs Wikipedia package
   office-extension            Installs the LibreOffice/OpenOffice extension package

Commands:
   GUI                         Runs GUI version of LanguageTool
   commandline                 Runs command line version of LanguageTool
   server                      Runs server version of LanguageTool

>>1009721

That's what I did! JAVA_HOME went unset and maven isn't able to find a compiler.

>>1009722

ah sorry, that is odd, you should be able to do something like the following:

JAVA_HOME=jdk-install-dir
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH

>>1009724

~$ env|grep JAVA_HOME
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-i386/
~$ sudo bash install.sh -b -p standalone
[omitted text]
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[INFO] 1 error

Am I doing something wrong? Is java just hopeless?

>>1009731

could you check to see if $JAVA_HOME is in your $PATH? other than this I'm not sure what could be wrong.

>>1009742

I did, of course. Eventually I figured that the new instance of bash wasn't receiving the environment variables for whatever reason. So I did,

~$ sudo bash -c "export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-i386;export PATH=$JAVA_HOME/bin:$PATH;. install.sh -b -p standalone"

One problem was solved; maven no longer warned that JAVA_HOME was unset. The original compilation error from >>1009731 still appeared, though. I'm giving up while I still can.