From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: Really wierd problems with autoload
Date: Thu, 30 Mar 2000 15:32:00 +0000 [thread overview]
Message-ID: <1000330153201.ZM8815@candle.brasslantern.com> (raw)
In-Reply-To: <200003301132.NAA30426@beta.informatik.hu-berlin.de>
On Mar 30, 1:32pm, Sven Wischnowsky wrote:
} Subject: PATCH: Re: Really wierd problems with autoload
}
} Bart Schaefer wrote:
}
} > alias run-help zman
} ^^^
} `alias run-help=zman', right?
You're talkng to the original CSH_JUNKIE, Sven. I have a shell function
named `alias' that pastes in the `=' for me and then calls the builtin. I
often forget about that when cutting snippets for posting.
} > run-help:9: run-help: function definition file not found
} >
} > and further by the time
} > zman finishes the function run-help IS correctly loaded, it just for some
} > reason won't execute. Subsequent uses of ESC-h execute the new run-help.
}
} And it is really weird? And a problem? With FPATH=$f you say it should
} search the directory .../run-help
D'oh! How silly ... but that still doesn't explain how the function got
loaded in the first place! Because it *is* loaded by the end of zman,
it just didn't *execute* during zman. If it were just not loaded at all,
I'd be less mystified.
} FPATH=$f:h, I think. Or maybe everybody thinks we should also check if
} the elements of $fpath are the names of the funtions searched?
No, no, it was just me making a typo when updating the function from its
form for a previous version of zsh. That's why "it always worked before."
But fixing $f:h doesn't have any effect on the rest of the wierd exported
FPATH behavior that I described.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-03-30 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 11:32 Sven Wischnowsky
2000-03-30 15:32 ` Bart Schaefer [this message]
2000-03-31 7:29 Sven Wischnowsky
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=1000330153201.ZM8815@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).