From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Sebastian Urban Newsgroups: gmane.emacs.bugs Subject: bug#36454: 26.2.90; feature request - Insert char by hex tab completion or C-x 8 RET ffe Date: Mon, 15 Jul 2019 10:34:22 +0200 Message-ID: References: <87r27016xo.fsf@mouse.gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="131214"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 Cc: 36454@debbugs.gnu.org To: Lars Ingebrigtsen , VanL Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jul 15 10:35:08 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hmwRv-000Xyu-It for geb-bug-gnu-emacs@m.gmane.org; Mon, 15 Jul 2019 10:35:07 +0200 Original-Received: from localhost ([::1]:35914 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hmwRu-0006Lb-1c for geb-bug-gnu-emacs@m.gmane.org; Mon, 15 Jul 2019 04:35:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38957) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hmwRr-0006LV-Ht for bug-gnu-emacs@gnu.org; Mon, 15 Jul 2019 04:35:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hmwRq-0005CB-JR for bug-gnu-emacs@gnu.org; Mon, 15 Jul 2019 04:35:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37483) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hmwRq-0005C0-E0 for bug-gnu-emacs@gnu.org; Mon, 15 Jul 2019 04:35:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hmwRq-0000aE-9L for bug-gnu-emacs@gnu.org; Mon, 15 Jul 2019 04:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Sebastian Urban Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 15 Jul 2019 08:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36454 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 36454-submit@debbugs.gnu.org id=B36454.15631796722200 (code B ref 36454); Mon, 15 Jul 2019 08:35:02 +0000 Original-Received: (at 36454) by debbugs.gnu.org; 15 Jul 2019 08:34:32 +0000 Original-Received: from localhost ([127.0.0.1]:46304 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hmwRL-0000ZQ-VQ for submit@debbugs.gnu.org; Mon, 15 Jul 2019 04:34:32 -0400 Original-Received: from mail-lf1-f48.google.com ([209.85.167.48]:43862) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hmwRJ-0000Z9-SD for 36454@debbugs.gnu.org; Mon, 15 Jul 2019 04:34:30 -0400 Original-Received: by mail-lf1-f48.google.com with SMTP id c19so10393283lfm.10 for <36454@debbugs.gnu.org>; Mon, 15 Jul 2019 01:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UHVAvjVfIj/6BaPHUqebNjmxoeKMBrJk9r/Mz/RS4Ps=; b=W2QMqLLwvxU16GzyF08FJt1UfV7pApL4YjiF8Bu3o5wkQLrphh2gIINrFeMVBE7rEq 8fxHV27RILeKAXIB5cr+ZVNW8nxgiTVfCENSDvCDKcPXLxkLsZTMt8IcUge2GG41XRXU 6bSxxV9tcc5n1YP8QncMvPynC9DIce9zRPp1B9AMWzVQ2YaauikfZHvQeppCSfMOn8xL GtoTrPo/Hl8FikFju/2pc0qG6hJ/7NBhM6DT8UChnjfy65rhlxj+KTpiD/d9giXwWhfR DG4fzFHp7JTCvPvYPp9qJEV0pDYsDkk/TpCL+CNtPY1FbqUFljWv7QlssVpiJ7cgpk/Y 4ohw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UHVAvjVfIj/6BaPHUqebNjmxoeKMBrJk9r/Mz/RS4Ps=; b=UT4ENF/mMaqfOQJoBOHeMfTTJg4a/H6nfF9cr4IIEQH2c0BU7tr3paA1MDi7SUUWHg NLqZqKzqeW4+sOzN9fAuRtIFE56YkbpBbNjxoxL2RS2mVHcEWhk4PengDMHufYM8gXtG qBUMRDJuTo5ZhuMaHoLhfkRqyvJi3IABbXT29SWH8r9dmqEyaKPVYWq+TaoTh5nGeGEJ J4Bdve1IWTZAm/VlMi36HcdyPG9ZRZcCz6vZIgsEodupJpq12WFzJydalJIqvYAljkYk FKOAqq7pR5hGbg3lLpqRzaAMQWjIoY/0iPhMTEr9D2fnGqrxCNehwC+1EiLWAXHJDaLa vjYA== X-Gm-Message-State: APjAAAVHUoFHe0/l1X5LLo9W4DqiDxP6IUdXLjhQ8Y9gPDBu1QZKILUO XV4OFKjZle5oHIucMOvuZVC9D11P X-Google-Smtp-Source: APXvYqw/zuMkg3bcD24n42+4JYTder3q/HSQROds1xKsuiahnFvSQUeAHIxaJMy5f9Cb0mUE1+Cc/Q== X-Received: by 2002:a19:641a:: with SMTP id y26mr10526312lfb.29.1563179663559; Mon, 15 Jul 2019 01:34:23 -0700 (PDT) Original-Received: from [89.161.9.216] (ip-89-161-9-216.tel.tkb.net.pl. [89.161.9.216]) by smtp.gmail.com with ESMTPSA id m25sm2256258lfp.97.2019.07.15.01.34.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Jul 2019 01:34:23 -0700 (PDT) In-Reply-To: <87r27016xo.fsf@mouse.gnus.org> Content-Language: en-GB X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:163066 Archived-At: Not that I disagree, but I have this idea. There are 3 ways of specifying character for 'C-x 8 RET': 1. Unicode name, 2. hex code, 3. code with radix specified, e.g. #o... (octal), #x... (hex), #10r...(decimal). While it'll be difficult(?) to have both completions for name and hex code (point 1. and 2.), because for example some names include numbers, completions based on the code for 3rd method of inserting char could be added. This way if someone type letters or numbers - method 1. or 2. - he'll get completions based on Unicode name. BUT if he define radix in the beginning (#b/#o/#x/#RADIXr), possible completions based on the code will appear. A bit more typing (defining radix) but it could work. This way we could also get completions for other codes than hex. > I don't think this sounds very useful, because the hex values are > kinda tightly packed, so you get too many matches. With approach described above, it'll only happen with 3rd method - probably not the most popular. Also I think if someone will try to complete it, he'll do it after typing at least 2 or as OP - 3 letters. > And they get in the way of name completion. With approach described above, this problem doesn't exist.