Dev Build 3127

[lastsecondsave]

When I try to scroll sidebar up with touchpad it doesn’t move up, it only bounces up and down. It will go up if I scroll faster. Horizontal scrolling has the same behavior too. Other controls work fine, it’s only the sidebar. With mouse wheel it forks fine as well.

I’m on Windows 10 and I have a precision touchpad.

[braver]

Minor visual glitch: On macOS, changing the color scheme makes the Adaptive theme lose its rounded corners (all four). The corners stay angular even when changing to the Default theme.

(I know I shouldn’t switch color schemes all the time but it’s an affliction… )

[wbond]

Minor visual glitch: On macOS, changing the color scheme makes the Adaptive theme lose its rounded corners (all four). The corners stay angular even when changing to the Default theme.

Yes, that has been identified and I will be working on a fix for one of the next several builds.

[cyan]

Using the latest builds (3127, 3128, 3129) on Mac, the yellow circle icons in the side bar denoting unsaved open tabs/files are cut off by half, showing just the right halves (see image).

A minor glitch, hope it can be fixed in the next build. Thanks!

[stuartherbert]

Hi Will,

1. Files already in the folder aren’t indexed - but do appear in the sidebar.
2. Files added to the folder aren’t indexed - and do not appear in the sidebar at first.
3. Collapsing and expanding the folder shows the added file. Does not add the file to the index.
4. Folder isn’t a symlink, and neither are any of the parents. Permissions are fine too.
5. When I click on a file in the sidebar, and that file hasn’t been indexed, the file’s tab opens just fine - but the file isn’t highlighted in the sidebar (even though that’s exactly where I clicked on it)
6. Clicking ‘Refresh Folders’ appears to trigger no action. There’s no measurable CPU increase (which I’d expect with re-indexing), no status bar indexing indicator, and no new Indexing job listed in the Indexing Status window.

Destroying the index entirely to force a rebuild doesn’t change which files get indexed. It’s always the same folders (and their contents) that don’t get indexed (so far). It appears deterministic and reproducible.

Dev builds prior to 3127 had no trouble at all with these files and folders.

I can’t find much information to help speculate on what the cause is, sorry.

• The index status reaches 99%, and there’s no obvious error messages in the index log (assuming I’m looking at the right log, of course!), so it doesn’t look like the indexer is crashing out.
• If it was me, my next step would be to get the indexer to log each file it examines, to isolate the problem either in the filesystem crawling code or in the index data structure code.

Is there anywhere I can look for information that would help with this? Any settings that I can switch on to gather more information? Very happy to help you diagnose this any way that I can

Some more sidebar behaviours observed in 3129:

• if I collapse a folder, sometimes a different folder is collapsed in the sidebar instead
• if I collapse a folder, sometimes the correct folder is collapsed, but one or more child files are still shown
• if I delete a folder via the sidebar’s right-click menu, sometimes a different folder is removed from the sidebar instead (this may be a different folder under the same parent, but sometimes it’s a top-level folder that’s removed)
• when I expand a folder, sometimes the same file is shown twice in the folder

When these glitches occur, some of the sidebar icons disappear.

Hope that helps.

[steveooo]

I really like it when people are trying to help to make Sublime Text better. Speed and stability are the 2 main feature points, so I hope that stability gets better or back to “normal”

[davidong]

Thanks the hard work for upgrading sublime text 3.
All the things work fine for me.
But is there anyway I can open project as a new tab instead of a new window in the newest version at the fullscreen mode because I can do that in the older version?

[wbond]

I hope that stability gets better or back to “normal”

If stability is of higher priority to you than new features, you should try running the beta channel instead of the dev channel.

Dev is where we are going to be doing (sometimes significant) work, and there will certainly be some rough edges. This last cycle was six months of work, so there were a number of things changed and improved, each with some edge cases to be found.

[wbond]

[arvin]

Yes - a good reminder.

And when you consider you guys are a (now) two-man crew, supporting all three major operating systems and almost 12 M users, is nothing short of amazing. Thanks again!

[rppn]

I can reproduce this issue.

[braver]

@wbond Is there documentation for customising the phantomCSS in a color scheme? I’m specifically looking for a way to tweak the color of the new pointer nubbin on the inline build errors.

[rppn]

• https://www.sublimetext.com/docs/3/color_schemes.html#css
• https://www.sublimetext.com/docs/3/minihtml.html#css

[wbond]

@wbond Is there documentation for customising the phantomCSS in a color scheme?

There is not an enumeration of the different CSS classes that the Default package uses, no. You could use the PackageResourceViewer to check out exec.py to see the default HTML and CSS.

[braver]

You could use the PackageResourceViewer to check out exec.py to see the default HTML and CSS.

Thanks, that helps. I can’t for the life of me get the nubbin to change color though. It seems like div.error-arrow should be the correct selector, and changing border-left: 0.5rem solid color(var(--redish) blend(var(--background) 30%)); should result to something.

That said, I kinda get the feeling that setting popupCss and phantomCss in a color scheme is an uphill battle since you don’t have any idea what the actual html will be like. It’s kinda like theming for Atom, you just set the defaults and hope package devs don’t make a mess of it. In this case I think I’ll just let the default generated styles take care of themselves rather than waste time trying to tweak it to taste. It’s not like it’s ugly or anything, it’s simple and neat as it is.

[wbond]

I can’t for the life of me get the nubbin to change color though.

Because of CSS specificity, you’ll need your phantomCss to utilize the selector body#inline-error div.error-arrow. Otherwise the <style> tag in the phantom’s HTML will override any definition for div.error-arrow you provide.

[braver]

Because of CSS specificity, you’ll need your phantomCss to utilize the selector body#inline-error div.error-arrow.

Alright, thanks!

Edit: doesn’t work either, or doesn’t update live, or something. But I’m going to let it rest, the defaults do a good enough job now that I’d rather not try to maintain the customisation anyway.

[braver]

The sidebar still seems unable to remove the correct folder. See the gif below, if I right-click delete a folder, the correct folder is removed from the file system, but the sidebar updates incorrectly. Folding and unfolding restores it.

It almost seems like if I delete the third child folder, it starts counting from the project root and removes the third folder.

edit… the gif not animating for other people either?

[wbond]

The sidebar still seems unable to remove the correct folder.

This is being tracked at https://github.com/SublimeTextIssues/Core/issues/1657

[schlamar]

Another sidebar issue in 3129: Sometimes if I want to open a file from the sidebar, the wrong file is opened (the file above or below the selected item).

(Windows 7 64bit)