From: Kaushal Modi <kaushal.modi@gmail.com>
To: 21874@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#21874: 25.0.50; point-entered no longer works
Date: Wed, 23 Mar 2016 16:30:05 -0400 [thread overview]
Message-ID: <CAFyQvY1_FZuuWY9W9JruJRDkA0Mkq2Mi4rzA7pazKhd1U4sb5Q@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1wwXTE4mtHoEOYKwm+bsnshsMJYvuQXVgbsPyA5yucGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
Then I tried the below (which sort of works):
(progn
(setq minibuffer-prompt-properties '(read-only t cursor-intangible t face
minibuffer-prompt))
(defun turn-on-cursor-intangible-mode ()
"Turns on cursor-intangible-mode."
(interactive)
(cursor-intangible-mode 1))
(define-globalized-minor-mode global-cursor-intangible-mode
cursor-intangible-mode turn-on-cursor-intangible-mode)
(global-cursor-intangible-mode 1))
Start emacs -Q and eval the above progn form.
The caveat is (and I cannot understand why) is that the cursor
intangibility does not kick in when you do C-x C-f for the first time! It
kicks in only from the second C-x C-f onwards.
The following steps try to explain what I mean (on latest build of
emacs-25):
1. emacs -Q
2. Eval the above progn form
3. C-x C-f C-x h (The read-only portion also gets selected!)
4. C-g
5. C-x C-f C-x h (NOW the read-only portion does not get selected as
expected)
So why is the cursor-intangible-mode not enabled in the minibuffer the
first time (Step 3)?
Also, would it be wise to enable cursor-intangible-mode globally? If not,
how can we have that mode always enabled in the minibuffer?
-------------------------
On the other hand, I have tested the below as an alternate solution
(probably better too as I am not enabling the mode globally) to always work:
(progn
(setq minibuffer-prompt-properties '(read-only t cursor-intangible t face
minibuffer-prompt))
(add-hook 'minibuffer-setup-hook #'cursor-intangible-mode))
If we want emacs to "do the right thing", should the above be made default?
[-- Attachment #2: Type: text/html, Size: 2909 bytes --]
next prev parent reply other threads:[~2016-03-23 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 23:27 bug#21874: 25.0.50; point-entered no longer works David Reitter
2016-03-23 20:06 ` Kaushal Modi
2016-03-23 20:30 ` Kaushal Modi [this message]
2016-03-23 21:28 ` Stefan Monnier
2016-03-23 21:38 ` Kaushal Modi
2016-03-23 21:55 ` Kaushal Modi
2016-03-24 0:27 ` Stefan Monnier
2016-03-24 2:14 ` David Reitter
2016-05-22 2:13 ` Paul Eggert
2022-02-15 10:52 ` bug#21874: `backward-char' can move point into minibuffer prompt by default Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY1_FZuuWY9W9JruJRDkA0Mkq2Mi4rzA7pazKhd1U4sb5Q@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=21874@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).