libretro / libretro/RetroArch

[Feature Request] Support ~ in playlist

Open
#19,017 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

In retroarch.cfg it is possible to use ~ to denote a path to the current user directory.

For example

rgui_browser_directory = "~/games"
rgui_config_directory = "~/.config/retroarch/config"

This makes it easy to synchronize the configuration file between different devices.

Playlists on the other hand, does not seem to support this feature

Example

{
    "version": "1.5",
    "default_core_path": "",
    "default_core_name": "",
    "label_display_mode": 0,
    "right_thumbnail_mode": 0,
    "left_thumbnail_mode": 0,
    "sort_mode": 0,
    "items": [
        {
            "path": "~/games/psp/supertux/Supertux/EBOOT.PBP",
            "label": "SuperTux PSP",
            "core_name": "Sony - PlayStation Portable (PPSSPP)",
            "core_path": "~/.config/retroarch/cores/ppsspp_libretro.so",
            "crc32": "00000000|crc",
            "db_name": "Sony - PlayStation Portable"
        }
    ]
}

I get the error message "Failed to load from playlist".

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides retroarch.cfg and a playlist JSON example, but no source file or test. Start by finding playlist loading and the existing path handling for ~ in configuration; done means a playlist using ~ loads successfully without breaking absolute paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.