public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Uninstall on macOS (13.5.1)
Date: Sun, 20 Aug 2023 12:19:50 -0400	[thread overview]
Message-ID: <59cc47a8-5a95-5801-5612-f828b47fce76@usa.net> (raw)
In-Reply-To: <06086c7d-8d7f-409e-ba92-28fb9739aa56n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


I think that script is fairly old - but as a quick next step, could you 
try running it with:

sudo perl ~/Desktop/uninstall-pandoc.pl

If pandoc was installed using root permissions (and the installer will 
ask for your password, which means it does), than it will need those 
permissions to remove them.

Alternately, just remove those files.

Daniel T. Staal

On 8/20/23 10:32 AM, GFS wrote:
> I installed pandoc (the package) then realised 30mins later that I don't 
> need it.  I'm not a coder, but have tried uninstalling via the 
> pandoc.org Documentation as proposed (uninstall-pandoc.pl). I found that 
> I could run the script, if I saved it to my Desktop as a txt file, gave 
> it the name: uninstall-pandoc.pl and entered the following command in 
> Terminal:
> perl ~/Desktop/uninstall-pandoc.pl
> 
> It threw some skipping errors and said that it had been successful. 
> *However*.. when I looked in the folder that it had listed for deletion, 
> I found that there were Pandoc files in them.
> 
> Can anyone please tell me what I need to do, to completely delete the 
> Pandoc package?
> 
> Here is a screen-grab of the Terminal as used + another showing 2 files 
> left in place.  I don't know if there are more somewhere else.
> 
> Many thanks for any help.
> 
> pandoc-grab1.jpeg
> 
> pandoc-grab2.jpeg


-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

-- 
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/59cc47a8-5a95-5801-5612-f828b47fce76%40usa.net.


  parent reply	other threads:[~2023-08-20 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 14:32 GFS
     [not found] ` <06086c7d-8d7f-409e-ba92-28fb9739aa56n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-20 16:19   ` Daniel Staal [this message]
     [not found]     ` <59cc47a8-5a95-5801-5612-f828b47fce76-Jdbf3xiKgS8@public.gmane.org>
2023-08-20 19:39       ` GFS
     [not found]         ` <aa112f32-2d03-40a1-b2bd-04507ababacfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-20 20:00           ` Daniel Staal
     [not found]             ` <816b89f8-547b-ae95-3bc5-07b4465b8717-Jdbf3xiKgS8@public.gmane.org>
2023-08-20 20:16               ` GFS

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=59cc47a8-5a95-5801-5612-f828b47fce76@usa.net \
    --to=dstaal-jdbf3xikgs8@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).