zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Ways of delivering code for execution
Date: Sun, 26 Nov 2017 09:06:47 -0800	[thread overview]
Message-ID: <7e43fb1a-0a39-6bcf-5ba0-7f24fd9f5821@eastlink.ca> (raw)
In-Reply-To: <etPan.5a1ad756.570c9efe.c73c@zdharma.org>

On 26/11/17 07:01 AM, Sebastian Gniazdowski wrote:
> Hello,
> I know following methods of loading a code for execution:
>
> a) source file
> b) autoload file && file
> c) eval $(<file)
>
> This is one of impossible questions that I sometimes ask. I'm wondering if there is any other method to do what a,b,c are doing?

Just curious: why do you look for other methods?


  reply	other threads:[~2017-11-26 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 15:01 Sebastian Gniazdowski
2017-11-26 17:06 ` Ray Andrews [this message]
2017-11-26 18:17   ` Sebastian Gniazdowski

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=7e43fb1a-0a39-6bcf-5ba0-7f24fd9f5821@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@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).