From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Should minibuffer prompt be made intangible by default? (Was debbugs 21874: 25.0.50; point-entered no longer works) Date: Wed, 30 Mar 2016 12:46:39 -0400 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b2e41c024a4cd052f46e67b X-Trace: ger.gmane.org 1459356452 20567 80.91.229.3 (30 Mar 2016 16:47:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Mar 2016 16:47:32 +0000 (UTC) Cc: Stefan Monnier , Emacs developers To: David Reitter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 30 18:47:28 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1alJHD-0003Cz-LH for ged-emacs-devel@m.gmane.org; Wed, 30 Mar 2016 18:47:27 +0200 Original-Received: from localhost ([::1]:55806 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alJHC-0005WL-CO for ged-emacs-devel@m.gmane.org; Wed, 30 Mar 2016 12:47:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37213) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alJH7-0005VX-VX for emacs-devel@gnu.org; Wed, 30 Mar 2016 12:47:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1alJH5-0005k0-Tz for emacs-devel@gnu.org; Wed, 30 Mar 2016 12:47:21 -0400 Original-Received: from mail-ob0-x22f.google.com ([2607:f8b0:4003:c01::22f]:36484) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alJH5-0005ig-NQ for emacs-devel@gnu.org; Wed, 30 Mar 2016 12:47:19 -0400 Original-Received: by mail-ob0-x22f.google.com with SMTP id m7so2993609obh.3 for ; Wed, 30 Mar 2016 09:47:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=t2TtHnLo5wyO9Ijv0NiakFb1DcnV5yTH9mJZW0FmqFE=; b=vyEOsvr6e54NtRofekYtDXQmKWZQsIm8LlMUNMDfuXy+fmeUhrOdYjodV6JFVdBiDA Wmr7Y9U5aeL5UuhnkUzUafZ9AW8potYamLS2DqkD2vs/Sy73JgRrazk+dfDE6bSu4Puz rnS26XdbSCQ47imwXcj8qkkn6ne1CY8dqgJTbztresl/9fW/BAJuVoZASJQU0gKiL4ZA ynp5ePzMceGkDDSVnGoFFIcZQ9NB4Trko5DoDzT4dE0mgSt/+UYa/G4goz4dsYHYOEKN BWRuNK+3lOX/SFRxnzx7Zrg3ZpMV06IwHNi0BoFsXra9N5Tb8naCkascbef4WgC/wasg Ti3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=t2TtHnLo5wyO9Ijv0NiakFb1DcnV5yTH9mJZW0FmqFE=; b=lZSBAgXGBZG+q08NvaIgrVAOIMQ9l8+Gp19Kws1kK8GIEItcSnfDFf3ROVv6rx0FTM EW+PYiCHO6dSEmXYjQjU3/INFRF1MpaGCJo0jbJ79xmvdZ7J/EJfNItHekI/7MuYLqdH MGcIAI2iwTY8772XTSWN5ZmCeZGYqmgdcd2R/mTwfOHHQ3WtHllhc9mMCnthWg8UZng8 i80Dnh0LmUrF9+p5w4YcZAClzp7vo6BIrwOSZPQT8/s4GvD86cUqaUszjMciNyyrpdco HOtQAMwJIETkwIn9k4i9B7qxak5MRLXeFSsa6CSRjvRMDQ9VacfPwuoT99yfjgNR1bIs BUbA== X-Gm-Message-State: AD7BkJJb0JG4AfjMd6MvcyeES/tchh2TysHWg7IO0B8JrCk6u/X0gW5SzMW9BNHk6oOgjxAmdhGRdAt3A8QxqA== X-Received: by 10.182.97.164 with SMTP id eb4mr5601425obb.39.1459356438928; Wed, 30 Mar 2016 09:47:18 -0700 (PDT) Original-Received: by 10.202.204.2 with HTTP; Wed, 30 Mar 2016 09:46:39 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c01::22f X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:202463 Archived-At: --047d7b2e41c024a4cd052f46e67b Content-Type: text/plain; charset=UTF-8 Hi Stefan, I agree with what David has to say; I too believe that there are a lot more users expecting the minibuffer prompt to be intangible. For now, I need to add the below to my emacs config (as I don't set the customize variables using the GUI approach, and I would like to simply append stuff to whatever the default value is): (let (;; (get ..) -> ((quote (read-only t face minibuffer-prompt))) ;; (car (get ..)) -> (quote (read-only t face minibuffer-prompt)) ;; (cdr (car (get ..))) -> ((read-only t face minibuffer-prompt)) ;; (car (cdr (car (get ..)))) -> (read-only t face minibuffer-prompt) (default (car (cdr (car (get 'minibuffer-prompt-properties 'standard-value))))) (dont-touch-prompt-prop '(cursor-intangible t))) ;; When `cursor-intangible' property is detected in `minibuffer-prompt-properties', ;; `cursor-intangible-mode' is automatically added to `minibuffer-setup-hook' ;; (see cus-start.el). (custom-set-variables '(minibuffer-prompt-properties (append default dont-touch-prompt-prop) nil nil "Make the minibuffer prompt intangible."))) It is helpful that the minibuffer-setup-hook is updated automatically. But I would also vote for '(cursor-intangible t) to be part of the default value of minibuffer-prompt-properties. That way majority of the users would see the minibuffer prompt behaving as they expect. --047d7b2e41c024a4cd052f46e67b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Stefan,

I agree with what David ha= s to say; I too believe that there are a lot more users expecting the minib= uffer prompt to be intangible.

For now, I need to add the below to my emacs confi= g (as I don't set the customize variables using the GUI approach, and I= would like to simply append stuff to whatever the default value is):
=

(let (;; (get ..) =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -> ((quote (= read-only t face minibuffer-prompt)))
=C2=A0 =C2=A0 =C2=A0 ;; (car (get ..)= ) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -> (quote (read-only t face = minibuffer-prompt))
=C2=A0 =C2=A0 =C2=A0 ;; (cdr (car (get ..))) =C2=A0 =C2= =A0 =C2=A0 -> ((read-only t face minibuffer-prompt))
=C2=A0 =C2=A0 =C2= =A0 ;; (car (cdr (car (get ..)))) -> (read-only t face minibuffer-prompt= )
= =C2=A0 =C2=A0 =C2=A0 (dont-touch-prompt= -prop '(cursor-intangible t)))
<= font face=3D"monospace, monospace">=C2=A0 ;; When `cursor-intangible' p= roperty is detected in `minibuffer-prompt-properties',
=C2=A0 ;; `curso= r-intangible-mode' is automatically added to `minibuffer-setup-hook'= ;
=C2=A0 (custom-set-variables '(minibuff= er-prompt-properties
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (append default dont-touch-prompt-pr= op)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 nil nil "Make the minibuffer prompt intangible.&q= uot;)))

It is helpful that the minibuffer-setup-hook is updated automatica= lly. But I would also vote for '(cursor-intangible t) to be part of the= default value of minibuffer-prompt-properties. That way majority of the us= ers would see the minibuffer prompt behaving as they expect.
--047d7b2e41c024a4cd052f46e67b--