bug#1507: marked as done (move-end-of-line inline doc unclear. (intangibility))

[owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]


Your message dated Sun, 04 Jan 2009 03:12:18 -0500
with message-id <87d4f3qyl9.fsf@cyd.mit.edu>
and subject line Re: move-end-of-line inline doc unclear. (intangibility)
has caused the Emacs bug report #1507,
regarding move-end-of-line inline doc unclear. (intangibility)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
1507: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1507
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3486 bytes --]

From: xah lee <xah@xahlee.org>
To: bug-gnu-emacs@gnu.org
Subject: move-end-of-line inline doc unclear. (intangibility)
Date: Sat, 6 Dec 2008 15:58:54 -0800
Message-ID: <80C4B428-FB5B-4166-9287-AEF63F5895FA@xahlee.org>

it seems to me that the move-end-of-line inline doc is unclear.

in the inline doc for move-end-of-line, it says:

«
move-end-of-line is an interactive compiled Lisp function in  
`simple.el'.
It is bound to M-D.
(move-end-of-line arg)

Move point to end of current line as displayed.
(If there's an image in the line, this disregards newlines
which are part of the text that the image rests on.)

With argument arg not nil or 1, move forward arg - 1 lines first.
If point reaches the beginning or end of buffer, it stops there.
To ignore intangibility, bind `inhibit-point-motion-hooks' to t.
»


• It is not clear to me what this sentence means: “(If there's an  
image in the line, this disregards newlines which are part of the  
text that the image rests on.)” So, if there is a image on the  
current line... i don't know what it means to say it disregard  
newline, because to me eol char is at the end of line...

• the last paragraph about intangibility is unclear. (i don't  
understand what it means. Looking up on that hook var didn't help much.)

• am not sure if move-end-of-line should be used in elisp code,  
which is my primary query. If this function is not suitable in elisp  
code, perhaps the doc should say.

similar in move-beginning-of-line.

   Xah
∑ http://xahlee.org/

☄





[-- Attachment #3: Type: message/rfc822, Size: 2591 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: xah lee <xah@xahlee.org>
Cc: 1507-done@emacsbugs.donarmstrong.com
Subject: Re: move-end-of-line inline doc unclear. (intangibility)
Date: Sun, 04 Jan 2009 03:12:18 -0500
Message-ID: <87d4f3qyl9.fsf@cyd.mit.edu>

> It is not clear to me what this sentence means: “(If there's an image
> in the line, this disregards newlines which are part of the text that
> the image rests on.)” So, if there is a image on the current line... i
> don't know what it means to say it disregard newline, because to me
> eol char is at the end of line...

Whenever a range of text contains a text or overlay property with a
`display' property that specifies an image to display, Emacs displays
that image instead of displaying the range of text in the usual way.
Hence, move-end-of-line ignores newlines in that range of text, because
it is not displayed as the end of a line (it is "hidden" inside the
image).

> the last paragraph about intangibility is unclear. (i don't understand
> what it means. Looking up on that hook var didn't help much.)

Unfortunately, it's not feasible to explain the effects of every single
text or overlay property in docstrings.  The role of the `intangible'
property is explained in the "Special Properties" node of the Emacs Lisp
reference manual.

> am not sure if move-end-of-line should be used in elisp code, which is
> my primary query. If this function is not suitable in elisp code,
> perhaps the doc should say.

This function is suitable for use in elisp code, provided one keeps in
mind that it moves to the end of line *as displayed*, i.e., taking
things like text properties into account, exactly as C-e does.  This may
or may not be what you want in a Lisp program.