Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug: Setting Error after Update 1.10.0
See original GitHub issueDescribe the Bug
After I installed the 1.10,0 version, the Setting configuration for Linter messed up
How to Reproduce
Steps to reproduce the behavior:
- Update to 1,10,0
- Open Setting (Ctrl+P)
- Find Linter in the Setting
Expected Behavior
Just showing Linter in the Setting Menu
Screenshots
Device
- Desktop
- Mobile
Additional Context
Windows 10; Obsidian 1.18.0
Issue Analytics
- State:
- Created 9 months ago
- Comments:6
Top Results From Across the Web
Mailspring won't open after update 1.10.0 - Bug Reports
Description Got a notification in Mailspring saying there is an update available, and after installing it I can never open Mailspring again.
Read more >Trouble updating to Anaconda Navigator 1.10.0 (MacOS)
Run Anaconda Prompt (Administrator mode) Run the command: conda install anaconda-navigator=2.2. 0. Run the command: conda update --all.
Read more >[bug] link error when using spdlog/1.10.0 #12299 - GitHub
a with above original version. It works. I notice these two libspdlog.a are different size. the logs: fmt/8.1.1: Already installed!
Read more >brush problem in 1.10.0 - Photo V1 Bugs found on Windows
The brush settings have been broken since version 1.9. Color select on Alt is a separate kind of masochism. Windows ink support is...
Read more >Bug listing with status RESOLVED with resolution FIXED as at ...
Bug listing with status RESOLVED with resolution FIXED as at 2022/12/24 19:46:07.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No worries. I am glad to hear that it is fixed. I will go ahead and close this.
The timing was wrong on my end. It is under a second still. I will just go ahead with the patch and hopefully it will fix the issue.