zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Portable rootless ZSH
Date: Fri, 11 Oct 2019 13:11:25 +0000	[thread overview]
Message-ID: <1570799484.3825.13.camel@samsung.com> (raw)
In-Reply-To: <TDwB1Iqe7IWM9v3ll1xTQHtjYH-dEp5OMRUBA341L7O4rccNO-nh6lUSKnXV-6HKFJ4yUlkmfrPeVBqNMxdr6_pIYXR6z40GWl3r3-S_QlM=@protonmail.com>

On Wed, 2019-10-09 at 20:07 +0000, Coden wrote:
> /root/.oh-my-zsh/oh-my-zsh.sh:69: compinit: function definition file not found
> /root/.oh-my-zsh/lib/theme-and-appearance.zsh:2: colors: function definition file not found

OK, so assuming the static linking is all set up (it's certainly doable
but not necessarily trivial as it's not all that common these days),
you're now faced with making shell functions available.  These can live
anywhere --- nothing here needs to be set up as root --- but obviously
you need to put them somewhere, and then tell the shell where you've put
them.  The directories are given by fpath (array) and FPATH
(collon-separated values for putting into the environment).  You can
look at the existing values for an idea of where everything is on the
system you're starting from.  Probably you'll be configuring the
directories in ~/.zshenv in the target system.

pws

      parent reply	other threads:[~2019-10-11 13:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 18:44 Coden
2019-10-08 20:47 ` Peter A. Castro
2019-10-09 20:07   ` Coden
2019-10-11 11:54     ` Coden
2019-10-11 19:32       ` Coden
2019-10-12 21:22         ` Coden
2019-10-12 23:22           ` Bart Schaefer
2019-10-13  0:13             ` Coden
2019-10-13  5:59               ` Bart Schaefer
2019-10-13 23:51                 ` Coden
2020-03-07 13:03                   ` Coden
2019-10-11 13:11     ` Peter Stephenson [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=1570799484.3825.13.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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