Uploaded image for project: 'Appcelerator Studio'
  1. Appcelerator Studio
  2. TISTUD-6926

Support use of environment variables as default tabstop values in snippets

    Details

    • Type: Bug
    • Status: Open
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: Release 3.4.0
    • Fix Version/s: None
    • Component/s: Editor
    • Labels:
      None
    • Sprint:
      To Be Scheduled

      Description

      If a snippet uses syntax like this:

      "${0:${TM_SELECTED_TEXT}}"
      

      We don't understand that at all. What should happen is that we place the cursor at that location in the snippet, with the previously selected text pre-filled in for that tabstop (and still selected). Right now, SnippetTemplateTranslator falls down parsing the double nesting of the curly braces and leaves the second close curly around. Additionally, as mentioned in TISTUD-6925, we don't support the TM_SELECTED_TEXT env var. And, even if we did, I don't think our tabstop and env variable resolvers for templates can handle being nested inside one another (so a tabstop's default value is that of the env var's).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cwilliams Christopher Williams
                Reporter:
                vchidambaram Visalakshi Chidambaram
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: