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

No subcommand to create project with create-executable #74

Closed
sogaiu opened this issue Jun 1, 2023 · 6 comments
Closed

No subcommand to create project with create-executable #74

sogaiu opened this issue Jun 1, 2023 · 6 comments

Comments

@sogaiu
Copy link

sogaiu commented Jun 1, 2023

As noted in this discussion:

In my view to create an executable should be the standard template for new-project

I agree that it would be nice for there to be some convenient way to create a new project that by default has an appropriate create-executable form in it.

I don't know whether that should be new-project, hence this issue instead of a PR.

@pepe
Copy link
Member

pepe commented Jun 1, 2023

I had the same thought when reading the discussion.

@sogaiu
Copy link
Author

sogaiu commented Jun 1, 2023

I guess one relatively simple idea would be another subcommand like new-exe-project or new-project-with-exe.

@MarcusE1W
Copy link

How about new-exec or new-executable ?

@sogaiu
Copy link
Author

sogaiu commented Jun 1, 2023

Yeah, may be those are nicely shorter names, perhaps fitting for the situation of quickly wanting to make a small executable :)

Though with such names I might expect a project.janet file that has content without declare-source, i.e. like:

(declare-project
  :name "fun"
  :description "Nice name"
  :version "0.0.0")

(declare-executable
  :name "fun"
  :entry "fun/init.janet")

@sogaiu
Copy link
Author

sogaiu commented Jun 1, 2023

On a side note, the file scaffold.janet code seems to have some "Python PEP292" templating features in it. I wonder if something based on that would be a good addition to spork...

Anyway, I'll see if I can put together a draft PR using the name new-exe-project.

Possibly the -project extension makes sense to have because when looking over the other subcommand names like quickbin, a name like new-exe* (without -project) might be confusing.

Another name can be chosen if discussion indicates there is a better choice.

@sogaiu
Copy link
Author

sogaiu commented Jun 1, 2023

#75 has been created.

bakpakin added a commit that referenced this issue Jun 2, 2023
Address #74 - add new-exe-project subcommand
@sogaiu sogaiu closed this as completed Jun 2, 2023
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

3 participants