Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v5n18-00BylK-Jh for pgadmin-support@arkaria.postgresql.org; Mon, 06 Oct 2025 15:20:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v5n16-008tQP-An for pgadmin-support@arkaria.postgresql.org; Mon, 06 Oct 2025 15:20:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v4cw9-00CYzl-SZ for pgadmin-support@lists.postgresql.org; Fri, 03 Oct 2025 10:22:54 +0000 Received: from mail-vk1-xa36.google.com ([2607:f8b0:4864:20::a36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v4cw7-000BIW-2A for pgadmin-support@lists.postgresql.org; Fri, 03 Oct 2025 10:22:53 +0000 Received: by mail-vk1-xa36.google.com with SMTP id 71dfb90a1353d-54aa789f9b5so1511566e0c.1 for ; Fri, 03 Oct 2025 03:22:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1759486969; x=1760091769; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JYtVE+rsa+pWphIBSsr92F827j4pkHuiiaCMdTxROTI=; b=g/6fuM5t+Ka51gDNaJ8mHGaUqJ43hmBj3pa6hKYVYG9tZHD1FGqvxa9cB8iaO9ve9Q P7AfUzBO03iEnW2PjnvhNDIHjZBqf8ZyXtqyo4CivSEKPhGdIgTyX6gnwL+s6TnPy1bX HxQvnQo47SKMI83A9pvurNORNSRQEYRiO3I0TwPea8IfW97rcXxadGoza262AbyzbtSa f77KcU3S1FXZmuQIy/ykiGIvGhXKA7B5gUKML7OQB0CW/NEBUPMBAk6j5GnTW2NCgg9o Z/kLhPfrCRarF+TLNZxJ0ijiGCchmhZmM084wp/a4cY9f3xPlWcI1O/681nlZMt+n5Uy b2iw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759486969; x=1760091769; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JYtVE+rsa+pWphIBSsr92F827j4pkHuiiaCMdTxROTI=; b=AjjiB+xTW2M/6H93Fs4HUEUky4uViwC92aLPaB87dA7Hf2iZY7CUj9ra+E6vBAtez3 adO3roNyEYh2T0QPWkO14eGKKm522E/8COZcaFeXdxEydBCQTEW01j28X2hPtL/98hdx XTQNjMJzk2uoIE8ie3IdI029NH/HdaWUKbxi99ltycPkg8OlK04LZnzkbtNt4/vP5glF lXvgjOcp4uNBAv3+rtiyqzwTgyABd/yr5PP0Y/7JF/qkdx1z5M61y2KPx5fFBejut4cO EVX6OStRidU6+HqhsbhofbzEewGHPePVS6gR1NRdcL5ALGCHKfhq2NZx+h4Ki8PkDdRU QpJQ== X-Gm-Message-State: AOJu0Yy4a/eo66oOqJArt1P1w8DKn80VRD3mqC4V3xrBGBbzIuh8yycg kYbwTMhPRYV1TJg6v4W6MfohgRd4SdISGFO6KeaddmpFAXzv+e+OgvZfqPOTWkKJZnpGf1MIa+T pvkJAwtU8eSOT4DDYv7VFZV4gtDOT9fI3z+hgG/IGsXXBuStlmwyCHA== X-Gm-Gg: ASbGnctbQR8/73rQ6G8UYOKUHE27N/bxdeCKG9f12CGkvMTbO+41Tv6A/i5CJ29W/mh daWGK2Y11/w5YqRtOloutCGmlNLTyLpkTSiIt7qr/rMLUUGRJS6bRDWTfDic8nU+YP7E0QEQj82 wjaKmJtwYbc5mR98+Y3micxNvkV0bxghYWxVynCu+T4NPVGjJlWefgp1yFQZ4S9YI+7rga1M+/M 42zCQ6KFR+wkxKGFwa/Gmlz1XuwniTA6UojXTln5ZhDqlZTRBjc+wjQGybhv8xB X-Google-Smtp-Source: AGHT+IGzYUyCNF03ilkfDUyK2YuCFjio2FrRTxhCj5ZciS+CV10m8G32EtVeO6HyOTTDL31Uh+96lNrSJc9dS2DGrw0= X-Received: by 2002:a05:6122:8c21:b0:54a:87d3:2f0c with SMTP id 71dfb90a1353d-5524e9213e6mr831027e0c.8.1759486968925; Fri, 03 Oct 2025 03:22:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Fri, 3 Oct 2025 15:52:12 +0530 X-Gm-Features: AS18NWCOADmraKszsOsm5xcMTXn8U_TA-e_rp_mAD9_umHTYbrIaizw6SRkBeSc Message-ID: Subject: Re: Assistance Required: Code Folding and Line Numbers Not Appearing in pgAdmin 4 (v9.8) To: Mas Kinato Cc: pgadmin-support@lists.postgresql.org, security@pgadmin.org, pgadmin-hackers@postgresql.org, webmaster@pgadmin.org Content-Type: multipart/alternative; boundary="000000000000c5245906403e7bc7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c5245906403e7bc7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Mas, Please check - https://github.com/pgadmin-org/pgadmin4/issues/9160 On Thu, Oct 2, 2025 at 1:38=E2=80=AFAM 'Mas Kinato' via pgAdmin Security < security@pgadmin.org> wrote: > Dear pgAdmin Support Team, > > I am reaching out regarding an issue we are encountering with code foldin= g > in pgAdmin 4 (version 9.8). > > Issue Summary: > =E2=80=A2 Code folding is enabled under Preferences =E2=86=92 Query Tool = =E2=86=92 Editor (the > =E2=80=9CCode folding=E2=80=9D option is toggled on). > =E2=80=A2 However, fold carets/triangles are not appearing for foldable r= egions > (e.g., WITH (=E2=80=A6) CTEs or VALUES (=E2=80=A6) blocks). > =E2=80=A2 We only see the caret when wrapping a block in BEGIN=E2=80=A6EN= D;, but that > makes the query invalid in SQL execution. > =E2=80=A2 Additionally, the =E2=80=9CLine numbers=E2=80=9D option (expect= ed under Preferences =E2=86=92 > Query Tool =E2=86=92 Display) is missing entirely in this version of pgAd= min 4, > which prevents us from exposing the gutter where fold carets normally > appear. > > Steps Taken So Far: > > 1. Verified that Code folding is enabled. > 2. Tried different themes (Default, Light, Dark) to check if the caret > was hidden due to UI visibility. > 3. Restarted Query Tool after preferences changes. > 4. Tested simple foldable examples (e.g., WITH test AS (VALUES (1), > (2), (3)) SELECT * FROM test;) =E2=80=94 no fold caret appeared. > 5. Confirmed with multiple users that the Line numbers preference is > not visible in our pgAdmin 4 v9.8 builds. > > Environment: > =E2=80=A2 pgAdmin 4 v9.8 > =E2=80=A2 Affected across multiple installations > =E2=80=A2 OS: [insert OS details if you want to include, e.g., Windows 11= / macOS > Sonoma] > > Request: > Could you please confirm: > > 1. Whether the Line numbers option has been relocated or removed in > pgAdmin 4 v9.8? > 2. If this is a known regression/bug affecting code folding in CTEs > and parentheses blocks. > 3. Recommended steps or patches to restore proper code folding > (without relying on BEGIN=E2=80=A6END;). > > We rely on folding for large SQL queries, and currently this limitation > makes navigation difficult. If this requires escalation, I=E2=80=99d be g= rateful if > you could provide guidance or log it as a support issue with the pgAdmin > development team. > > Thank you for your assistance. > > Best regards, > Mas > --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Staff SDE II | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --000000000000c5245906403e7bc7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Mas,

Please=C2=A0check -=C2=A0https://github.com/pgadmin-org/= pgadmin4/issues/9160


On Thu, Oct 2, 202= 5 at 1:38=E2=80=AFAM 'Mas Kinato' via pgAdmin Security <security@pgadmin.org> wrote:
Dear pgAdmin Support Team,<= br aria-hidden=3D"true" style=3D"box-sizing:inherit">
I am reaching out regarding an issue we are= encountering with code folding in pgAdmin 4 (version 9.8).

Issue Summary:
=E2=80=A2 Code folding is enabled under Preferences = =E2=86=92 Query Tool =E2=86=92 Editor (the =E2=80=9CCode folding=E2=80=9D o= ption is toggled on).
= =E2=80=A2 However, fold carets/triangles are not appearing for fo= ldable regions (e.g., WITH (=E2=80=A6) CTEs or VALUES (=E2=80=A6) blocks).<= br aria-hidden=3D"true" style=3D"box-sizing:inherit"> =E2=80=A2 We= only see the caret when wrapping a block in BEGIN=E2=80=A6END;, but that m= akes the query invalid in SQL execution.
=E2=80=A2 Additionally, the =E2=80=9CLine numb= ers=E2=80=9D option (expected under Preferences =E2=86=92 Query Tool =E2=86= =92 Display) is missing entirely in this version of pgAdmin 4, which preven= ts us from exposing the gutter where fold carets normally appear.

Steps Taken So Far:
  1. Verified that Code folding is enabled.
  2. Tried different themes (Defa= ult, Light, Dark) to check if the caret was hidden due to UI visibility.
  3. = Restarted Query Tool after preferences changes.
  4. Tested simple foldable ex= amples (e.g., WITH test AS (VALUES (1), (2), (3)) SELECT * FROM test;) =E2= =80=94 no fold caret appeared.
  5. Confirmed with multiple users that the Lin= e numbers preference is not visible in our pgAdmin 4 v9.8 builds.
=
Environment: =E2=80=A2 pgA= dmin 4 v9.8
=E2=80=A2 Affected across multiple installations
=E2= =80=A2 OS: [insert OS details if = you want to include, e.g., Windows 11 / macOS Sonoma]

Request:
Co= uld you please confirm:
  1. Whether the Line= numbers option has been relocated or removed in pgAdmin 4 v9.8?
  2. If this = is a known regression/bug affecting code folding in CTEs and parentheses bl= ocks.
  3. Recommended steps or patches to restore proper code folding (withou= t relying on BEGIN=E2=80=A6END;).
We rely on folding for large SQL queries, and = currently this limitation makes navigation difficult. If this requires esca= lation, I=E2=80=99d be grateful if you could provide guidance or log it as = a support issue with the pgAdmin development team.

Thank you for your assistance.

Best= regards,
Mas


--
Thanks,
Aditya Toshniw= al
pgAdmin Hacker=C2=A0| Sr. Staff SDE II=C2= =A0| enterprisedb.com
"Don't Complain about Heat, Plant a TREE"
--000000000000c5245906403e7bc7--