From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: npostavs@users.sourceforge.net Newsgroups: gmane.emacs.bugs Subject: bug#16828: 24.3.50; eval-expression, character representation of integer results time-consuming Date: Sun, 26 Mar 2017 10:55:44 -0400 Message-ID: <87inmw3x5b.fsf@users.sourceforge.net> References: <83mwhk4v48.fsf@gnu.org> <83txbr2sye.fsf@gnu.org> <87zjljf086.fsf@rosalinde.fritz.box> <83a9di3lt1.fsf@gnu.org> <877g8mb3lh.fsf@Rainer.invalid> <530DBEEE.8060805@gmx.at> <87zig84s6l.fsf@users.sourceforge.net> <83wpbc9ldc.fsf@gnu.org> <83lgrs9k8p.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1490540128 1242 195.159.176.226 (26 Mar 2017 14:55:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 26 Mar 2017 14:55:28 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) Cc: 16828@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Mar 26 16:55:24 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cs9Zb-0006e7-QJ for geb-bug-gnu-emacs@m.gmane.org; Sun, 26 Mar 2017 16:55:15 +0200 Original-Received: from localhost ([::1]:41262 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cs9ZZ-0002l2-Dc for geb-bug-gnu-emacs@m.gmane.org; Sun, 26 Mar 2017 10:55:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cs9ZS-0002j6-7z for bug-gnu-emacs@gnu.org; Sun, 26 Mar 2017 10:55:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cs9ZO-00023V-UO for bug-gnu-emacs@gnu.org; Sun, 26 Mar 2017 10:55:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:47853) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cs9ZO-00023P-Qe for bug-gnu-emacs@gnu.org; Sun, 26 Mar 2017 10:55:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cs9ZO-0007uJ-1k for bug-gnu-emacs@gnu.org; Sun, 26 Mar 2017 10:55:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: npostavs@users.sourceforge.net Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 26 Mar 2017 14:55:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16828 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 16828-submit@debbugs.gnu.org id=B16828.149054007130304 (code B ref 16828); Sun, 26 Mar 2017 14:55:01 +0000 Original-Received: (at 16828) by debbugs.gnu.org; 26 Mar 2017 14:54:31 +0000 Original-Received: from localhost ([127.0.0.1]:46051 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cs9Yt-0007sh-IS for submit@debbugs.gnu.org; Sun, 26 Mar 2017 10:54:31 -0400 Original-Received: from mail-it0-f46.google.com ([209.85.214.46]:37784) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cs9Yr-0007sO-Sd for 16828@debbugs.gnu.org; Sun, 26 Mar 2017 10:54:30 -0400 Original-Received: by mail-it0-f46.google.com with SMTP id 190so29761866itm.0 for <16828@debbugs.gnu.org>; Sun, 26 Mar 2017 07:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=XKu7CGuTfNGoeaO3hyOAiIptpUxdn/x/SAofDtpMs4g=; b=s/SQ6CIfAoWUQ+sajZqUfrNVeiFYwBZHy8c9Wywa4fITLuDUsvblPXNtB7zqfsFrbx oR+MPTYLS30Mjiww5MP0BCuUXNgGPM5K0IAHfkQ5eIvZOZQ/pXMRkqDyy1VhH1CNVomg NTinlLTskTckBgWNwENcICpO07ETJMssLD8X4dRgoSoR0RTey8w8s1NKKnnGQkMQzM7w 5fMHdDzHMPL2bEGGG9b0yhf7AuwcFWCG+SE+ev+eZZoFv90HqmZwd4WgwMHYW0/QCELj NelrUt70y6Npv4Gxsn8KkObZlJhbSZ6rXzJP9dqcWtT54CNEb6FLJBEzY4qwbb8/p16F yEMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=XKu7CGuTfNGoeaO3hyOAiIptpUxdn/x/SAofDtpMs4g=; b=dAA20Wi57PcCqRNj9oumH4/TgZ2IYHfEbXy3LICRDYAITQnj50YvvyC0MOn3yn7dwQ L/inftX2so0yvuaxBWS3rDNAG2f4d5n/F3Y4Qv6/I6EBYIy6+RrMdGvLmuC3anAdV22d LnHnuu5+h5SutKKvFFvBXCLBERTUpOZVror2zU0W1usW/PEj4GW1708ToBb/++90GdpY kHpCr/CVU4iOnPyP8CChl9CbdaVvv/93S/s2QR2dHrlmv1c1q/TAuMvGElGBiGI7IPRv Dpirlkq1BHDg7GqmAbmqtoOl0BwK8tQKapLLHTDINs/20Rn0fNywbV+53u0pJOATtBrG OQMA== X-Gm-Message-State: AFeK/H3mkhmMhr3f/9jq86sR0gO5MGxfU/5s1PJdT5QqlbtRzGD0VB54IEH7HpKG/Z2PRg== X-Received: by 10.107.20.86 with SMTP id 83mr16849724iou.94.1490540064223; Sun, 26 Mar 2017 07:54:24 -0700 (PDT) Original-Received: from zony ([45.2.7.65]) by smtp.googlemail.com with ESMTPSA id e134sm3984069itc.23.2017.03.26.07.54.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 26 Mar 2017 07:54:23 -0700 (PDT) In-Reply-To: <83lgrs9k8p.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 Mar 2017 17:37:58 +0300") 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: 208.118.235.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:130976 Archived-At: Eli Zaretskii writes: >> > >> > So, under this proposal, is there any way to get the character for a >> > single invocation of M-:, without setting the option, if I only need >> > that sometimes? Should there be such a way? >> >> Isn't M-: (prin1-char value) sufficient? > > No, not after years of using "M-: #xNNNN RET". If you want to keep muscle memory, (setq eval-expression-print-maximum-character most-positive-fixnum) should give you back the old behaviour. If you only want this only some of the time, perhaps we should add a toggle-print-maximum-character command?