trailing_spaces_at_eol in url.zig - conflicting with pi tui

[ruseel]

What do you want to change?

I want to change behavior of path matching in src/config/url.zig
to exclude trailing space at line.

In my setup ghostty + pi tui, FilePath is not clickable in 1.3.1.
With the full help of gpt-5.6 terra high, reason was narrowed to pi tui.

pi is updating screen with

CSI 2K # Erase Entire Line

then outputing

line

So terminal is filled with blank space
and path is overwritten.
Then space is remained in terminal.

and url.zig is matching path including tailing space at line in PR #9921

And mitchellh also made some comment for concerns about matching trailing space with comment in PR
#9921 (comment)

This is just for pi user. Normal terminal path output doesn't have this problem, it is just result of pi's rendering behavior.
But IMO adding trailing_space is little bit too much.

I researched problem with gpt-5.6 terra high
and made a patch with gpt-5.6 terra high
and compiled on OSX with gpt-5.6 terra high
and tested manually.

through this pi session, https://pi.dev/session/#002bdfbebe85ecdddd5c51481cd9d1b3

below is patch, I will raise a PR if this is vouched.

diff --git a/src/config/url.zig b/src/config/url.zig
index 2621898e1..463ea9bfc 100644
--- a/src/config/url.zig
+++ b/src/config/url.zig
@@ -52,10 +52,6 @@ const no_trailing_colon =
     \\(?<!:)
 ;
 
-const trailing_spaces_at_eol =
-    \\(?: +(?= *$))?
-;
-
 const dotted_path_lookahead =
     \\(?=[\w\-.~:\/?#@!$&*+;=%]*\.)
 ;
@@ -92,13 +88,11 @@ const rooted_or_relative_path_branch =
     path_chars ++ "+" ++
     dotted_path_space_segments ++
     no_trailing_colon ++
-    trailing_spaces_at_eol ++
     "|" ++
     non_dotted_path_lookahead ++
     path_chars ++ "+" ++
     any_path_space_segments ++
     no_trailing_colon ++
-    trailing_spaces_at_eol ++
     ")";
 
 // Branch 3: Bare relative paths such as src/config/url.zig.
@@ -110,8 +104,7 @@ const bare_relative_path_branch =
     dotted_path_lookahead ++
     bare_relative_path_prefix ++
     path_chars ++ "+" ++
-    no_trailing_colon ++
-    trailing_spaces_at_eol;
+    no_trailing_colon;
 
 pub const regex =
     scheme_url_branch ++
@@ -282,7 +275,7 @@ test "url regex" {
         },
         .{
             .input = "../example.py ",
-            .expect = "../example.py ",
+            .expect = "../example.py",
         },
         .{
             .input = "first time ../example.py contributor ",
@@ -341,11 +334,12 @@ test "url regex" {
             .input = "IPv6 in markdown [link](http://[2001:db8::1]/docs)",
             .expect = "http://[2001:db8::1]/docs",
         },
-        // File paths with spaces
+        // Trailing whitespace isn't part of a detected file path.
         .{
             .input = "./spaces-end.   ",
-            .expect = "./spaces-end.   ",
+            .expect = "./spaces-end.",
         },
+        // File paths with internal spaces
         .{
             .input = "./space middle",
             .expect = "./space middle",

Why do you want to make this change?

I want to refine user experience for 'pi tui'

I acknowledge that:

• I have read the Contributing Guide and understand the contribution process.
• I have read and agree to follow the AI Usage Policy.
• I wrote this vouch request myself, in my own voice, without AI generating it.

[tristan957]

!vouch