[rcombs]

Saving ASS subtitles now writes current project settings to .aegiconf-[full filename] by default, keeping local project state out of subtitle diffs. When Save Project Settings in Subtitle File is disabled, existing in-file settings are preserved as loaded rather than removed or updated; files without them remain without them. Legacy settings in [Script Info] may migrate into [Aegisub Project Garbage] while retaining their loaded values.

Load shared .aegiconf files from ancestor directories, then the per-subtitle config, with closer files overriding earlier ones. Discovery stops at Git and filesystem boundaries. Loading any matching config, including an empty file, discards all inline project settings from the active configuration while retaining their load-time values for saving. Legacy settings remain the fallback when no config is loaded.

Support ordered video, audio, keyframe, and timecode patterns relative to the subtitle directory, plus Audio File: ?video. Pattern-derived paths are omitted from saved overrides, and comments, unknown directives, and active patterns are preserved. The Save Project Settings in Subtitle File preference updates inline settings when enabled; config loading can be disabled separately. Recovery autosaves retain embedded project settings and resolved paths.

Includes separate filesystem utility commits, documentation, and regression coverage for config precedence, legacy-setting replacement, relative paths, patterns, discovery boundaries, repeated saves, and preservation of original inline settings.

🤖 Codex

[JohhanSam]

This is a really cool feature, went to port it when I saw it on my feed with my agent and it flagged a few issues:

• A broken or unreadable .aegiconf file can stop a subtitle from opening at all. Some fallback would be good.
• Recovery autosaves can lose their media links. Opening one re-runs config discovery from the autosave folder instead of the project folder.
• The two new preferences interact badly. One combo silently reverts saved changes on reopen. Another combo saves settings nowhere.
• Saving writes sidecar files for non-ASS formats like SRT.
• Opening a video silently marks timecodes and keyframes as cleared, and that sticks in the sidecar.
• Pattern matching differs across platforms, like case sensitivity and bracket handling.
• The Windows mount point check misses cross-volume directory symlinks.
• Timecodes and keyframes erases get clobbered by the restore logic, which is fragile.
• Audio from video can leave a stale "?video" reference after closing the video.
• Automation Scripts paths are not resolved in recovery files.
• Error messages don't say which config file failed.
• If config saving fails after the subtitle is written, the user is told the save failed with no detail.

[9vult]

I'm not sure having this be a dotfile is the best idea when most platforms hide dotfiles in the file explorer by default. While it is cleaner to have them hidden, having visible files ensures the user knows they exist (and can rename/delete them when renaming/deleting the ass file)

[rcombs]

Being hidden (and thus unobtrusive) by default is the point. Could equivalently put it in a database in the user data dir, but this seemed cleaner. I suppose the rename concern is valid, but imo it's fairly minor (nothing in project garbage is that important), and renaming stuff willy-nilly has gotten a lot less common in the git era anyway.