Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVSB-0003P2-Jr for pgsql-admin@arkaria.postgresql.org; Tue, 29 Jan 2019 15:37:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1goVSA-0000K9-7t for pgsql-admin@arkaria.postgresql.org; Tue, 29 Jan 2019 15:37:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVS9-0000K2-SF for pgsql-admin@lists.postgresql.org; Tue, 29 Jan 2019 15:37:34 +0000 Received: from mail-io1-xd31.google.com ([2607:f8b0:4864:20::d31]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVS6-0007DL-9U for pgsql-admin@lists.postgresql.org; Tue, 29 Jan 2019 15:37:33 +0000 Received: by mail-io1-xd31.google.com with SMTP id l14so16626014ioj.5 for ; Tue, 29 Jan 2019 07:37:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtssigns-com.20150623.gappssmtp.com; s=20150623; h=reply-to:from:mime-version:thread-index:date:message-id:subject:to; bh=87ZwHDB3N7XZZbSz1yKyTUJj4DHAlWIIdfeMovomV+s=; b=t6gZ3Kq/ZcYVLGue9AADoF66S+Ms5Jr8HLRpVtbsbhqiLCuUDkehzey/wL0m2z9TDD cJeLTQZOm09oJW5UzAzkYn9m/13bOQAzR7X0ncMmDZgsZFdauoDCwfds9YHhIEvFN/q7 TFgGTDmvbUeWSuNCIUNb0YUMmAUu2Lay8PXXZtzAQ0nZloC76FPmLFWA1WZqNh+6RJ+1 Gq7Xc8pREyjLhUOII/rdUw3xNCkrWFtR8WZ69DTiYhJb/+vebWTY9MaDZW+Py+24yr35 Z0lAcL5gnzWlkpWLMSR+R/9ajXO5wX4PqCpYyaptG6Vxx+fkUnDNJoqSZn8QoEiMvTrb 9Psw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:from:mime-version:thread-index:date :message-id:subject:to; bh=87ZwHDB3N7XZZbSz1yKyTUJj4DHAlWIIdfeMovomV+s=; b=qrd99ZIIs+/yKVb4orKx+VFeL6TTVAGtjk1bLi5m6EE4aWiG2DIQt6Hp8tRCSECZXt Vbd/Ji7X8px46KcF5/u4IJIaVo6nWbK5T/VeykvyFtY8stqOIz0bBAXJN/eBODhlxyqj uiVbzZ9v3o4NrtJiiOI1+r1gBEfQO52lr+m8RU4gKJb2aGhyHVoFIXEXnF+pBrZwOjWK q9u2WhaAZI3RT4YEv8a8MsT3csmSP/hbc2UrVUmTukiTZgYJ+daLtssE4rCY+yqOUeTJ mHPOFKDZGDFX4SCTpjefzDezauQhDfEKEOun5J5ACo/vIK9sziW19ba7X/uAetUgIMva +veQ== X-Gm-Message-State: AHQUAuZtiX9fwJvvokV/kQobyy0O6FWkpxtoTltAv6Eb4wwHbXAxMMSf x9g0UsmdrH2ENRJu+m1JmIGCyZY5jpBNg4d8UYXVe2ZI X-Google-Smtp-Source: AHgI3IZ7lT+I4oQV6a8eLCtfSQFSw+MTv7o7sowbLp+2+374F7Ma0OOn7wzsCib8rQv3+G3ui4EeKCmPatpS32eFKvI= X-Received: by 2002:a6b:f90c:: with SMTP id j12mr641061iog.245.1548776248164; Tue, 29 Jan 2019 07:37:28 -0800 (PST) Reply-To: From: Mike Moening MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdS36IgmVIncF2/yQmSME9uP+GDBnw== Date: Tue, 29 Jan 2019 09:37:24 -0600 Message-ID: Subject: Ctrl-C to copy rows? To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000001bdf1e05809a926b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000001bdf1e05809a926b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Is it possible to configure pgAdmin4 so that I can use Ctrl-C to copy rows and Ctrl-V to paste them using the DataOutput pane via keyboard? The preferences for keyboard says: =E2=80=9Caccess key=E2=80=9D but I have = no idea what that is or how I can change it. Thanks, Mike --0000000000001bdf1e05809a926b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Is it possible to configure p= gAdmin4 so that I can use Ctrl-C to copy rows and Ctrl-V to paste them usin= g the DataOutput pane via keyboard?

The preferenc= es for keyboard says: =E2=80=9Caccess key=E2=80=9D but I have no idea what = that is or how I can change it.

=C2=A0

Thanks,

Mike

--0000000000001bdf1e05809a926b--