From: martin.ebourne@arcordia.com
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
Cc: zsh-users@sunsite.dk
Subject: RE: FPATH being reset after .zshenv
Date: Wed, 1 Aug 2001 11:19:10 +0100 [thread overview]
Message-ID: <OFA68A7FC5.868D0315-ON80256A9B.0037D096@uk.jpmorgan.com> (raw)
> Unfortunately it seems that zsh resets the fpath after executing this
file
> (it is empty while running the file). It does however, remember the
> autoload commands, which obviously then become useless.
>
I cannot reproduce it. Are you sure it is not reset in any other startup
file?
I've looked into it some more, and found the culprit. I had the following
line earlier on:
typeset -U FPATH
which obviously makes the parameter local as a side effect. I've changed it
to -Ug now which is working fine.
Having looked back at the info documentation, I suspect what confused me
into leaving the -g out is the bit that says 'This flag does not affect the
parameter after creation':
The -g (global) flag is treated specially: it means that any
resulting parameter will not be restricted to local scope. Note
that this does not necessarily mean that the parameter will be
global, as the flag will apply to any existing parameter (even if
unset) from an enclosing function. This flag does not affect the
parameter after creation, hence it has no effect when listing
existing parameters, nor does the flag +g have any effect except
in combination with -m (see below).
Anyhow, thanks for the help.
Martin.
next reply other threads:[~2001-08-01 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 10:19 martin.ebourne [this message]
2001-08-01 10:37 ` Borsenkow Andrej
-- strict thread matches above, loose matches on Subject: below --
2001-08-01 11:05 martin.ebourne
2001-08-01 11:30 ` Borsenkow Andrej
2001-08-01 9:25 martin.ebourne
2001-08-01 9:52 ` Borsenkow Andrej
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=OFA68A7FC5.868D0315-ON80256A9B.0037D096@uk.jpmorgan.com \
--to=martin.ebourne@arcordia.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--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).