Sublime Forum

Show definitions bug

#1

New in Sublime 3124 is “show_definitions”, or sd (for short). This bug creates a massive number of useless popups everywhere. For example, I link to a local PNG file wile coding an HTML page, and the bug popup hides the png path, displaying the garbage shown in the following clip.

Click on page, popup disappears and back to code that displays my PNG image. Click on “Definition” popup link and browser opens garbage data page. “Definition” has nothing to do with any branch of HTML web design that I have ever heard about. What is the “Definition” popup about? From sublime text site somewhere:
“shows where a symbol is defined when hovering over it [also, obstructs coding when cursor moves close to content that triggers ‘definition’ popup]… makes use of the new on_hover API [messed up with cursor moves], and can be controlled via the show_definitions setting [that does not exist, depending on version and who knows what else]”

Where is ‘show_definitions’ setting? Did not find it searching version 3114 Settings - Default.

1 Like
#2

Just open Preferences > Settings and on the right side on a reasonable position (e.g. behind the first opening {) add a line with the content:

    "show_definitions": false,
4 Likes
#3

Tested “show_definitions”: false in Settings - User for ST version 3114, which predates the appearance of Definition bug (version 3124). Adding “show_definitions”: false to user settings appears to cause the removal of built in in-line CSS style elements.

For example, after adding the setting suggested by r-stein, now when coding in-line style, cursor activates the style properties popup

however, the color property is gone, and options remaining appear to be HTML tags only. The popup is stripped of style properties whenever accessed.

show_definitions from the new On-Hover API’ and “show_definitions”: false setting are both bad news for everyone using Sublime to code CSS.

0 Likes
#4

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

0 Likes
#5

Try posting again when you’re not drunk.

1 Like
#6

OPS: please remove the “svenax” post.

0 Likes
#7

More ‘Definition’ popup problems.

While testing Settings - User entries to manage Show definitions bug, Sublime stopped supporting Docsys4: at least, Sublime app started flagging new coding conventions as errors.

Is this due to Sublime app owners responding to this post (albeit clumsily), or more unmanaged bad news.

0 Likes
#8

It’s ok, he’s taken his medication now.

0 Likes
#9

Show Definitions was added in build 3116. You must be using a version of Sublime Text newer than 3114. The setting to disable the show definitions popup definitely works.

There is no interaction between the show popup dialog and your CSS completions. The completions list for the example you provided properly shows color for me. It may be that you have an old version of the HTML package, or are using a custom HTML syntax rather than the default.

Based on the screenshots you have posted, you are either using a version of Sublime Text older than build 3126 (the newest beta build), or you are not using the default CSS syntax. The default CSS syntax in build 3126 handles the snippet of CSS you posted without issue.

You can check to see if your customizations are the issue by shutting down Sublime Text, moving your existing data folder to another location, and restarting Sublime Text. This will revert your setup to a stock install, and you can check to see if your CSS and HTML issues are resolved.

0 Likes
#10

Thank you for reference to http://www.sublimetext.com/docs/3/revert.html [moving your existing data folder to another location]. I removed 3114, observing app logical arguments tangle very similar to those that you so eloquently describe. I will now download and install current beta 3126.

Whilst we have your attention, wbond when do you think we will see alpha ST3 and beta ST4?

:electric_plug: What seems to be the catch for waiting-and-watching web designers is modern code consolidation. Sublime Text has to consolidate arguments for CSS3 and HTML5 syntax vis-a-vis code hinting colors for schemes and themes and (naturally) the useful and instructional code popups. PackageControl.io CSS3 and HTML5 plugins are becoming too cryptic, problematic. That is what stands out for me in your reply. We all use those plugins. They are causing problems. Not just this STICKY! “Definition” bug that REPEATEDLY! renders ST useless on my company’s Mac Pro. CSS3 and HTML5 should be alpha, not beta. How difficult can that consolidation be?

FYI My usual ST3 plugin population, in order of install - ST2 same, minus PRV:
Package Control || PackageResourceViewer || Theme - Soda SolarizedDark || * CSS Extended Completions * || * CSS Format * || * CSS3 * || HTML Page Snippets || HTML5 || HTML5 Doctor Reset || HTMLAttributes || LoremIpsum || Open URL || ProjectManager || Side​Bar​Enhancements || Can I Use || Google Search || * Search Stack Overflow *

  • asterix* indicates that plugin populates “package Control Messages”
0 Likes
#11

I presume you are referring to ST3 stable? Jon mentioned in the last beta announcement blog post that our next cycle will be focusing on making ST3 the stable release.

There are no current plans for “ST4”, per se. One of the big breaks between ST2 and ST3 was the plugin system (Python 2.6 to Python 3.3), along with updates to the API and internal changes. I’ve got some ideas on how we can move forward in terms of supporting new versions of Python without breaking backwards compatibility like ST3 had to.

The HTML5 and CSS3 packages were developed during a period where the default packages shipped with ST3 did not support all of those new features. Over the past year myself and the community have done a ton of work on the default packages. At the current time, HTML5 and CSS3 support should be in great shape. If you run into issues, report them at https://github.com/sublimehq/Packages.

I can’t speak to the quality of third-party packages. I don’t know which guidelines they follow, or if they try to enhance things in a way that may cause issues.

0 Likes
#12

Re: ST4

relates to (beyond 4.1/2) Docsys5
tuit talk of new versions of PHP, Python and others :evergreen_tree: hope your ideas work in

Re: 3rd party

stack overflow has onerous history of attracting juvenile hoodlums [also ‘hackers 12th’ hangout]
review indicates that Search Stack Overflow somehow screwed CSS3 and ST build ins
ALWAYS where hacks intrude to structure deeper than simple ST use, the removal of ~Library/Application Support/Sublime Text 3 does a nothing to repair damaged app. Further, with the new SIP security in OS X Sierra, ~Library deletions are seldom of any value. 5 other active Libraries regulate installed apps such as Sublime Text. Best way to isolate a particular problem is simply observe, and report.

process: …careful 1-by-1 install plugin and observe both for ST2 and for ST3
observation: …bugs are never immediate, typically appear start of work day ~ typical hack profile
conclusion: …ST3 CSS has been taking the ‘hit’ for quite some time now, sadly

disclaimer: …riverleaf is a trademark web design project and is …

0 Likes