all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17511@debbugs.gnu.org
Subject: bug#17511: 24.4.50; `line-move-ignore-invisible': doc and purpose not clear
Date: Sat, 17 May 2014 09:24:23 -0700 (PDT)	[thread overview]
Message-ID: <01ef3dd7-c4a9-4e37-be97-ecd4b73d7436@default> (raw)
In-Reply-To: <<8361l4e66d.fsf@gnu.org>>

> OK, I removed the empty line.

Thx.  Maybe it would be good to decide on the convention to use and
document it in the guidelines.  Just a suggestion.

> I see no reason to mention invisible lines, because that might be
> confusing: what matters are not the lines, but the newlines.
> Therefore, the doc string now only talks about newlines, and the
> manual now says:
> 
>     Ordinarily, functions that operate on text or move point do not care
>   whether the text is invisible, they process invisible characters and
>   visible characters alike.  The user-level line motion commands,
>   such as @code{next-line}, @code{previous-line}, ignore invisible
>   newlines if @code{line-move-ignore-invisible} is non-@code{nil} (the
>   default), i.e., behave like these invisible newlines didn't exist in
>   the buffer, but only because they are explicitly programmed to do so.

Looks good.  I will close the bug.





  parent reply	other threads:[~2014-05-17 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<8c772b14-20d1-4e3a-9936-f81936c3d31b@default>
     [not found] ` <<83a9age9dl.fsf@gnu.org>
2014-05-17 16:03   ` bug#17511: 24.4.50; `line-move-ignore-invisible': doc and purpose not clear Drew Adams
2014-05-17 16:11     ` Eli Zaretskii
     [not found]   ` <<547b37b1-f55b-45e9-8c89-eb9388580d36@default>
     [not found]     ` <<8361l4e66d.fsf@gnu.org>
2014-05-17 16:24       ` Drew Adams [this message]
     [not found] <<e3c64828-b37d-466e-8f33-b509898027a1@default>
     [not found] ` <<83iop4eq5h.fsf@gnu.org>
2014-05-17 14:45   ` Drew Adams
2014-05-17 15:02     ` Eli Zaretskii
2014-05-16 20:52 Drew Adams
2014-05-17  9:00 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01ef3dd7-c4a9-4e37-be97-ecd4b73d7436@default \
    --to=drew.adams@oracle.com \
    --cc=17511@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.