unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ivan Shmakov <ivan@siamics.net>
Cc: mah@everybody.org, 18687@debbugs.gnu.org,
	Stefan Kangas <stefan@marxist.se>,
	mediawiki-el@lists.everybody.org, tim@tim-landscheidt.de
Subject: bug#18687: mw 0.1: modular MediaWiki interface for Emacs
Date: Sun, 08 Mar 2020 13:52:24 -0400	[thread overview]
Message-ID: <jwvmu8qu4hy.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <875zfo6eig.fsf@stefankangas.se> (Stefan Kangas's message of "Sun, 01 Mar 2020 02:38:15 +0100")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/x-markdown; coding=UTF-8, Size: 461 bytes --]

>> http://am-1.org/~ivan/packages-el/
>> http://am-1.org/~ivan/archives/git/mw-el-2014.git/

Thanks.

If the code might still be useful for future developments, I could add
it as an `externals/mw` branch in elpa.git but since it uses an outdated
API it wouldn't be worthwhile to release an actual GNU ELPA package for
it (i.e. I'd set the "Version:" to 0 to prevent building a package).

How does it compare to the current `mediawiki-el`?


        Stefan






  reply	other threads:[~2020-03-08 17:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87oatpkof7.fsf@passepartout.tim-landscheidt.de>
2014-10-11 10:55 ` bug#18687: mw 0.1: modular MediaWiki interface for Emacs Ivan Shmakov
2014-10-12  4:47   ` Stefan Monnier
2014-10-12 10:20     ` Ivan Shmakov
2014-10-14 18:40       ` Stefan Monnier
2014-10-14 20:05         ` Ivan Shmakov
     [not found]         ` <87k342zabt.fsf@violet.siamics.net>
2014-10-14 23:51           ` Stefan Monnier
2014-10-21 16:33             ` Stefan Monnier
2014-10-22 21:35               ` Ivan Shmakov
2014-10-24 18:55                 ` Ivan Shmakov
2014-12-31 12:12                   ` bug#18687: mw: " Ivan Shmakov
2015-01-01 16:06                     ` Stefan Monnier
2015-01-01 16:37                       ` Ivan Shmakov
2015-01-23 14:42                       ` Ivan Shmakov
2015-02-20 17:14                         ` Stefan Monnier
2015-02-20 18:30                           ` Ivan Shmakov
2015-02-20 19:52                             ` Stefan Monnier
2015-01-01 21:03                     ` Ivan Shmakov
2015-02-20  7:09                     ` Ivan Shmakov
2020-02-29 18:39     ` bug#18687: mw 0.1: " Stefan Kangas
2020-02-29 19:55       ` Ivan Shmakov
2020-03-01  1:38         ` Stefan Kangas
2020-03-08 17:52           ` Stefan Monnier [this message]
2020-08-04 16:06             ` Stefan Kangas
2020-08-04 16:45               ` Mark A. Hershberger
2020-08-04 16:47                 ` Stefan Kangas
2020-03-02 20:30       ` Mark A. Hershberger
2020-03-11  1:31         ` Stefan Kangas
2014-10-13 17:20   ` Mark A. Hershberger

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=jwvmu8qu4hy.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=18687@debbugs.gnu.org \
    --cc=ivan@siamics.net \
    --cc=mah@everybody.org \
    --cc=mediawiki-el@lists.everybody.org \
    --cc=stefan@marxist.se \
    --cc=tim@tim-landscheidt.de \
    /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).