Re: `vocabulary` broken?

"Ethan Azariah" <[email protected]> Mon, 13 Oct 2025 12:03:00 +0100
Newsgroups gmane.comp.lang.forth.gforth
Message-ID <[email protected]>
Argh! Sorry, this whole issue was based on a mistake. I thought vocabulary names were defined in the root vocabulary and thus were always available, but this is apparently false. When failing, `qxv` was actually being defined in the editor vocabulary which wasn't available after `only forth`. Moving `only forth` to the beginning of the line didn't help because I didn't insert `definitions` before `vocabulary qxv`. The following line works correctly no matter the load order:

    only forth definitions vocabulary qxv also qxv definitions

I should define `clean` as I have in some previous gforth installations:

    : clean ( -- ) only forth also definitions ;

A helper word to create a vocabulary in Forth and immediately start defining into it might be a good idea too.

Did gforth put vocabulary names into Root in the past?

[I now have no idea what's up with bash. :) Maybe I'll report it to its packager, Termux.]

On Mon, Oct 13, 2025, at 11:28 AM, Ethan Azariah wrote:
> On Sat, Sep 27, 2025, at 12:57 AM, Ethan Azariah wrote:
>> vocabulary qxv only forth also qxv definitions
>> error: Undefined word
>> vocabulary qxv only forth also >>>qxv<<< definitions