You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
A while ago was added context-aware bracket wrapping on this pull. That's great for ruby-style string interpolation, but there is no option to disable it in the settings.
Steps to Reproduce
Expected behavior:
Some way to unable/disable/customize context aware bracket wrapping.
Actual behavior:
Settings do not mention anything about context-aware bracket wrapping
Well, maybe I do not want all of my "#" strings to be replaced with the ruby styled "#{}" as I write in coffeescript. It is a cool feature to have if you are programming in those languages, but if I merely want to do some cson like
tags: [
"#TagA""#TagB""#TagC"
]
Is very annoying to have to erase the {} that context-aware matching generates every time.
This is not an issue with the cofeescript or ruby packages, as it goes away when I disable the bracket-matcher package.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prerequisites
Description
A while ago was added context-aware bracket wrapping on this pull. That's great for ruby-style string interpolation, but there is no option to disable it in the settings.
Steps to Reproduce
Expected behavior:
Some way to unable/disable/customize context aware bracket wrapping.
Actual behavior:
Settings do not mention anything about context-aware bracket wrapping
Versions
packages:
bracket-matcher: 0.91.2
Atom : 1.46.0
Electron: 4.2.7
Chrome : 69.0.3497.128
Node : 10.11.0
apm 2.4.3
npm 6.2.0
node 10.2.1 x64
atom 1.46.0
python 3.7.7
git 2.22.0.windows.1
visual studio
OS: windows 10
The text was updated successfully, but these errors were encountered: