libretro / libretro/RetroArch

[Feature Request] Start directory for Load Configuration

Open
#14,378 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Curent behavior

We have 1 option for this in Settings/Directory:

Configs:
Set the start directory for menu configuration browser

But that description is not really all it does, it kinda secretly does 2 things at the same time:

  • Sets where the core overrides/configs/shaders are located.
  • Sets as a start directory for the Load Configuration browser.

Expected behavior

I would like to separate those 2 behaviors into 2 different Directory settings to distinguish RetroArch's main config files from Core files:

RetroArch Configs:
Sets as a start directory for the Load Configuration browser. (Where you manually load main RetroArch config files)

Core Configs:
Sets where the core overrides/configs/shaders are located.

This means I could have a folder with multiple RetroArch configs neatly named and organized in a folder, and not have to go looking for it every time I go into Load Configuration because it starts in the core configs folder.

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

Start by tracing the Settings/Directory entry for the current Configs path and the Load Configuration browser. Determine where the same directory value is used for core overrides/configs/shaders and for browsing RetroArch config files. Done means separate settings control those two locations independently.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.