emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#16453: closed (24.3.50; Motion functions not respe


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#16453: closed (24.3.50; Motion functions not respecting field boundaries as documented)
Date: Wed, 05 Feb 2014 10:33:02 +0000

Your message dated Wed, 05 Feb 2014 11:32:21 +0100
with message-id <address@hidden>
and subject line Re: bug#16453: 24.3.50; Motion functions not respecting field 
boundaries as documented
has caused the debbugs.gnu.org bug report #16453,
regarding 24.3.50; Motion functions not respecting field boundaries as 
documented
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
16453: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16453
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; Motion functions not respecting field boundaries as documented Date: Wed, 15 Jan 2014 08:17:19 -0800 (PST)
(elisp) `Introduction to Minibuffers' says this:

 The text in the minibuffer always starts with the "prompt string",
 the text that was specified by the program that is using the minibuffer
 to tell the user what sort of input to type.  This text is marked
 read-only so you won't accidentally delete or change it.  It is also
 marked as a field (*note Fields::), so that certain motion functions,
 including `beginning-of-line', `forward-word', `forward-sentence', and
 `forward-paragraph', stop at the boundary between the prompt and the
 actual text.

So I would expect that `backward-word' and `backward-sexp' would stop at
the field boundary, which is the end of the prompt.  `beginning-of-line'
does indeed do this, as the doc suggests.  But `backward-word' and
`backward-sexp', at least, do not - they move backward into the prompt.

Seems like this is the wrong behavior, and the doc describes the right
behavior.  But perhaps it is the other way around and this is a doc bug.

FWIW, I noticed this because I use a different Lisp symbol completion
function in the minibuffer.  It moves `backward-sexp' and later tries to
delete the text corresponding to the symbol prefix to be completed.  If
that prefix is empty then it raises the error of attempting to modify
read-only text.  If `backward-sexp' did what the doc says then it would
not leave the field and enter the prompt.  This is not important to the
bug report - just mentioning how I happened to notice this.



In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2014-01-07 on ODIEONE
Bzr revision: 115916 address@hidden
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'



--- End Message ---
--- Begin Message --- Subject: Re: bug#16453: 24.3.50; Motion functions not respecting field boundaries as documented Date: Wed, 05 Feb 2014 11:32:21 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
Hi Drew,

Drew Adams <address@hidden> writes:

>> While I'm waiting for a core maintainer to have a look at this,
>> can you test the patch and report any side-effect?
>
> No, sorry.  I don't build Emacs from C sources.  I would test
> a Lisp patch if one were available.  But you don't really need
> me to test it.  I think the bug report is pretty clear, and I'm
> sure you understand it OK.  If you are unsure, let me know.
> And thanks for working on this.

I committed the patch.  Now closing this bug.
Thanks for reporting this,

-- 
 Bastien


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]