René's URL Explorer Experiment


Title: problems with big strings that contain numbers · Issue #69 · vim-jp/vim-cpp · GitHub

Open Graph Title: problems with big strings that contain numbers · Issue #69 · vim-jp/vim-cpp

X Title: problems with big strings that contain numbers · Issue #69 · vim-jp/vim-cpp

Description: Hi, I had the problem, that vim is not highlighting correctly and stops working when I use string literals in my C++ program that contain big numbers. Here is an example program: #include int main() { puts("12345678901234567891...

Open Graph Description: Hi, I had the problem, that vim is not highlighting correctly and stops working when I use string literals in my C++ program that contain big numbers. Here is an example program: #include ...

X Description: Hi, I had the problem, that vim is not highlighting correctly and stops working when I use string literals in my C++ program that contain big numbers. Here is an example program: #include <stdio...

Opengraph URL: https://github.com/vim-jp/vim-cpp/issues/69

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"problems with big strings that contain numbers","articleBody":"Hi,\n\nI had the problem, that vim is not highlighting correctly and stops working when I use string literals in my C++ program that contain big numbers. Here is an example program:\n\n```c++\n#include \u003cstdio.h\u003e\n\nint main() {\n\tputs(\"123456789012345678912345678912345678912345678912345678900000\");\n}\n```\n\nIt is important to save it as a C++ file (e.g. as `too_big.cpp`) and not as a C file (`too_big.c`). The C syntax highlighter has no problems with this file, but the C++ syntax highlighter slows down vim, so that it will reduce the syntax highlighting and may stop to react completely.\n\nMy configuration is: Macbook Air Apple M1, 16 GB; vim 9.1.1752; vim-cpp from May 2024 04.\n\nPlease change the syntax so that big numbers in string literals don't bother the highlighter. These occur regularly as test cases for text processing tools (e.g. md5). As a workaround you can split the string literal into multiple literals (`\"0-9\" \"0-9\" ...`). That will stop the syntax highlighting from getting angry :-)","author":{"url":"https://github.com/itmm","@type":"Person","name":"itmm"},"datePublished":"2025-12-28T17:23:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/69/vim-cpp/issues/69"}

route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:cc34d85c-4731-9cc1-abbf-1a43f5f8a994
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idCC7C:3026F0:1F5DDE5:2CFEB4E:6A4BDD65
html-safe-nonced9ed1201e1ae45235ce23cd9e179f932be03e4e5c6c53a493d5fd4d66ba68c94
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDQzdDOjMwMjZGMDoxRjVEREU1OjJDRkVCNEU6NkE0QkRENjUiLCJ2aXNpdG9yX2lkIjoiMTQ1MzQ2MTUyMDgwNTI1NjU0OSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmacf0830cd36ed5ebee4effaee6c1ae1146f9005654060d3878b975623fce7620e5
hovercard-subject-tagissue:3765847660
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/vim-jp/vim-cpp/69/issue_layout
twitter:imagehttps://opengraph.githubassets.com/98938fdb16dc1c275041d1aabce7062fb54c8f6fe45745bc7b8bd383461897e4/vim-jp/vim-cpp/issues/69
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/98938fdb16dc1c275041d1aabce7062fb54c8f6fe45745bc7b8bd383461897e4/vim-jp/vim-cpp/issues/69
og:image:altHi, I had the problem, that vim is not highlighting correctly and stops working when I use string literals in my C++ program that contain big numbers. Here is an example program: #include ...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameitmm
hostnamegithub.com
expected-hostnamegithub.com
None0f5d3ba365b3985d75c32a5957c8635488d58dcf027ae6ae958eee7edaa306a2
turbo-cache-controlno-preview
go-importgithub.com/vim-jp/vim-cpp git https://github.com/vim-jp/vim-cpp.git
octolytics-dimension-user_id1051958
octolytics-dimension-user_loginvim-jp
octolytics-dimension-repository_id4631849
octolytics-dimension-repository_nwovim-jp/vim-cpp
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id4631849
octolytics-dimension-repository_network_root_nwovim-jp/vim-cpp
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release253920ac2dc35b0849cca4633895f1f2e5f03051
ui-targetfull
theme-color#1e2327
color-schemelight dark

Links:

Skip to contenthttps://github.com/vim-jp/vim-cpp/issues/69#start-of-content
https://github.com/
Sign in https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fvim-jp%2Fvim-cpp%2Fissues%2F69
GitHub CopilotWrite better code with AIhttps://github.com/features/copilot
GitHub Copilot appDirect agents from issue to mergehttps://github.com/features/ai/github-app
MCP RegistryNewIntegrate external toolshttps://github.com/mcp
ActionsAutomate any workflowhttps://github.com/features/actions
CodespacesInstant dev environmentshttps://github.com/features/codespaces
IssuesPlan and track workhttps://github.com/features/issues
Code ReviewManage code changeshttps://github.com/features/code-review
GitHub Advanced SecurityFind and fix vulnerabilitieshttps://github.com/security/advanced-security
Code securitySecure your code as you buildhttps://github.com/security/advanced-security/code-security
Secret protectionStop leaks before they starthttps://github.com/security/advanced-security/secret-protection
Why GitHubhttps://github.com/why-github
Documentationhttps://docs.github.com
Bloghttps://github.blog
Changeloghttps://github.blog/changelog
Marketplacehttps://github.com/marketplace
View all featureshttps://github.com/features
Enterpriseshttps://github.com/enterprise
Small and medium teamshttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
App Modernizationhttps://github.com/solutions/use-case/app-modernization
DevSecOpshttps://github.com/solutions/use-case/devsecops
DevOpshttps://github.com/solutions/use-case/devops
CI/CDhttps://github.com/solutions/use-case/ci-cd
View all use caseshttps://github.com/solutions/use-case
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
View all industrieshttps://github.com/solutions/industry
View all solutionshttps://github.com/solutions
AIhttps://github.com/resources/articles?topic=ai
Software Developmenthttps://github.com/resources/articles?topic=software-development
DevOpshttps://github.com/resources/articles?topic=devops
Securityhttps://github.com/resources/articles?topic=security
View all topicshttps://github.com/resources/articles
Customer storieshttps://github.com/customer-stories
Events & webinarshttps://github.com/resources/events
Ebooks & reportshttps://github.com/resources/whitepapers
Business insightshttps://github.com/solutions/executive-insights
GitHub Skillshttps://skills.github.com
Documentationhttps://docs.github.com
Customer supporthttps://support.github.com
Community forumhttps://github.com/orgs/community/discussions
Trust centerhttps://github.com/trust-center
Partnershttps://github.com/partners
View all resourceshttps://github.com/resources
GitHub SponsorsFund open source developershttps://github.com/sponsors
Security Labhttps://securitylab.github.com
Maintainer Communityhttps://maintainers.github.com
Acceleratorhttps://github.com/accelerator
GitHub Starshttps://stars.github.com
Archive Programhttps://archiveprogram.github.com
Topicshttps://github.com/topics
Trendinghttps://github.com/trending
Collectionshttps://github.com/collections
Enterprise platformAI-powered developer platformhttps://github.com/enterprise
GitHub Advanced SecurityEnterprise-grade security featureshttps://github.com/security/advanced-security
Copilot for BusinessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/premium-support
Pricinghttps://github.com/pricing
Search syntax tipshttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
documentationhttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
Sign in https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fvim-jp%2Fvim-cpp%2Fissues%2F69
Sign up https://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=vim-jp%2Fvim-cpp
Reloadhttps://github.com/vim-jp/vim-cpp/issues/69
Reloadhttps://github.com/vim-jp/vim-cpp/issues/69
Reloadhttps://github.com/vim-jp/vim-cpp/issues/69
Please reload this pagehttps://github.com/vim-jp/vim-cpp/issues/69
vim-jp https://github.com/vim-jp
vim-cpphttps://github.com/vim-jp/vim-cpp
Notifications https://github.com/login?return_to=%2Fvim-jp%2Fvim-cpp
Fork 45 https://github.com/login?return_to=%2Fvim-jp%2Fvim-cpp
Star 149 https://github.com/login?return_to=%2Fvim-jp%2Fvim-cpp
Code https://github.com/vim-jp/vim-cpp
Issues 11 https://github.com/vim-jp/vim-cpp/issues
Pull requests 6 https://github.com/vim-jp/vim-cpp/pulls
Actions https://github.com/vim-jp/vim-cpp/actions
Projects https://github.com/vim-jp/vim-cpp/projects
Wiki https://github.com/vim-jp/vim-cpp/wiki
Security and quality 0 https://github.com/vim-jp/vim-cpp/security
Insights https://github.com/vim-jp/vim-cpp/pulse
Code https://github.com/vim-jp/vim-cpp
Issues https://github.com/vim-jp/vim-cpp/issues
Pull requests https://github.com/vim-jp/vim-cpp/pulls
Actions https://github.com/vim-jp/vim-cpp/actions
Projects https://github.com/vim-jp/vim-cpp/projects
Wiki https://github.com/vim-jp/vim-cpp/wiki
Security and quality https://github.com/vim-jp/vim-cpp/security
Insights https://github.com/vim-jp/vim-cpp/pulse
problems with big strings that contain numbershttps://github.com/vim-jp/vim-cpp/issues/69#top
https://github.com/itmm
itmmhttps://github.com/itmm
on Dec 28, 2025https://github.com/vim-jp/vim-cpp/issues/69#issue-3765847660
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.