zsh-users
 help / color / mirror / code / Atom feed
From: John Buttery <john@io.com>
To: Zsh users list <zsh-users@sunsite.dk>
Subject: Re: Prompt themes
Date: Tue, 4 Feb 2003 13:43:44 -0600	[thread overview]
Message-ID: <20030204194344.GC32379@io.com> (raw)
In-Reply-To: <20030204151357.13256.qmail@web12306.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]

* Le Wang <lewang@yahoo.com> [2003-02-04 10:13:57 -0500]:
> It really is not a good idea to "set" the FPATH in any of your init scripts,
> despite what your chi and harmony might lead you to believe.  ;)  Things will
> break in unpredictable ways when you upgrade or try to use your init scipts
> on a different machine.

  I know, and that's the very trouble I was referring to when I said the
chi and harmony justified it.  :)  I believe in training myself to be
"debug-resilient", which means that I do things a certain way that
probably causes breakage a little more often than doing it your way
(which is the way most people do it, I'm sure), but leaves me more
prepared to deal with problems when they do occur...if for no other
reason than the familiarity.

> There is a $fpath variable, which is an array that mirrors the contents of
> $FPATH (e.g. when you modify one, the other will change as well).  I find it
> easier to play with arrays, for example the following:
> 
> fpath=(${LE_ETC}/shell/zsh/autoloads/interactive
>        ${LE_ETC}/shell/zsh/completion
>        $fpath)
> 
> prepends two directories to $fpath and indirectly $FPATH.

  Are you saying there's a difference between playing with $fpath and
$FPATH (I mean, besides the syntactic differences of dealing with them,
I realize one's an array and the other's different...but a difference in
the results produced after the modification)?

> Perpend/append good; set bad.

  That depends on your definitions of good and bad.  :)  If it makes you
feel better, I have this line right above my normal FPATH-setting line
in .zshrc:

#export FPATH="${HOME}/.zsh/functions:${FPATH}"

  It's there to be uncommented at any time; part of being
"debug-resilient".  :)

-- 
------------------------------------------------------------------------
 John Buttery
                                     (Web page temporarily unavailable)
------------------------------------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-02-04 19:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28 12:37 Arno Dark
2002-06-28 12:45 ` Borsenkow Andrej
2002-06-28 15:25   ` Arno
2002-06-28 16:13     ` Clint Adams
2002-06-28 16:21     ` Bart Schaefer
2002-06-28 21:49       ` Andy Spiegl
2002-06-29 16:59         ` Bart Schaefer
2002-06-29  0:20       ` Adam Spiers
2002-06-30  6:46         ` Cameron McBride
2003-01-23  8:57       ` John Buttery
2003-01-23  9:04         ` Borzenkov Andrey
2003-01-23 10:19           ` john
2003-01-23 10:23             ` Joakim Ryden
2003-01-23 10:40             ` Borzenkov Andrey
2003-01-23 18:02               ` Bart Schaefer
2003-01-24 21:12                 ` John Buttery
2003-02-03 11:24                   ` Clemens Fischer
2003-02-04  9:33                     ` John Buttery
2003-02-04 10:45                       ` Roman Neuhauser
2003-02-04 14:30                         ` John Buttery
2003-02-04 15:13                           ` Le Wang
2003-02-04 19:43                             ` John Buttery [this message]
2003-02-04 19:58                               ` Le Wang
2003-01-23 10:40             ` Peter Stephenson
  -- strict thread matches above, loose matches on Subject: below --
2002-06-28 12:11 Arno Dark
2002-06-28 12:19 ` Borsenkow Andrej
2002-06-28 12:50 ` Roman Neuhauser

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=20030204194344.GC32379@io.com \
    --to=john@io.com \
    --cc=zsh-users@sunsite.dk \
    /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).