-
Notifications
You must be signed in to change notification settings - Fork 181
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
Defaulting value to another value bug #59
Comments
I don't know whether this is even supported - neither do I think I would About your description: |
I'm quite sure that current vim-snipmate implementation doesn't provide this feature. So, if we agree I could label this issue as a feature request and change the title to "support for using placeholders for default values" or something better you could sugget. We can leave it open until we find a good way to do it. P.S. @MarcWeber What Do you think about labeling issues? I can do it if you like the idea. |
I use the following snippet with original repo and this fork without any problem for ages:
If it is working and was working than this issue is bug. |
So can you describe in more detail what broke exactly? |
Broken thing is:
This was working before. |
Excerpts from Bogdan Gusiev's message of Tue Oct 18 10:25:41 +0200 2011:
|
Did a little more investigation and found out that not selected second value bug appear only when ${1} do not have default value. So the following:
Works And the following:
Doesn't work. Sorry for messing you, Marc. |
Excerpts from Bogdan Gusiev's message of Tue Oct 18 11:12:41 +0200 2011:
I'd prefer the README because its more likely that people read it and |
This happens because of the way SnipMate keeps track of and updates everything. It simply stores the line number and column number of where tab stops and variables start and end. This simplistic way means that there's no real way to tell that in There is no easy way to fix this using the current implementation. However, I'm going to leave this issue open in case I manage to think of something clever. |
This seems to have been fixed along with the work on allowing nested stops. Note: This is only fixed for |
Let's say we have the following skippet:
k.snippet:
Key sequence:
ik<Tab>hello<Tab>
should:The text was updated successfully, but these errors were encountered: