Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haxe --display requires a valid file #4488

Closed
elsassph opened this issue Aug 18, 2015 · 8 comments
Closed

haxe --display requires a valid file #4488

elsassph opened this issue Aug 18, 2015 · 8 comments

Comments

@elsassph
Copy link
Contributor

The documentation (http://haxe.org/manual/cr-completion-overview.html) about --display file@position[@mode] indicates that file "does not respect any class paths or libraries".

What does that mean?

In any case it seems to enforce that the file is in the classpath, and that the file name respects the regular file restructions (must end with .hx, must start with an underscore).

The problem

As a service for editors, it is a bad user experience to have to save the file everytime the compiler has to be used: we really need a way to fix that without having to resort to adding a temporary classpath.

@yar3333
Copy link
Contributor

yar3333 commented Aug 18, 2015

This problem was discussed several times at past. Nicolas said, what to hard to implement processing file from memory. In my experience file saving on completion is unexpected behavior only, but not a big problem.

@elsassph
Copy link
Contributor Author

What I'm asking is to write the file in a temporary location or as a temporary hidden file.

@yar3333
Copy link
Contributor

yar3333 commented Aug 19, 2015

Philippe, why you think what adding a temporary classpath is a bad solution?

haxe <user options> -cp temp --display ...

@elsassph
Copy link
Contributor Author

For one, manipulating the compiler arguments is always a bit risky, and second compiler completion requires the build and completion arguments are identical.

@ncannasse
Copy link
Member

I don't really understand how it's a bad user experience to save a file, for instance it's already done when compiling. Any insight ?

@elsassph
Copy link
Contributor Author

For me that's just abnormal and I don't understand why we have this limitation.

@kaikoga
Copy link
Contributor

kaikoga commented Aug 20, 2015

👍 to Philippe. Everything you type might be everything you want to compile (in Haxe where you must compile for completions at least), but is NOT everything you want to have on your file system to get restored when you either exit and restart your editor another day, or say, have your editor just crash at random timing.

Requiring write access for completions may have more problems, if you want some completions in read only files, or files over slow network.

@Simn
Copy link
Member

Simn commented Jan 17, 2016

See #4651.

@Simn Simn closed this as completed Jan 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants