Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open large files as plain text #2364

Closed
menzow opened this issue Jun 22, 2018 · 2 comments
Closed

Open large files as plain text #2364

menzow opened this issue Jun 22, 2018 · 2 comments
Labels
R: duplicate

Comments

@menzow
Copy link

menzow commented Jun 22, 2018 •
edited

Summary

Sublime text struggles with opening large JSON documents. I get a 40% faster 'first interactive' view of a document when I rename it to .txt. After disabling word wrapping I gain an additional 15% performance.

...

Expected behavior

Disable word wrapping and highlighting if it will have a big impact on load time. Move the highlighting task into the background and apply when ready. Don't apply word wrapping if document size impacts the users ability to resize the window.

...

Actual behavior

Sublime text opens documents with code highlighting and word wrapping enabled by default for some file extensions.

...

Steps to reproduce

  1. Find a big json document
  2. Open it in sublime text, measure the time.
  3. Remove the .json extension from the filename and reopen the document. The editor will let you view the doc a lot faster

Environment

  • MBP.2013.
@keith-hall
Copy link
Collaborator

If I understand right, this is a feature request, so that when ST opens large files (whereby what "large" means is defined in the user preferences, I guess), it should override the normal/syntax specific preferences (with large-file.sublime-settings, for example), which would disable word wrapping and set the syntax to Plain Text?

There's another issue open where large file support is being discussed: #358.

@FichteFoll
Copy link
Collaborator

I'd like to close this as duplicate and keep discussion regarding big files to the existing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
R: duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@FichteFoll @menzow @keith-hall