Closed agarzola closed 8 years ago
I have just installed the fresh copy of sublime text 2 and the master of Stylus plugin and I can't actually reproduce the original bug you described. Could you please let me know which plugins do you have besides Stylus?
Probably too many. Here’s the result of running ls
on my Packages directory.
0_package_control_loader
ASP
ActionScript
AppleScript
Batch File
C#
C++
CSS
Clojure
Color Scheme - Default
D
Dayle Rees Color Schemes
Default
Diff
EJS
Emmet
EncodingHelper
Erlang
FakeDataGenerator
FakeImg Image Placeholder Snippet
Figlet Big ASCII Text
GitGutter
GitHub Flavored Markdown Preview
Go
Graphviz
Groovy
HTML
HTMLBeautify
Haml
Handlebars
Haskell
Hayaku - tools for writing CSS faster
JSHint Gutter
Jade
Java
JavaScript
JavaScriptNext - ES6 Syntax
LESS
LaTeX
Language - English
Lisp
Logs Colorize
Lua
Makefile
Markboard
Markdown
Markdown Preview
MarkdownEditing
Matlab
OCaml
Objective-C
Origami
PHP
Package Control
PackageDev
Perl
PyV8
Python
R
Rails
Regular Expressions
RestructuredText
Ruby
Ruby Slim
SQL
Sass
SassBeautify
Scala
Schemr
ShellScript
Six - Future JavaScript Syntax
Stylus
SyncedSideBar
Syntax Highlighting for Sass
TCL
Text
Textile
Theme - Afterglow
Theme - Aqua
Theme - Default
Theme - Farzher
Theme - Nexus
Theme - Spacegray
Themr
Tomorrow Color Schemes
Unquote
User
Velocity
Vintage
XML
YAML
bz2
caniuse_local
ordereddict
pygments
pyyaml
If you have time and access to some VM or are ok temporarily replace your packages folder could you please confirm that the error actually happens on sublime text 2 without any packages besides Stylus.
Since I can't confirm the bug I'm a bit hesitant to merge this.
You are correct. With only the core packages and the Stylus package, this issue does not occur.
Thank you for pointing me in the right direction! I always thought it had to do with Stylus package since it’s the only syntax with which I’ve observed this bizarre behavior. I’ll close this pull request, nail down where the conflict is occurring and report any findings in #72.
Thanks again!
This addresses the problem described in #72.