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

Support entering idea without opening editor #1

Open
simeg opened this issue Nov 28, 2017 · 4 comments
Open

Support entering idea without opening editor #1

simeg opened this issue Nov 28, 2017 · 4 comments

Comments

@simeg
Copy link
Owner

simeg commented Nov 28, 2017

Like git commit vs. git commit -m [msg]. Sometimes you just want to write down something small, eureka should support this use-case as well.

@travv0
Copy link

travv0 commented Mar 20, 2019

I agree with this. I'm trying it out, and after thinking of something I'll enter it at the prompt and then be presented with my editor, despite already having entered the thing I thought of. (I'm also not really sure if there's a certain format I should be entering text into the readme in. Just newline-separated by idea I guess?)

@simeg
Copy link
Owner Author

simeg commented Mar 20, 2019

@tssund93 What you're doing when you're storing an idea is making a git commit. So the first step is the subject of the commit (what you'll see when you run git log --oneline) and how you structure your ideas in the README is up to you. I separate my ideas by a line of - characters.

But it's interesting that you bring it up - I assumed everyone thought about it like me but obviously not. The problem with not having your ideas in the README, but only in the git log, is that you would have to go to multiple places to see all of your ideas.

@travv0
Copy link

travv0 commented Mar 21, 2019

I was thinking it would be nice if there was a command that would take the commit message you enter and duplicate it in the readme, but obviously then there would have to be a specific way the readme is structured. So doesn't really make sense, I suppose.

@tahervali
Copy link

So I really think, That the usecase where we enter new creates a new Read.md file will also cater to the use case we are discussing here.
@simeg @travv0

What do you think?

I could take up the creating new read.md for every Idea first(Giving the user an option to choose whether to create a new read.md or use the old one)

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

No branches or pull requests

3 participants