Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
GLib
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 924
    • Issues 924
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 58
    • Merge Requests 58
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • GLib
  • Issues
  • #2093

Closed
Open
Opened Apr 23, 2020 by Ailin Nemui@Nei

g_utf8_get_char_validated function that can accept U+0000?

A question about !967 (merged) and our use of g_utf8_get_char_validated in a downstream project (irssi).

GLib 2.64 is slowly trickling into production and now we have a growing number of people that are freezing their Irssi IRC clients by pressing Ctrl+Space. The reason is that utf8_get_char_validated was changed to reject Ctrl+Space aka NUL with -2.

According to the docs, " a partial sequence [...] that could begin a valid character ". Now the logic in our app used to be this: as long as -2 is returned, continue reading and accumulating terminal input in a buffer with a length, trying to build up valid UTF-8 characters. What should we do?

cf. https://github.com/irssi/irssi/issues/1180

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/glib#2093