From: Pranesh Prakash <the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: check for latest version of pandoc
Date: Sat, 24 Sep 2022 07:11:17 -0700 (PDT) [thread overview]
Message-ID: <372d9912-6e1d-4e25-92e7-4fc637d4f64dn@googlegroups.com> (raw)
In-Reply-To: <CALwjjMgS45dOb+t_akw=Kh0Se8R5nxNhD6g6f10rzWE72ivXeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1211 bytes --]
Dear John,
You can convert this (not really tested + simplistic) bash script to
whatever its Windows equivalent would be and run it to check if the version
you have is the latest (released on Github) or not.
```
#/usr/bin/env bash
a=$(curl https://github.com/jgm/pandoc/releases/latest -s -L -I -o
/dev/null -w '%{url_effective}' | cut -d'/' -f8)
b=$(pandoc --version | cut -d' ' -f2 | head -n1)
if [ "$a" = "$b" ]
then echo 'latest'
else echo 'not latest'
fi
```
Cheers,
Pranesh
On Thursday, 25 August, 2022 at 2:00:43 am UTC+5:30 john.a...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
wrote:
> Hello All!
>
> Sorry if this has come up before, but is there an easy way to check if
> the version of Pandoc installed locally is the latest version?
>
> I'm using Windows 10.
>
> Thanks!
>
> John
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/372d9912-6e1d-4e25-92e7-4fc637d4f64dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1846 bytes --]
prev parent reply other threads:[~2022-09-24 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 20:30 John O'Regan
[not found] ` <CALwjjMgS45dOb+t_akw=Kh0Se8R5nxNhD6g6f10rzWE72ivXeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-24 14:11 ` Pranesh Prakash [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=372d9912-6e1d-4e25-92e7-4fc637d4f64dn@googlegroups.com \
--to=the.solipsist-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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).