mirror of https://github.com/enso-org/enso.git synced 2024-12-25 17:26:12 +03:00

History

Hubert Plociniczak dcba966754 Use a custom directory for VCS repo metadata (#3921 ) Rather than hard-coding `.git` in the root of the project, VCS should save data into Enso's data directory (i.e. `.enso`). This change reshuffles initialization and configuration to store Git VCS metadata by default at `.enso/.git`. This is follow up to https://github.com/enso-org/enso/pull/3851 # Important Notes Apparently a custom Git directory in JGit means that it always creates a `.git` file with `gitdir` pointing to the custom location. This is not necessary in our case since all our commands provide that explicitly. That is why `init` operation removes `.git` file, which may seem a bit counter-intuitive.	2022-11-29 14:40:36 +00:00
..
src	Use a custom directory for VCS repo metadata (#3921 )	2022-11-29 14:40:36 +00:00
README.md	Add a markdown style guide (#1022 )	2020-07-21 13:59:40 +01:00

Hubert Plociniczak dcba966754

Use a custom directory for VCS repo metadata (#3921 )

Rather than hard-coding `.git` in the root of the project, VCS should save data into Enso's data directory (i.e. `.enso`).
This change reshuffles initialization and configuration to store Git VCS metadata by default at `.enso/.git`.
This is follow up to https://github.com/enso-org/enso/pull/3851

# Important Notes
Apparently a custom Git directory in JGit means that it always creates a `.git` **file** with `gitdir` pointing to the custom location.
This is not necessary in our case since all our commands provide that explicitly.
That is why `init` operation removes `.git` file, which may seem a bit counter-intuitive.

2022-11-29 14:40:36 +00:00

src

Use a custom directory for VCS repo metadata (#3921 )

2022-11-29 14:40:36 +00:00

README.md

Add a markdown style guide (#1022 )

2020-07-21 13:59:40 +01:00

README.md

Enso Language Server

The Enso Language Server is responsibile for providing a remote-communication protocol for the runtime, exposing many of its features to the users. In addition it provides the backing service for much of the IDE functionality associated with the language. It encompasses the following functionality:

Introspection Services: Giving clients the ability to observe information about their running code including values, types, profiling information, and debugging.
Code Execution: The ability for clients to execute arbitrary Enso code in arbitrary scopes. This can be used in conjunction with the above to provide a REPL with an integrated debugger.
Code Completion: Sophisticated completion functionality that refines suggestions intelligently based on context.
Node Management: Tracking and providing the language server's internal node representation of the Enso program.
Code Analysis: Analysis functionality for Enso code (e.g. find usages, jump-to-definition, and so on).
Refactoring: Refactoring functionality for Enso code (e.g. rename, move, extract, and so on).
Type Interactions: Features for type-driven-development that allow users to interact with the types of their programs.