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 1tIiA1-00G2pP-H4 for pgadmin-support@arkaria.postgresql.org; Wed, 04 Dec 2024 05:42:53 +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 1tIi9y-00FCYl-0Z for pgadmin-support@arkaria.postgresql.org; Wed, 04 Dec 2024 05:42:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tIi9x-00FCYc-PI for pgadmin-support@lists.postgresql.org; Wed, 04 Dec 2024 05:42:50 +0000 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIi9s-000xC8-Ee for pgadmin-support@postgresql.org; Wed, 04 Dec 2024 05:42:49 +0000 Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5d0c098c870so917428a12.1 for ; Tue, 03 Dec 2024 21:42:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733290963; x=1733895763; darn=postgresql.org; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YC/YIZn3L3CVnquE7yO37vNr1oO2vrJa5FNI97FPxrA=; b=m8J78nO5aU+wD6DQyMMFlCrs+u6GUFIetePAw3ogGvwCBkzcWrJ34I7VS+DgrMsMZL 0PNj+q93EiR6OYNFMAWMEFcG+hHuqTow5kpLfXt9Qp27pF0IPMOYCMaPzIHdF4gNzJSf MQwXg/sPhyv9PK2hZ3uBFuoOm9WeSwj5xadG1BwuFvwoc6jib1GYBznozMz7RT4G4RT0 fonZlOPJ5cH2OferD0zYACWNCNf4s7S5fMJYL7SRzPmVfe1k7Vzcp123lNCkoZb/PKV+ 8bD4ilbE7SaphbqK8tBuznKSyfLeDsGY5sUB+S9OWoD08/irWpGUOMGhmCno1n3RVi/J DD3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733290963; x=1733895763; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YC/YIZn3L3CVnquE7yO37vNr1oO2vrJa5FNI97FPxrA=; b=aBj/p+aPu4CB0S+L8ec9dL5QfrAFgG1jzi6+3BSzByH1GEhYxOH7l818qTc+uoq4ZR ZmehJsGFbR7cFikjOWYQpkeijIGHYHGRO+R+lj8B6Dwld0vKyJJLkqGvZkhGGZFvRJnH C3zYvJRVppff+RZ7Vwn/FbowQh/dZYjTY/udJF/cJqRY60mAx571GJ9lAQ9iku0iYkD7 C0EIMvd/b9kofQGUqUZQprwJgjeXn9ySg1tLSmIjTSKX6x5bJ2IgXYfNe60C4++doMJW M9Z5WIdv7i9nXt2plaBTjv9cbL9mF8v3k+5yZUbp6S2eyzIZXqPuJWGJ1G6wS4SAgd2j UrEg== X-Gm-Message-State: AOJu0YwwRW/JWZkRSVYB/zCgAnP0E2q04qdoCCbC3P1eYc1surKubtNw hzXbIg6ASUKUSjgowWE1X6rsRxmEbK9BpB78LiklV9me9XTJfrEU5gUy1CDpwTI6dBahVvzvLBf ZoUprJpHKIzAfRPqWASwQTzn2NN7qjw== X-Gm-Gg: ASbGnctShH+6v6nU8GjycCbXZQnwk+hOyg9qGu4JMoEYD7t5VXnc4sfklZf2yCPC+nn hOBrXFwbc8tIrQKxFnpCsCcEnJ1YCmsNT X-Google-Smtp-Source: AGHT+IHstw+z7MrtLOsEWUSrblzc/nJJR57bBdtfFrWQEQGh6qrumRXS2SeNGE6cxBO46/VAXJ7iWA5gABzh7qPkwA4= X-Received: by 2002:a05:6402:350e:b0:5d0:fc12:79e3 with SMTP id 4fb4d7f45d1cf-5d0fc127d4amr10104652a12.15.1733290962670; Tue, 03 Dec 2024 21:42:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Reply-To: calle.hedberg@gmail.com From: Calle Hedberg Date: Wed, 4 Dec 2024 06:42:32 +0100 Message-ID: Subject: Re: Version 8.13 now encapsulates any copy and paste value in double quotes - how to remove that? To: Aditya Toshniwal Cc: pgAdmin Support Content-Type: multipart/alternative; boundary="0000000000001f5b8f06286b4014" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001f5b8f06286b4014 Content-Type: text/plain; charset="UTF-8" Pablo, Changing that setting has no impact on this issue - as confirmed by Aditya, it is actually a bug. But when reading the bug report, I see there IS a workaround, of sorts: You can use CTRL-X (cut) instead of CTRL-C (copy), the paste it back to the original position before pasting it into the new position. Messy, but maybe a little bit quicker than using CTRL-C and then delete the double quotes etc. I any case, I hope this regression bug will be fixed asap. Aditya, thank you very much for clarifying that the issue has been reported and accepted as a bug. Best regards Calle --0000000000001f5b8f06286b4014 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Pablo,

Changing that s= etting has no impact on this issue - as confirmed by Aditya, it is actually= a bug.

But when reading the bug report, I see the= re IS a workaround, of sorts: You can use CTRL-X (cut) instead of CTRL-C (c= opy), the paste it back to the original position before pasting it into the= new position. Messy, but maybe a little bit quicker than using CTRL-C and = then delete the double quotes etc.

I any case, I h= ope this regression bug will=C2=A0be fixed asap.

A= ditya, thank you very much for clarifying that the issue has been reported = and accepted as a bug.

Best regards
Call= e

--0000000000001f5b8f06286b4014--