From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: tomas@tuxteam.de Newsgroups: gmane.emacs.devel Subject: Re: xterm [menu] key definition Date: Tue, 24 Aug 2021 13:00:14 +0200 Message-ID: <20210824110014.GA28734@tuxteam.de> References: <20210819024728.kgnf6jmpakqdto4p.ref@Ergus> <20210819024728.kgnf6jmpakqdto4p@Ergus> <87mtp71i4s.fsf@mail.linkov.net> <20210824081906.lg2qt4z2snhaxnjv@Ergus> <20210824083433.GC17209@tuxteam.de> <20210824091741.heeyge3xhufujkd7@Ergus> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33701"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: emacs-devel@gnu.org To: Ergus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 24 13:01:02 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mIUAv-0008VX-QL for ged-emacs-devel@m.gmane-mx.org; Tue, 24 Aug 2021 13:01:01 +0200 Original-Received: from localhost ([::1]:46432 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mIUAu-0006MF-Dk for ged-emacs-devel@m.gmane-mx.org; Tue, 24 Aug 2021 07:01:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34946) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mIUAH-0005aY-41 for emacs-devel@gnu.org; Tue, 24 Aug 2021 07:00:21 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:37485) by eggs.gnu.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.90_1) (envelope-from ) id 1mIUAC-0002Pz-Lv for emacs-devel@gnu.org; Tue, 24 Aug 2021 07:00:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=OLJha6gCJnkDI77J0CdfAYgXXvVlYxvZIrbT4QcqxSc=; b=N5l4YZasA27k2aRrZehiobzb++12ZV31yfF62/oRzFeCr/b3gxI7tfVBVZgwnGwv6xcXXrmwxsDfK6tJk/k91PUDN1fvjbGNdgt4GC5KDQp4TgX7NNFdeGfiiAaZua+hPh49JJmVxMCmSdbsylrCzsELeEZmvzAJycIUkQy9YMQmkjLXlmPd65wT5l1i5kaCNbA42empyANGw/MTfMYQJ+AAQaA3O7wAgkIdOwUtPgYyCVqXZf1aablxAfiF6hOOesL/Gq0Gc5bIt8LlDAsHyOzAuOqLktCOFJQgbVY48tekWYTxffQf7cl/coqUFYfjMGo+oPM3k1EGlD0zUQsaHw==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1mIUAA-0007ow-89; Tue, 24 Aug 2021 13:00:14 +0200 Content-Disposition: inline In-Reply-To: <20210824091741.heeyge3xhufujkd7@Ergus> Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:272904 Archived-At: --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Tue, Aug 24, 2021 at 11:17:41AM +0200, Ergus wrote: [...] > Then if you have it, could you tell what escape sequence it sends throw > Xterm by default? If you could do the same with urxvt will be very nice > ;) Sure :) I tried both. My methodology is to run 'cat | hexdump -C' in each of xterm and urxvt and to terminate input with CTRL-D. I tested the methodology itself by trying some keys where I more or less knew what to expect ("a", , but also ). The result is... nothing. This may sound disappointing, but then, xterm tries to pretend being a VT220, and those had no "print" key. OTOH, it would be subestimating the folks at MIT Project Athena to assume that would not be configurable. Hard-coding this wouldn't have made sense to them. So yes, for xterm at least (but I think for urxvt, too), you can configure that with X Resources. This one [1] looks as if there were hope as long as there is a keysym. No time to try it out at the moment, though. Whether the application (Emacs) running "in" the xterm can change that dynamically (or has to tell the user to do that for it ;) is the next interesting question :-) Cheers [1] http://www.fifi.org/doc/xterm/xterm.faq.html#how2_fkeys which is, BTW, a wonderful resource in things xterm. - t --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAmEk0T4ACgkQBcgs9XrR2katogCcCtcJQculhmNdBiaaRoEO6zKb RNgAn1VemR2QW+FLdnXIxsaq4oQXj8XW =VgsB -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf--