Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
F
flatpak-qt-creator
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Marco Bubke
flatpak-qt-creator
Commits
4d26f334
Commit
4d26f334
authored
May 06, 2010
by
Leandro Melo
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Small change to the behaviour of the highlighter that should help it working with broken files.
parent
44202754
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
2 deletions
+6
-2
src/plugins/genericeditor/highlighter.cpp
src/plugins/genericeditor/highlighter.cpp
+6
-2
No files found.
src/plugins/genericeditor/highlighter.cpp
View file @
4d26f334
...
...
@@ -422,8 +422,12 @@ void Highlighter::pushDynamicContext(const QSharedPointer<Context> &baseContext)
void
Highlighter
::
setCurrentContext
()
{
if
(
m_contexts
.
isEmpty
())
throw
HighlighterException
();
if
(
m_contexts
.
isEmpty
())
{
// This is not supposed to happen. However, there might be broken files (for example, the
// PHP definition) which will cause this behaviour. In such cases just pushing the default
// context is enough to keep highlighter working.
m_contexts
.
push_back
(
m_defaultContext
);
}
m_currentContext
=
m_contexts
.
back
();
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment