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.
Allow configuring comments
See original GitHub issueParsing a pattern argument
If an argument contains /*. then only the text before ‘/’ is taken as the argument.
for example, if a/*.txt is the argument value given, then the command only takes ‘a’ as its argument.
use case: Filenames can’t be globbed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Choose comment settings - YouTube Help
Change your default comment settings · Sign in to YouTube Studio. · From the left-hand menu, select Settings. · Select Community and then...
Read more >Enable and Disable Comments | WordPress.com Support
In Settings. You can enable or disable comments on all future posts by going to Settings → Discussion. Under “Default Article Settings,” toggle...
Read more >Settings to Allow Comments on Documents and Envelopes
To enable comments and manage the settings for them, you must be an administrator with All Administration Capabilities.
Read more >Comments in WordPress
Before you enable comments on posts or Pages, reviewing the options under Settings > Discussion can help make your life as a moderator...
Read more >Set up and moderate blog comments
Customize comment settings ... Click to toggle the Turn on commenting switch on. ... Please note: if Moderate comments and Allow comments to...
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
Uhoh, I just made an oopsie 😦 I had a local branch with this change which was tracking master. When I pushed the change, it went to master. So no PR, because it’s already been committed on master.
Sorry guys.
But I have fixed the issue by not treating C-style comments as comments unless they are closed properly, and have unit tests to verify correct behavior.
I manually verified that the fix already merged to master works well. So I am closing this issue.