From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Zed obtains fresh text of function
Date: Sat, 3 Oct 2015 12:18:51 -0700 [thread overview]
Message-ID: <151003121851.ZM4733@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVCAoJaV0q5d65TyiL6NP16CZH=S=Mw2irZo_LOQEqi8jA@mail.gmail.com>
On Oct 3, 12:44pm, Sebastian Gniazdowski wrote:
} Subject: Zed obtains fresh text of function
}
} Hello,
} creating simple function tst in */site-functions:
}
} echo "Hello tst abcd"
}
} doing:
} autoload zed
} autoload tst
} zed -f tst
}
} And then repeating:
} zed -f tst<Enter><Ctrl-C>
}
} after each update of the tst file/function - will result in zed
} loading the most recent version of the function, i.e. from disk.
Yes, if you ctrl+c out of zed then it does not save the function in
the current shell, so it remains undefined/autoloadable. Then the
next time you run zed, it loads from the $fpath file again.
This is the intended behavior; you need to exit from zed with ^X^W
(or ZZ if in vicmd mode) in order to save your changes (even if you
didn't explicitly make any -- autoloading was an implicit change).
Even if you ^X^W the state is only saved to the current shell (memory),
not written back to the source file.
} Not sure if this is expected, however I face an obvious situation - I
} update autoloaded function and run it, and it is the disk version that
} is being run, not the one from first load
If the ONLY "first load" is with zed, then the function was never
really loaded -- it was only pulled into a vared buffer to await
that final write command. You aborted the process of parsing it
into a runnable state by hitting ctrl+c.
If this isn't what you mean, then you're going to have to give a
more explicit example.
prev parent reply other threads:[~2015-10-03 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 10:44 Sebastian Gniazdowski
2015-10-03 19:18 ` Bart Schaefer [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=151003121851.ZM4733@torch.brasslantern.com \
--to=schaefer@brasslantern.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).