Andy Wokula wrote:
> Am 08.12.2018 um 16:03 schrieb Bram Moolenaar:
> > Yasuhiro Matsumoto wrote:
> >
> >> On Saturday, December 8, 2018 at 10:53:07 PM UTC+9, Bram Moolenaar
> >> wrote:
> >>> I have recently changed the behavior of :function to allow for
> >>> redefining (overwriting) a function
Am 08.12.2018 um 16:03 schrieb Bram Moolenaar:
Yasuhiro Matsumoto wrote:
On Saturday, December 8, 2018 at 10:53:07 PM UTC+9, Bram Moolenaar
wrote:
I have recently changed the behavior of :function to allow for
redefining (overwriting) a function when that should normally be
fine. Therefore, us
Yasuhiro Matsumoto wrote:
> On Saturday, December 8, 2018 at 10:53:07 PM UTC+9, Bram Moolenaar wrote:
> > I have recently changed the behavior of :function to allow for
> > redefining (overwriting) a function when that should normally be fine.
> > Therefore, using function! is hardly ever needed
On Saturday, December 8, 2018 at 10:53:07 PM UTC+9, Bram Moolenaar wrote:
> I have recently changed the behavior of :function to allow for
> redefining (overwriting) a function when that should normally be fine.
> Therefore, using function! is hardly ever needed.
>
> Previously, when sourcing a sc
Hi,
> I have recently changed the behavior of :function to allow for
> redefining (overwriting) a function when that should normally be
> fine.
> Therefore, using function! is hardly ever needed.
>
> [...]
> Vim now checks the script ID of where the function was defined, and
> whether that same
I have recently changed the behavior of :function to allow for
redefining (overwriting) a function when that should normally be fine.
Therefore, using function! is hardly ever needed.
Previously, when sourcing a script a second time, one had to use
function! to redefine the functions. This was
