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

Feature Request: Command History #51

Closed
gsingh93 opened this issue Aug 13, 2013 · 5 comments
Closed

Feature Request: Command History #51

gsingh93 opened this issue Aug 13, 2013 · 5 comments

Comments

@gsingh93
Copy link
Contributor

It would be nice to have a command history, where pressing up would go to the previous command and pushing down would go to later commands.

@misfo
Copy link
Owner

misfo commented Aug 14, 2013

This has already been implemented, it's what the sublime_readline module provides

Sent from my phone

On Aug 13, 2013, at 6:12 PM, gsingh93 notifications@github.com wrote:

It would be nice to have a command history, where pressing up would go to the previous command and pushing down would go to later commands.


Reply to this email directly or view it on GitHub.

@gsingh93
Copy link
Contributor Author

I see. Looks like this is another issue with ST3. I don't think I'm going to look into this one, but if you have time to fix it, that would be great. Here is the error that occurs whenever I press up or down:

TypeError: run_() takes 2 positional arguments but 3 were given

@mreinhardt
Copy link

I have a similar but different problem with command history on ST3.

If I push up I get the last command, but if I then press enter I get the following output regardless of the command:

shell_cmd or cmd is required
[cmd: ]
[dir: /Users/mikereinhardt/dev/project/]
[path: /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin]
[Finished]

If I instead push up to get the last command, select and cut, push down and paste, hit enter, then the command is executed.

@misfo
Copy link
Owner

misfo commented Dec 3, 2013

@mreinhardt looks like this is the same issue as #55. Thanks for the details. Going back in the shell history is what triggers the issue

@misfo
Copy link
Owner

misfo commented Sep 9, 2015

This was fixed way back in a24bc8e

@misfo misfo closed this as completed Sep 9, 2015
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