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: Installation directory on MacOS
Date: Wed, 1 Feb 2023 11:31:52 -0500	[thread overview]
Message-ID: <2c373fe2-76f8-9dcb-34bf-aac16f53674d@usa.net> (raw)
In-Reply-To: <bb894ee8-2abd-44e4-9a41-f44afa62b2b3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 2/1/23 11:21 AM, Marco Noris wrote:
> Thank you all...
> 
> which command is a great learning, thanks!!

Note that `which` tells you which binary you would run if you typed that 
program - it does *not* tell you every version you have installed, or if 
you have others installed, or help you find anything that isn't an 
executable in your current $PATH.

But if you need to find the path to a program you can run from the 
command line, it's quick and easy.

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:[~2023-02-01 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 13:27 Marco Noris
     [not found] ` <788bab18-b5c5-4458-9c86-ac09613be2c6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-31 16:36   ` John MacFarlane
2023-01-31 18:57   ` Daniel Staal
     [not found]     ` <1be0c094-ab7c-5f64-bbc9-2b92f1e3050c-Jdbf3xiKgS8@public.gmane.org>
2023-02-01 16:21       ` Marco Noris
     [not found]         ` <bb894ee8-2abd-44e4-9a41-f44afa62b2b3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-01 16:31           ` Daniel Staal [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=2c373fe2-76f8-9dcb-34bf-aac16f53674d@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).