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

Broken Embedded Ruby #57

Closed
bardsley opened this issue Oct 4, 2013 · 4 comments
Closed

Broken Embedded Ruby #57

bardsley opened this issue Oct 4, 2013 · 4 comments

Comments

@bardsley
Copy link

bardsley commented Oct 4, 2013

The embedded ruby shortcut (^> by default) now apears to work the first time but used to toggle between

<%= %>
<% %>
<%# %>
<%= -%>

Or potentially a different order. I think issue 36 maybe be part of the problem but can't find anyway after playing with git to go back to earlier to fix this. Currently ^> work as expected first time then inserts => for each click after (presumably the hash pointer command? )

@bardsley
Copy link
Author

bardsley commented Oct 4, 2013

Disabling has pointer fixes this but I think it might be worth removing this conflict by default perhaps?

@elia
Copy link
Contributor

elia commented Oct 5, 2013

related: #36

@eheiberg
Copy link

eheiberg commented Nov 4, 2013

"Disabling has pointer fixes this"
I'm sorry. I'm not that familiar with Textmate enough to understand how to do this. I'm assuming that this is a workaround? Thanks in advance for any guidance on this.

@sorbits
Copy link
Member

sorbits commented Nov 4, 2013

I think it was a typo — @infininight rebound the hash pointer snippet to ⌃> (issue #36) which is what broke the cycling behavior.

At least that is how I interpret the above.

You can locally remove the key binding or join #textmate IRC on freenode and pester @infininight to fix this ;)

On Nov 4, 2013, at 19:53, eheiberg notifications@github.com wrote:

"Disabling has pointer fixes this"
I'm sorry. I'm not that familiar with Textmate enough to understand how to do this. I'm assuming that this is a workaround? Thanks in advance for any guidance on this.


Reply to this email directly or view it on GitHub.

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

4 participants