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

Pass companion file reference to Editor #357

Open
adamfowleruk opened this issue Jan 1, 2020 · 2 comments
Open

Pass companion file reference to Editor #357

adamfowleruk opened this issue Jan 1, 2020 · 2 comments
Assignees
Labels
enhancement TDD TDD delivery approach MUST be used

Comments

@adamfowleruk
Copy link
Collaborator

When opening a file in Paladin, pass on the companion file full path to the editor for the file being opened. This assists the Editor when the companion file is not in the same folder.

Only Paladin has an idea of the Project context, and thus file dependencies, of the opened file.

Document this protocol fully and advertise to developers of Editors (E.g. Pe and Koder).

@adamfowleruk adamfowleruk added this to the 01 User requested milestone Jan 1, 2020
@adamfowleruk adamfowleruk self-assigned this Jan 1, 2020
@scottmc
Copy link
Member

scottmc commented Jan 1, 2020

IIRC Pe and perhaps others, also accept the line number to open up to by adding :nnn to the end of the path.

@adamfowleruk
Copy link
Collaborator Author

Yeah I'm already passing line number (supported by both Pe and Koder) and column (supported by Koder) - E.g. if you double click on a compilation error.

@adamfowleruk adamfowleruk added the TDD TDD delivery approach MUST be used label Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement TDD TDD delivery approach MUST be used
Development

No branches or pull requests

2 participants