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.

Sign up for GitHub

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

Jump to bottom

Investigate merging this upstream into Stack #6

Open
friedbrice opened this issue Jul 30, 2020 · 1 comment
Open

Investigate merging this upstream into Stack #6

friedbrice opened this issue Jul 30, 2020 · 1 comment
Assignees
@friedbrice
Labels
Meta UX

Comments

@friedbrice
Copy link
Owner

friedbrice commented Jul 30, 2020 •
edited
Loading

It's kinda lame this tool is such a thin wrapper for another tool (I would have made it a simple shell script, except that i wanted it to work for my Windows friends). In particular, it contributes to this problem

How Standards Proliferate. (See: A/C chargers, character encodings, instant messaging, etc.). Situation: There are 14 competing standards. Cueball: 14?! Ridiculous! We need to develop one universal standard that covers everyone's use cases. Ponytail: Yeah! Soon: Situation: There are 15 competing standards. Standards

Ideally, Stack would have this functionality built in. We need to see if (1) There's a sensible way to add it, and (2) If the Stack devs even want such a feature added.
@friedbrice friedbrice self-assigned this Aug 1, 2020
@friedbrice
Copy link
Owner Author

Well, let's see how this goes... commercialhaskell/stack#5354

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@friedbrice friedbrice

Labels
Meta UX
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@friedbrice