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

issue #273 #552

Merged
merged 1 commit into from
Oct 13, 2015
Merged

issue #273 #552

merged 1 commit into from
Oct 13, 2015

Conversation

spokorski
Copy link
Contributor

pressing shift-enter in the command sender will suppress the trailing enter key in the
commands actually sent to the putty sessions. pressing enter by itself will still function as
normal.

pressing shift-enter will suppress the trailing linebreak in the
commands being sent.  pressing enter by itself will still function as
normal, including the linebreak in the sent commands.
@jimradford
Copy link
Owner

Can you briefly explain under what circumstances this would be useful for? I am not oposed to the change just want an idea of when it might be used.

@spokorski
Copy link
Contributor Author

Primarily I use this for VIM. for example, k to go up one line would be followed by a line break, causing the cursor to go back down a line. likewise, j would go down 2 lines instead of one. this is especially annoying when editing a line, as the additional line break would need to then be deleted.

issue #273 voices similar concerns, and other people may have additional uses for this functionality

jimradford added a commit that referenced this pull request Oct 13, 2015
issue #273 allows control+enter to bypass sending carriage return, useful for vi keystrokes
@jimradford jimradford merged commit 1a71106 into jimradford:master Oct 13, 2015
@jimradford
Copy link
Owner

@spokorski Thanks, that makes sense and is a good use case. I've merged in your changes.

@larsen0815
Copy link

Tested with 1.4.0.9 and this doesn't seem to work:

  • I've entered "ls" and pressed Shift+Enter
  • I expected to get "ls" on the command line of my session
  • However, the command "ls" was executed which I suppose shouldn't be the case

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

Successfully merging this pull request may close these issues.

3 participants