Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xrdb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • xorg
  • app
  • xrdb
  • Merge requests
  • !2

Add actual querying capabilities to -query

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Michele Guerini Rocco requested to merge rnhmjoj/xrdb:query into master Oct 01, 2020
  • Overview 1
  • Commits 1
  • Changes 2

The world is littered with broken grep commands because xrdb -query can only dump the database and doesn't implement this simple search feature.

Things I tested:

  • xrdb -query without arguments works the same as before

  • xrdb -query prop prints the value of prop when it exists in the resource database.

  • xrdb -query prop doesn't print anything when prop doesn't exist in the resource database.

  • xrdb -query prop doesn't leak any memory. I run it in valgrind with the --leak-check=full option.

PS: I think Sun took care of the fputs thing by now.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: query