From: Drew Adams <drew.adams@oracle.com>
To: 17511@debbugs.gnu.org
Subject: bug#17511: 24.4.50; `line-move-ignore-invisible': doc and purpose not clear
Date: Fri, 16 May 2014 13:52:58 -0700 (PDT) [thread overview]
Message-ID: <e3c64828-b37d-466e-8f33-b509898027a1@default> (raw)
1. The doc string says only that `next-line' and `previous-line' ignore
invisible lines. What does it mean for these commands to "ignore
invisible lines" - what does "ignore" mean here? What's the
user-visible BEHAVIOR difference between a nil and a non-nil value?
Why/when might a user change the value to nil?
2. The doc string speaks of invisible lines. But (elisp) `Invisible
Text' speaks of "invisible newlines" (not lines), which is presumably
something different (newline chars vs lines of any chars except newline,
possibly including the separating newlines). Are both true? Which?
3 The manual speaks of "the user-level line motion commands", not just
`next-line' and `previous-line'. Is there a difference? What other
commands are involved here, besides those two?
4. This Elisp manual node is not very clear in general. Again, what
does it mean for these line commands to ignore invisible newlines? Or,
for that matter, for them to "not care whether the text is invisible"?
What user-visible BEHAVIOR difference is there?
5. After saying that we provide option `line-move-ignore-invisible'
specifically to let you prevent line motion commands from ignoring
invisible newlines (whatever that might mean!), this node says that if
ANY command ends with point in a certain position relative to invisible
text, then the cursor is automatically moved past that stretch of
invisible text (one direction or the other). How is this related to the
previous text about line motion commands and
`line-move-ignore-invisible'?
If a user ends up understanding something coherent and useful from this
text, s?he is lucky indeed.
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-04-29 on ODIEONE
Bzr revision: 117031 monnier@iro.umontreal.ca-20140429151607-qnkgbymwfaj5ut08
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/snapshot/trunk
--enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
-Ic:/Devel/emacs/include''
next reply other threads:[~2014-05-16 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 20:52 Drew Adams [this message]
2014-05-17 9:00 ` bug#17511: 24.4.50; `line-move-ignore-invisible': doc and purpose not clear Eli Zaretskii
[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
[not found] <<8c772b14-20d1-4e3a-9936-f81936c3d31b@default>
[not found] ` <<83a9age9dl.fsf@gnu.org>
2014-05-17 16:03 ` 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
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=e3c64828-b37d-466e-8f33-b509898027a1@default \
--to=drew.adams@oracle.com \
--cc=17511@debbugs.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.