From: luigi scarso <luigi.scarso@gmail.com>
To: Nicola <nvitacolonna@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
MetaPost List <metapost@tug.org>
Subject: Re: ANN: Updated Vim scripts for METAFONT/MetaPost
Date: Wed, 5 Oct 2016 10:35:01 +0200 [thread overview]
Message-ID: <CAG5iGsC+083EseYbaJGvtDKHCx5srMf691XehW_1E=k7ACKa-A@mail.gmail.com> (raw)
In-Reply-To: <nt2dg5$hab$1@blaine.gmane.org>
On Wed, Oct 5, 2016 at 10:26 AM, Nicola <nvitacolonna@gmail.com> wrote:
> FYI:
> https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
>
> Click on "changed files".
>
good.
Btw
http://www.guitex.org/home/meeting
--
luigi
--
http://tug.org/metapost/
prev parent reply other threads:[~2016-10-05 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 10:46 Nicola
2016-09-18 12:05 ` Nicola
2016-09-18 12:09 ` luigi scarso
2016-09-18 14:32 ` Nicola
[not found] ` <nrm87q$bkn$1@blaine.gmane.org>
2016-10-05 8:26 ` Nicola
2016-10-05 8:35 ` luigi scarso [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG5iGsC+083EseYbaJGvtDKHCx5srMf691XehW_1E=k7ACKa-A@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--cc=metapost@tug.org \
--cc=ntg-context@ntg.nl \
--cc=nvitacolonna@gmail.com \
/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.
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 NNTP newsgroup(s).