Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 873
    • Issues 873
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 37
    • Merge requests 37
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • GLib
  • Issues
  • #3094

bugreport: regex escape

Hi

I think have found a bug while using Midnight Commander's extension/file matching feature.

It seems that the glib 2.76.4->2.76.5 upgrade broke a regex-filematching. (Same goes for 2.77.2->2.77.3)

Example:

mc.ext.ini:

[something] Regex=.my_extension$ Open=echo "opening: " %f

This does not match anymore for asdf.my_extension. The problem is the ".".

git bisect points me to these commits on both minor versions:

2.76.4->5: 3fd1b634 2023-08-29 15:32:27 +0200 | gkeyfile: Fix overwriting of GError

2.77.2->3: 71b7efd0 2023-08-29 15:32:27 +0200 | gkeyfile: Fix overwriting of GError

On first glance it has something to do with backslashes, but it might be a midnight commander bug after all.

core/glibc 2.38-3

extra/mc 4.8.30-1

core/linux 6.4.12.arch1-1

Br,

Tibor

Assignee
Assign to
Time tracking