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

Easier way to get started / run your code against the testsuite. #55

Open
daxida opened this issue Apr 21, 2024 · 1 comment
Open

Easier way to get started / run your code against the testsuite. #55

daxida opened this issue Apr 21, 2024 · 1 comment
Labels
feature Feature request

Comments

@daxida
Copy link
Collaborator

daxida commented Apr 21, 2024

This would ideally be a set of justfile commands similar to what we had prior to this commit:

It should ease the process of:

  • opening the file to edit (with whatever editor).
  • (optional) go to the next clash.
  • generate the stub.
  • run the code on autosave.

Not all the steps are necessary, but I found those to be the bare minimum when solving puzzles / clashes.

@daxida daxida added the feature Feature request label Apr 21, 2024
@Andriamanitra
Copy link
Owner

The main problem is that you want 3 terminal panes (one for editor, one for showing the statement/test cases, and one for showing the test results) and how to split or open new terminals depends on what kind of setup the user has.

Here's a couple of ideas for how we could handle this:

  • Detect if the user has a terminal multiplexer like zellij or tmux installed and use those to open the different panes.
  • Provide two separate commands, and let users worry about opening the editor and terminals
    • one for automatically showing the statement & generating stub
    • one for automatically running the tests on save).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature request
Projects
None yet
Development

No branches or pull requests

2 participants