Hi again,
"Slava Pestov" writes:
> Hi Jose,
>
> First, I will address your original problem by storing the auto-use
> info in variables to make it easier to extract without parsing.
>
Related to this, try running extra/boids/boids.factor without USING:
line. Compilation fails, with no vocabula
Hi Slava,
"Slava Pestov" writes:
> Hi Jose,
>
> First, I will address your original problem by storing the auto-use
> info in variables to make it easier to extract without parsing.
>
Excellent. What i'm doing now is storing amended-use, getting its value
in a hook in print-use-hook.
> As for
Hi Jose,
First, I will address your original problem by storing the auto-use
info in variables to make it easier to extract without parsing.
As for the issue of restarts in the case of multiple words having the
same name, that's a feature ;-) Can't FUEL just present the user with
a prompt, or eve
"Slava Pestov" writes:
> Try this,
>
> Remove the USING: form from a file, then do
>
> auto-use? on
> "path/to/my/file.factor" run-file
>
I'm adding support for auto-use to FUEL (using a variation of the
procedure above), but got a problem. It seems than when a word (e.g.
write) can be imported
"Slava Pestov" writes:
> Try this,
>
> Remove the USING: form from a file, then do
>
> auto-use? on
> "path/to/my/file.factor" run-file
Yes, but this prints the missing USING, and then i'd have to parse the
string in emacs. It'd be more robust if i could put the sequence of
vocabularies on the s
Try this,
Remove the USING: form from a file, then do
auto-use? on
"path/to/my/file.factor" run-file
Slava
On Sun, Dec 21, 2008 at 9:10 AM, Jose A. Ortega Ruiz wrote:
> "Slava Pestov" writes:
>
>> On Thu, Dec 18, 2008 at 6:01 PM, Nicholas Seckar wrote:
>>> - Applying factor's corrective ad
"Slava Pestov" writes:
> On Thu, Dec 18, 2008 at 6:01 PM, Nicholas Seckar wrote:
>> - Applying factor's corrective advice to the source (e.g. Add USING:
>> entries, etc?)
>
> That would be nice.
What would be a good way of programmatically recovering the list of
USINGs for a file after compil
"Slava Pestov" writes:
> After you pass the right using form to the listener, you can do
>
> [ ... ] infer.
>
> and Factor will print a stack effect.
>
Excellent, i'll see what i can do...
> I saw a conflict in the USING: line in fuel.factor. A few words in
> parser got moved to vocabs.parser,
On Thu, Dec 18, 2008 at 6:22 PM, Jose A. Ortega Ruiz wrote:
> This would be really cool, but i'd need to learn more about support from
> factor to infer the stack effect of a region (it could be done in the
> elisp side, i guess, but i doubt it'd be robust enough). Any pointers?
After you pass th
"Slava Pestov" writes:
>> - Showing the stack effect of the region under the cursor? (Maybe more
>> experienced Factorsauria don't goof up the stack effects, but I still do.)
>
> This seems to already work; put the cursor on a word and you'll see
> the effect in the minibuffer.
I thought Nicho
On Thu, Dec 18, 2008 at 4:22 PM, Jose A. Ortega Ruiz wrote:
>
> Hi Nicholas,
>
> "Nicholas Seckar" writes:
>
> > Forgive me if some of this already exists and I just haven't found it
> yet, but...
> > - Applying factor's corrective advice to the source (e.g. Add USING:
> > entries, etc?)
>
>
Hi Nicholas,
"Nicholas Seckar" writes:
> Forgive me if some of this already exists and I just haven't found it yet,
> but...
> - Applying factor's corrective advice to the source (e.g. Add USING:
> entries, etc?)
Yup, the USINGs on the TODO. What other corrective advice is available?
>
On Thu, Dec 18, 2008 at 6:01 PM, Nicholas Seckar wrote:
> - Applying factor's corrective advice to the source (e.g. Add USING:
> entries, etc?)
That would be nice.
> - Showing the stack effect of the region under the cursor? (Maybe more
> experienced Factorsauria don't goof up the stack effe
Forgive me if some of this already exists and I just haven't found it yet,
but...
- Applying factor's corrective advice to the source (e.g. Add USING:
entries, etc?)
- Some kind of support for jump-to-error?
- Showing the stack effect of the region under the cursor? (Maybe more
experienced Fa
Hi,
The latest HEAD of my emacs branch completes completion support for now
and fixes a possible cause of the listener hanging when datastack
display was active... this could, or could not, explain Slava's
problems.
Supposing it works, what new functionality would you like to see next in
FUEL?
15 matches
Mail list logo
