From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Grammar checking in Emacs
Date: Wed, 17 Nov 2021 09:49:07 +1100 [thread overview]
Message-ID: <87sfvvd6tk.fsf@gmail.com> (raw)
In-Reply-To: <jwvfsrwqit4.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> In my view, this is not a problem of software freedom, so I do consider
> LanguageTool to be philosophically perfectly acceptable.
> It's just technically rather annoying to install :-(
> [ Installing a JAR file is no solution, since you then have to worry
> about keeping it up-to-date. ]
>
Just interested in why you find installing a jar file so problematic.
Given it is essentially just a zip archive, how is installing a jar file
and keeping it up-to-date any different from installing any binary
package? Even when you clone a repository and build from sources, you
still have to pull updates and rebuild. Is their something fundamentally
different with jar or is it simply a different build system and the
discomfort is due to it being less familiar?
next prev parent reply other threads:[~2021-11-16 22:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1zgq6xon7.fsf.ref@yahoo.es>
2021-11-15 0:12 ` Grammar checking in Emacs Daniel Martín
2021-11-15 2:46 ` Stefan Monnier
2021-11-15 8:16 ` tomas
2021-11-15 22:43 ` Peter Oliver
2021-11-15 23:02 ` Stefan Monnier
2021-11-16 18:01 ` Philip Kaludercic
2021-11-16 18:09 ` Eli Zaretskii
2021-11-17 3:18 ` Stefan Monnier
2021-11-19 21:51 ` Peter Oliver
2021-11-17 4:13 ` Richard Stallman
2021-11-19 22:14 ` Peter Oliver
2021-11-16 4:06 ` Richard Stallman
2021-11-16 11:32 ` Ihor Radchenko
2021-11-16 14:28 ` Stefan Monnier
2021-11-16 22:49 ` Tim Cross [this message]
2021-11-16 23:29 ` Stefan Monnier
2021-11-16 6:28 ` Alexandre Garreau
2021-11-16 14:30 ` Stefan Monnier
2021-11-16 15:43 ` tomas
2021-11-18 3:51 ` Richard Stallman
2021-11-16 8:23 ` tomas
2021-11-15 19:45 ` Rudolf Adamkovič
2021-11-17 4:12 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfvvd6tk.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).