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: Pandoc install on Mojave OS
Date: Sat, 2 Feb 2019 22:35:02 -0500	[thread overview]
Message-ID: <38ad2ca4-c9b9-e93b-1825-deebedb0a20a@usa.net> (raw)
In-Reply-To: <d8befbed-1b70-4c08-9c8d-20833f1f9cef-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 2/2/19 6:30 PM, jwalter-GeJbg9m2jcQAvxtiuMwx3w@public.gmane.org wrote:
> 
> 
> On Saturday, February 2, 2019 at 6:19:21 PM UTC-5, John MacFarlane wrote:
> 
> 
>     What do these tell you?
> 
>     ls -l /usr/local/bin/pandoc
> 
> 
> Permission denied
> 
> 
>     ls -ld /usr/local/bin
> 
> drwx-------- etc
> 
You've got something seriously messed up in your OS install.  Try 
running First Aid on it from Disk Utility.  If that doesn't work, I'd 
actually recommend a reinstall - though for this issue itself you could 
just fix the permissions on this one directory.

(Fixing this itself isn't necessarily hard - but if you've got low-level 
issues like this here, I have to worry about what other issues you might 
have.  Oh, and I'd have been really interested in the rest of that line 
on the second - this is enough to show it's wrong, but the rest is 
important info as well.  It's always best to post full output when 
responding to requests for info like this - you don't know what the 
requester is looking for.)

Daniel T. Staal

---------------------------------------------------------------
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.
---------------------------------------------------------------


  parent reply	other threads:[~2019-02-03  3:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02  2:23 jwalter-GeJbg9m2jcQAvxtiuMwx3w
     [not found] ` <ee13f2a3-4a7a-4123-9d21-ec34213a973e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-02  3:46   ` Daniel Staal
     [not found]     ` <723de4c4-5ced-30b9-2d3f-5ae9eab8b24d-Jdbf3xiKgS8@public.gmane.org>
2019-02-02 22:40       ` jwalter-GeJbg9m2jcQAvxtiuMwx3w
     [not found]         ` <58dd6940-0e03-48a0-b42b-6d748982e25a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-02 23:19           ` John MacFarlane
     [not found]             ` <m2o97tn5hy.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-02-02 23:30               ` jwalter-GeJbg9m2jcQAvxtiuMwx3w
     [not found]                 ` <d8befbed-1b70-4c08-9c8d-20833f1f9cef-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-03  3:35                   ` Daniel Staal [this message]
2019-02-02  5:26   ` John MacFarlane
     [not found]     ` <m2womin4kp.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-02-02 22:43       ` jwalter-GeJbg9m2jcQAvxtiuMwx3w

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=38ad2ca4-c9b9-e93b-1825-deebedb0a20a@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).